[systemd-devel] In unit files of systemd version 234 Type=notify not working
Hi all, We are building Genivi 14 in which we are trying to launch weston at boot time with service file. service file is as follows: [Unit] Description= launch weston Requires= dbus-session.service dbus.service systemd-user-sessions.service After= dbus-session.socket dbus.service dbus-session.service systemd-user-sessions.service session-c1.scope ConditionPathExists=/dev/tty0 [Service] Type=notify User=root Restart=on-failure ExecStart=/usr/bin/weston NotifyAccess=all PAMName=login StandardInput=tty-fail TTYPath=/dev/tty7 TTYReset=yes TTYVHangup=yes TTYVTDisallocate=yes UtmpIdentifier=tty7 UtmpMode=root TimeoutStartSec=60 WatchdogSec=20 #ExecStart=/usr/bin/weston [Install] WantedBy=basic.target --- Here Type=notify is not supporting. I observed other types are working fine. Please help me to solve this issue. Thank You Regards, Rajshekhar Sanda Tata Consultancy Services Limited Mailto: rajshekhar.sa...@tcs.com Website: http://www.tcs.com<http://www.tcs.com/> Experience certainty.IT Services Business Solutions Consulting =-=-= Notice: The information contained in this e-mail message and/or attachments to it may contain confidential or privileged information. If you are not the intended recipient, any dissemination, use, review, distribution, printing or copying of the information contained in this e-mail message and/or attachments to it are strictly prohibited. If you have received this communication in error, please notify us by reply e-mail or telephone and immediately and permanently delete the message and any attachments. Thank you ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] Weston not launching Via Service file.
b systemd[1]: Starting User Manager for UID 0... -- Subject: Unit user at 0.service<https://lists.freedesktop.org/mailman/listinfo/systemd-devel> has begun start-up -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit user at 0.service<https://lists.freedesktop.org/mailman/listinfo/systemd-devel> has begun starting up. Feb 22 04:56:00 h3ulcb systemd[3121]: pam_unix(systemd-user:account): account root has password changed in future Feb 22 04:56:00 h3ulcb kernel: audit: type=1006 audit(1550811360.143:2): pid=3121 uid=0 old-auid=4294967295 auid=0 tty=(none) old-ses=4294967295 ses=1 res=1 Feb 22 04:56:00 h3ulcb systemd[3121]: pam_unix(systemd-user:session): session opened for user root by (uid=0) Feb 22 04:56:00 h3ulcb systemd-logind[3068]: New session c1 of user root. -- Subject: A new session c1 has been created for user root -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- Documentation: https://www.freedesktop.org/wiki/Software/systemd/multiseat -- -- A new session with the ID c1 has been created for the user root. -- -- The leading process of the session is 3108. Feb 22 04:56:00 h3ulcb systemd[1]: Started Session c1 of user root. -- Subject: Unit session-c1.scope has finished start-up -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit session-c1.scope has finished starting up. -- -- The start-up result is done. Feb 22 04:56:00 h3ulcb systemd[1]: Starting Hostname Service... -- Subject: Unit systemd-hostnamed.service has begun start-up -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit systemd-hostnamed.service has begun starting up. Feb 22 04:56:00 h3ulcb systemd[1]: Starting WPA supplicant... -- Subject: Unit wpa_supplicant.service has begun start-up -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit wpa_supplicant.service has begun starting up. Feb 22 04:56:00 h3ulcb kernel: Micrel KSZ9031 Gigabit PHY e680.ethernet-:00: attached PHY driver [Micrel KSZ9031 Gigabit PHY] (mii_bus:phy_addr=e680.ethernet-:00, irq=179) Feb 22 04:56:00 h3ulcb kernel: IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready Feb 22 04:56:00 h3ulcb connmand[3067]: Adding interface eth0 [ ethernet ] Feb 22 04:56:00 h3ulcb connmand[3067]: eth0 {update} flags 36931 Feb 22 04:56:00 h3ulcb connmand[3067]: eth0 {newlink} index 2 address 76:52:48:4C:23:63 mtu 1500 Feb 22 04:56:00 h3ulcb connmand[3067]: eth0 {newlink} index 2 operstate 0 Feb 22 04:56:00 h3ulcb connmand[3067]: eth0 {update} flags 36867 Feb 22 04:56:00 h3ulcb connmand[3067]: eth0 {newlink} index 2 address 76:52:48:4C:23:63 mtu 1500 Feb 22 04:56:00 h3ulcb connmand[3067]: eth0 {newlink} index 2 operstate 2 Feb 22 04:56:00 h3ulcb systemd[1]: Failed to start launch weston. -- Subject: Unit launchWeston.service has failed -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit launchWeston.service has failed. -- -- The result is failed. Regards, Rajshekhar Sanda Tata Consultancy Services Limited Mailto: rajshekhar.sa...@tcs.com Website: http://www.tcs.com<http://www.tcs.com/> Experience certainty.IT Services Business Solutions Consulting ____ ____ From: Pekka Paalanen Sent: Friday, May 17, 2019 1:08:53 PM To: Rajshekhar Sanda Cc: systemd-devel@lists.freedesktop.org; Madhu Chandrashekhar Subject: Re: [systemd-devel] Weston not launching Via Service file. On Fri, 17 May 2019 04:36:52 + Rajshekhar Sanda wrote: > Hello, > > > We are working on Genivi14, in which we are trying to launch weston > via service file. It is not working if iam giving Type=notify in > service file. > Hi, could you attach the stderr and stdout output of Weston as well, please? You should be able to find that in your system journal I guess. That should help diagnose if it is a problem with Weston or with the systemd unit file. Thanks, pq =-=-= Notice: The information contained in this e-mail message and/or attachments to it may contain confidential or privileged information. If you are not the intended recipient, any dissemination, use, review, distribution, printing or copying of the information contained in this e-mail message and/or attachments to it are strictly prohibited. If you have received this communication in error, please notify us by reply e-mail or telephone and immediately and permanently delete the message and any attachments. Thank you ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] Weston not launching Via Service file.
A new session with the ID c1 has been created for the user root. -- -- The leading process of the session is 3108. Feb 22 04:56:00 h3ulcb systemd[1]: Started Session c1 of user root. -- Subject: Unit session-c1.scope has finished start-up -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit session-c1.scope has finished starting up. -- -- The start-up result is done. Feb 22 04:56:00 h3ulcb systemd[1]: Starting Hostname Service... -- Subject: Unit systemd-hostnamed.service has begun start-up -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit systemd-hostnamed.service has begun starting up. Feb 22 04:56:00 h3ulcb systemd[1]: Starting WPA supplicant... -- Subject: Unit wpa_supplicant.service has begun start-up -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit wpa_supplicant.service has begun starting up. Feb 22 04:56:00 h3ulcb kernel: Micrel KSZ9031 Gigabit PHY e680.ethernet-:00: attached PHY driver [Micrel KSZ9031 Gigabit PHY] (mii_bus:phy_addr=e680.ethernet-:00, irq=179) Feb 22 04:56:00 h3ulcb kernel: IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready Feb 22 04:56:00 h3ulcb connmand[3067]: Adding interface eth0 [ ethernet ] Feb 22 04:56:00 h3ulcb connmand[3067]: eth0 {update} flags 36931 Feb 22 04:56:00 h3ulcb connmand[3067]: eth0 {newlink} index 2 address 76:52:48:4C:23:63 mtu 1500 Feb 22 04:56:00 h3ulcb connmand[3067]: eth0 {newlink} index 2 operstate 0 Feb 22 04:56:00 h3ulcb connmand[3067]: eth0 {update} flags 36867 Feb 22 04:56:00 h3ulcb connmand[3067]: eth0 {newlink} index 2 address 76:52:48:4C:23:63 mtu 1500 Feb 22 04:56:00 h3ulcb connmand[3067]: eth0 {newlink} index 2 operstate 2 Feb 22 04:56:00 h3ulcb systemd[1]: Failed to start launch weston. -- Subject: Unit launchWeston.service has failed -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit launchWeston.service has failed. -- -- The result is failed. *** please help me to solve this issue. Regards, Rajshekhar Sanda Tata Consultancy Services Limited Mailto: rajshekhar.sa...@tcs.com Website: http://www.tcs.com<http://www.tcs.com/> Experience certainty.IT Services Business Solutions Consulting =-=-= Notice: The information contained in this e-mail message and/or attachments to it may contain confidential or privileged information. If you are not the intended recipient, any dissemination, use, review, distribution, printing or copying of the information contained in this e-mail message and/or attachments to it are strictly prohibited. If you have received this communication in error, please notify us by reply e-mail or telephone and immediately and permanently delete the message and any attachments. Thank you ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel