Here are the logs as follows:

‚óŹ launchWeston.service - launch weston
   Loaded: loaded (/etc/systemd/system/launchWeston.service; disabled; vendor 
preset: enabled)
   Active: failed (Result: protocol) since Fri 2019-02-22 04:56:02 UTC; 3min 
12s ago
  Process: 3177 ExecStart=/usr/bin/weston (code=killed, signal=TERM)
 Main PID: 3177 (code=killed, signal=TERM)

Feb 22 04:56:01 h3ulcb systemd[1]: launchWeston.service: Unit entered failed 
state.
Feb 22 04:56:01 h3ulcb systemd[1]: launchWeston.service: Failed with result 
'protocol'.
Feb 22 04:56:02 h3ulcb systemd[1]: launchWeston.service: Service hold-off time 
over, scheduling restart.
Feb 22 04:56:02 h3ulcb systemd[1]: Stopped launch weston.
Feb 22 04:56:02 h3ulcb systemd[1]: launchWeston.service: Start request repeated 
too quickly.
Feb 22 04:56:02 h3ulcb systemd[1]: Failed to start launch weston.
Feb 22 04:56:02 h3ulcb systemd[1]: launchWeston.service: Unit entered failed 
state.
Feb 22 04:56:02 h3ulcb systemd[1]: launchWeston.service: Failed with result 
'protocol'.


******************************************************************************************************


journalctl -xe logs as follows:



-- Unit getty at 
tty1.service<https://lists.freedesktop.org/mailman/listinfo/systemd-devel> has 
finished starting up.
--
-- The start-up result is done.
Feb 22 04:55:59 h3ulcb systemd[1]: Starting launch weston...
-- Subject: Unit launchWeston.service has begun start-up
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit launchWeston.service has begun starting up.
Feb 22 04:56:00 h3ulcb systemd[1]: Started Serial Getty on ttySC0.
-- Subject: Unit serial-getty at 
ttySC0.service<https://lists.freedesktop.org/mailman/listinfo/systemd-devel> 
has finished start-up
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit serial-getty at 
ttySC0.service<https://lists.freedesktop.org/mailman/listinfo/systemd-devel> 
has finished starting up.
--
-- The start-up result is done.
Feb 22 04:56:00 h3ulcb PAS[3076]: PAS >> Daemon process PersistenceAdminService 
starting.
Feb 22 04:56:00 h3ulcb systemd[1]: Reached target Login Prompts.
-- Subject: Unit getty.target has finished start-up
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit getty.target has finished starting up.
--
-- The start-up result is done.
Feb 22 04:56:00 h3ulcb systemd[1]: Reached target Multi-User System.
-- Subject: Unit multi-user.target has finished start-up
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit multi-user.target has finished starting up.
--
-- The start-up result is done.
Feb 22 04:56:00 h3ulcb systemd[1]: Starting Update UTMP about System Runlevel 
Changes...
-- Subject: Unit systemd-update-utmp-runlevel.service has begun start-up
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit systemd-update-utmp-runlevel.service has begun starting up.
Feb 22 04:56:00 h3ulcb systemd[3108]: pam_unix(login:account): account root has 
password changed in future
Feb 22 04:56:00 h3ulcb systemd[3108]: pam_unix(login:session): session opened 
for user root by (uid=0)
Feb 22 04:56:00 h3ulcb systemd[1]: Started Update UTMP about System Runlevel 
Changes.
-- Subject: Unit systemd-update-utmp-runlevel.service has finished start-up
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit systemd-update-utmp-runlevel.service has finished starting up.
--
-- The start-up result is done.
Feb 22 04:56:00 h3ulcb systemd[1]: Created slice User Slice of root.
-- Subject: Unit user-0.slice has finished start-up
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit user-0.slice has finished starting up.
--
-- The start-up result is done.
Feb 22 04:56:00 h3ulcb connmand[3067]: Checking loopback interface settings
Feb 22 04:56:00 h3ulcb connmand[3067]: System hostname is h3ulcb
Feb 22 04:56:00 h3ulcb dbus[3064]: [system] Activating via systemd: service 
name='fi.w1.wpa_supplicant1' unit='wpa_supplicant.service'
Feb 22 04:56:00 h3ulcb connmand[3067]: lo {newlink} index 1 address 
00:00:00:00:00:00 mtu 65536
Feb 22 04:56:00 h3ulcb dbus[3064]: [system] Activating via systemd: service 
name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service'
Feb 22 04:56:00 h3ulcb connmand[3067]: lo {newlink} index 1 operstate 0 
<UNKNOWN>
Feb 22 04:56:00 h3ulcb connmand[3067]: eth0 {create} index 2 type 1 <ETHER>
Feb 22 04:56:00 h3ulcb connmand[3067]: eth0 {update} flags 4098 <DOWN>
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 <DOWN>
Feb 22 04:56:00 h3ulcb 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 
e6800000.ethernet-ffffffff:00: attached PHY driver [Micrel KSZ9031 Gigabit PHY] 
(mii_bus:phy_addr=e6800000.ethernet-ffffffff: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 <UP,RUNNING>
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 
<UNKNOWN>
Feb 22 04:56:00 h3ulcb connmand[3067]: eth0 {update} flags 36867 <UP>
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 <DOWN>
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 <ppaala...@gmail.com>
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 +0000
Rajshekhar Sanda <rajshekhar.sa...@tcs.com> 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

Reply via email to