[Solved] Service doesn’t start after update

zoidby · 2019-09-20 12:07:46

Edit: This issue was just solved by a pacman -Syu. The update included systemd (243.51-1 -> 243.78-1), which might have had a bug, but i’m not certain.

I use xlogin to automatically start X at boot. But since an update a couple of days ago, the service doesn’t get started at boot anymore.

It is enabled:

# systemctl status xlogin@zoidby.service 
● xlogin@zoidby.service - Direct X login for user zoidby
   Loaded: loaded (/etc/systemd/system/xlogin@zoidby.service; enabled; vendor preset: disabled)
   Active: active (running) since Tue 2019-09-17 13:53:53 CEST; 3 days ago
 Main PID: 1412 (xfwm4)
    Tasks: 0
   Memory: 552.0K
   CGroup: /system.slice/system-xlogin.slice/xlogin@zoidby.service
           ‣ 1412 xfwm4

Sep 17 13:53:53 lain systemd[1]: Started Direct X login for user zoidby.
Sep 17 13:53:53 lain systemd[1412]: pam_unix(login:session): session opened for user zoidby by (uid=0)

And it works fine when started manually.

There is nothing in the logs until i start it manually.

Last edited by zoidby (2019-10-23 13:42:34)

ua4000 · 2019-10-01 15:33:51

zoidby wrote:

And it works fine when started manually.
There is nothing in the logs until i start it manually.

Sound like a timing or dependency problem, maybe running out of entropy ?

Try: add

ExecStartPre=/usr/bin/sleep 30

to the [Service] section of the systemd unit, to check out the 1st one.

Entropy: Does the unit start after generating some additional entropy ?
E.g. logging in with ssh and do some maintenance stuff.

zoidby · 2019-10-01 16:10:35

Thanks for your answer.

I tried both of your suggestions, but neither worked.

I also think that in both cases, the service would have to be started and fail. But there isn't even a indication of an failed startup attempt in the logs.

It’s as if the service wasn’t enabled.

V1del · 2019-10-01 16:21:04

Maybe the KMS issue, try enabling early KMS

Also to pick up on the entropy suggestion try installing and enabling haveged.

zoidby · 2019-10-01 16:43:14

Early KMS is already enabled.

Installing haveged did not help either.

Thanks anyway.

seth · 2019-10-01 17:25:25

Please post a full system journal and the status of the service *before* hand-invoking it.
You can use https://wiki.archlinux.org/index.php/Pastebin to feed output into a pastebin service.

zoidby · 2019-10-02 09:34:48

journal -b

systemctl status xlogin@zoidby

seth · 2019-10-02 14:07:24

There's no trace of any of this in the journal.

systemctl status x@vt7.service

(before fixing stuff)
Also check whether you get an updated X11 log before starting the server yourself.

zoidby · 2019-10-02 14:22:44

# systemctl status x@vt7
● x@vt7.service - X on vt7
   Loaded: loaded (/usr/lib/systemd/system/x@.service; static; vendor preset: disabled)
   Active: inactive (dead)

Also check whether you get an updated X11 log before starting the server yourself.

No updated log.

seth · 2019-10-02 14:53:34

systemctl show graphical.target

(system condition doesn't matter)

zoidby · 2019-10-02 15:26:41

# systemctl show graphical.target
Id=graphical.target
Names=graphical.target
Requires=multi-user.target
Wants=pcscd.service display-manager.service xlogin@zoidby.service
WantedBy=x@vt7.service
Conflicts=rescue.target rescue.service shutdown.target
Before=shutdown.target
After=pcscd.service x@vt7.service rescue.target rescue.service xlogin@zoidby.service display-manager.service multi-user.target
Documentation=man:systemd.special(7)
Description=Graphical Interface
LoadState=loaded
ActiveState=active
SubState=active
FragmentPath=/usr/lib/systemd/system/graphical.target
UnitFileState=static
UnitFilePreset=disabled
StateChangeTimestamp=Wed 2019-10-02 16:18:04 CEST
StateChangeTimestampMonotonic=47399725
InactiveExitTimestamp=Wed 2019-10-02 16:18:04 CEST
InactiveExitTimestampMonotonic=47399725
ActiveEnterTimestamp=Wed 2019-10-02 16:18:04 CEST
ActiveEnterTimestampMonotonic=47399725
ActiveExitTimestampMonotonic=0
InactiveEnterTimestampMonotonic=0
CanStart=yes
CanStop=yes
CanReload=no
CanIsolate=yes
StopWhenUnneeded=no
RefuseManualStart=no
RefuseManualStop=no
AllowIsolate=yes
DefaultDependencies=yes
OnFailureJobMode=replace
IgnoreOnIsolate=no
NeedDaemonReload=no
JobTimeoutUSec=infinity
JobRunningTimeoutUSec=infinity
JobTimeoutAction=none
ConditionResult=yes
AssertResult=yes
ConditionTimestamp=Wed 2019-10-02 16:18:04 CEST
ConditionTimestampMonotonic=47399519
AssertTimestamp=Wed 2019-10-02 16:18:04 CEST
AssertTimestampMonotonic=47399519
Transient=no
Perpetual=no
StartLimitIntervalUSec=10s
StartLimitBurst=5
StartLimitAction=none
FailureAction=none
SuccessAction=none
InvocationID=2c033cd8cd2446fdba57c52acda84a41
CollectMode=inactive

zoidby · 2019-10-23 13:42:46

This issue was just solved by a pacman -Syu. The update included systemd (243.51-1 -> 243.78-1), which might have had a bug, but i’m not certain.

Arch Linux

#1 2019-09-20 12:07:46

[Solved] Service doesn’t start after update

#2 2019-10-01 15:33:51

Re: [Solved] Service doesn’t start after update

#3 2019-10-01 16:10:35

Re: [Solved] Service doesn’t start after update

#4 2019-10-01 16:21:04

Re: [Solved] Service doesn’t start after update

#5 2019-10-01 16:43:14

Re: [Solved] Service doesn’t start after update

#6 2019-10-01 17:25:25

Re: [Solved] Service doesn’t start after update

#7 2019-10-02 09:34:48

Re: [Solved] Service doesn’t start after update

#8 2019-10-02 14:07:24

Re: [Solved] Service doesn’t start after update

#9 2019-10-02 14:22:44

Re: [Solved] Service doesn’t start after update

#10 2019-10-02 14:53:34

Re: [Solved] Service doesn’t start after update

#11 2019-10-02 15:26:41

Re: [Solved] Service doesn’t start after update

#12 2019-10-23 13:42:46

Re: [Solved] Service doesn’t start after update

Board footer