You are not logged in.
Pages: 1
Since the commit on systemd-exit.service that changed exit on shutdown
https://github.com/systemd/systemd/comm … 5b100b3c90
incorporated in Arch version systemd-239.370-1-x86_64.pkg.tar.xz
systemd is hanging on shutdown with the following messages:
jan 08 16:45:31 RJASTEC-01118 systemd[900]: /usr/lib/systemd/user/systemd-exit.service:7: Failed to parse failure action specifier, ignoring: exit-force
jan 08 16:45:31 RJASTEC-01118 systemd[900]: systemd-exit.service: Service lacks both ExecStart= and ExecStop= setting. Refusing.
jan 08 16:45:31 RJASTEC-01118 systemd[900]: Failed to enqueue exit.target job: Unit systemd-exit.service has a bad unit file setting.
Although shutdown does not happen frequently, it is an annoying wait.
Any hints or an upstream bug?
Offline
I get the same errors.
Offline
Problem appears to be solved for me.
After the next reboot and newest updates via pacman -Syu, shutdown went smooth again.
Offline
If it will help there my
/usr/lib/systemd/user/systemd-exit.service
[Unit]
Description=Exit the Session
Documentation=man:systemd.special(7)
DefaultDependencies=no
Requires=shutdown.target
After=shutdown.target
[Service]
Type=oneshot
ExecStart=/usr/bin/systemctl --user --force exit
and
/usr/lib/systemd/system/systemd-exit.service
[Unit]
Description=Exit the Session
Documentation=man:systemd.special(7)
DefaultDependencies=no
Requires=shutdown.target
After=shutdown.target
[Service]
Type=oneshot
ExecStart=/usr/bin/systemctl --force exit
Also check
/etc/systemd/system.conf
...
DefaultTimeoutStartSec=10s
DefaultTimeoutStopSec=10s
...
Offline
Pages: 1