systemd: user@9.service failed
This is somewhat puzzling. When I run 'systemctl status' I see:
● merlin
State: degraded
Jobs: 0 queued
Failed: 1 units
Since: Sat 2014-10-25 22:52:07 CDT; 9h ago
CGroup: /
The resulting tree displayed is of the running processes, so I ran
'systemctl --failed' and I see:
UNIT LOAD ACTIVE SUB DESCRIPTION
● user@9.service loaded failed failed User Manager for UID 9
LOAD = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB = The low-level unit activation state, values depend on unit type.
1 loaded units listed. Pass --all to see loaded but inactive units, too.
To show all installed unit files use 'systemctl list-unit-files'.
Well, 'systemctl status user@9.service' reports:
● user@9.service - User Manager for UID 9
Loaded: loaded (/lib/systemd/system/user@.service; static)
Active: failed (Result: timeout) since Sun 2014-10-26 01:51:45 CDT; 6h ago
Process: 3483 ExecStart=/lib/systemd/systemd --user (code=killed, signal=KILL)
Main PID: 3483 (code=killed, signal=KILL)
Status: "Startup finished in 142ms."
Looking at /etc/passwd, UID 9 is:
news:x:9:9:news:/var/spool/news:/usr/sbin/nologin
and /var/log/syslog only shows:
Oct 26 01:51:45 merlin systemd[1]: user@9.service stop-sigterm timed out. Killing.
Oct 26 01:51:45 merlin systemd[1]: Unit user@9.service entered failed state.
Other than the fact that /var/spool/news does not exist, I don't have
anything news related installed except for slrn which I run as a local
user and not as a system instance. Interestingly, another Sid system
with systemd also has the same UID of 9 defined and /var/spool/news does
not exist either but I am not seeing the same unit failure on it. On the
kernel commandline is passed 'systemd.show_status=1' but I don't see
mention of a failure during the startup output to the screen.
Comparing the two systems I see that the one with the failure has
'console-kit-daemon.service' shown as "active (running)" and the one
without the failure shows it as "inactive (dead)". The consolekit
package is installed on each system, but '/etc/systemd/system' doesn't
have anything related to consolekit on either machine.
No doubt, this is a minor thing and I am trying to understand the
systemd way of doing things and how to follow up on minor issues like
this.
- Nate
--
"The optimist proclaims that we live in the best of all
possible worlds. The pessimist fears this is true."
Ham radio, Linux, bikes, and more: http://www.n0nb.us
Reply to: