Anybody know who user-65534 is?
Apart from 'nobody', according to /etc/passwd. He seems to login most
sessions, and when he does, he causes the dreaded two-minute shutdown.
Here's what I can find in journalctl:
>sudo journalctl | grep user-65534
Aug 06 07:56:20 jresid systemd[1]: Starting user-65534.slice.
Aug 06 07:56:20 jresid systemd[1]: Created slice user-65534.slice.
Aug 06 20:05:54 jresid systemd[1]: Stopping user-65534.slice.
Aug 06 20:05:54 jresid systemd[1]: Removed slice user-65534.slice.
Aug 07 07:58:40 jresid systemd[1]: Starting user-65534.slice.
Aug 07 07:58:40 jresid systemd[1]: Created slice user-65534.slice.
Aug 07 20:57:31 jresid systemd[1]: Stopping user-65534.slice.
Aug 07 20:57:31 jresid systemd[1]: Removed slice user-65534.slice.
Aug 11 08:27:34 jresid systemd[1]: Starting user-65534.slice.
Aug 11 08:27:34 jresid systemd[1]: Created slice user-65534.slice.
Aug 11 09:10:25 jresid systemd[1]: Stopping user-65534.slice.
Aug 11 09:10:25 jresid systemd[1]: Removed slice user-65534.slice.
Aug 12 08:32:09 jresid systemd[1]: Starting user-65534.slice.
Aug 12 08:32:09 jresid systemd[1]: Created slice user-65534.slice.
Aug 12 22:17:40 jresid systemd[1]: Stopping user-65534.slice.
Aug 12 22:17:40 jresid systemd[1]: Removed slice user-65534.slice.
Aug 13 15:16:24 jresid systemd[1]: Starting user-65534.slice.
Aug 13 15:16:24 jresid systemd[1]: Created slice user-65534.slice.
Aug 13 21:51:37 jresid systemd[1]: Stopping user-65534.slice.
Aug 13 21:51:37 jresid systemd[1]: Removed slice user-65534.slice.
Aug 14 08:23:02 jresid systemd[1]: Starting user-65534.slice.
Aug 14 08:23:02 jresid systemd[1]: Created slice user-65534.slice.
Aug 14 20:39:35 jresid systemd[1]: Stopping user-65534.slice.
Aug 14 20:39:35 jresid systemd[1]: Removed slice user-65534.slice.
Aug 15 07:09:41 jresid systemd[1]: Starting user-65534.slice.
Aug 15 07:09:41 jresid systemd[1]: Created slice user-65534.slice.
Aug 15 07:27:28 jresid systemd[1]: Stopping user-65534.slice.
Aug 15 07:27:28 jresid systemd[1]: Removed slice user-65534.slice.
>sudo journalctl | grep user@65534
Aug 06 20:05:54 jresid systemd[1]: user@65534.service stopping timed
out. Killing.
Aug 06 20:05:54 jresid systemd[1]: Unit user@65534.service entered
failed state.
Aug 07 20:57:31 jresid systemd[1]: user@65534.service stopping timed
out. Killing.
Aug 07 20:57:31 jresid systemd[1]: Unit user@65534.service entered
failed state.
Aug 11 09:10:25 jresid systemd[1]: user@65534.service stopping timed
out. Killing.
Aug 11 09:10:25 jresid systemd[1]: Unit user@65534.service entered
failed state.
Aug 12 22:17:40 jresid systemd[1]: user@65534.service stopping timed
out. Killing.
Aug 12 22:17:40 jresid systemd[1]: Unit user@65534.service entered
failed state.
Aug 13 21:51:37 jresid systemd[1]: user@65534.service stopping timed
out. Killing.
Aug 13 21:51:37 jresid systemd[1]: Unit user@65534.service entered
failed state.
Aug 14 20:39:35 jresid systemd[1]: user@65534.service stopping timed
out. Killing.
Aug 14 20:39:35 jresid systemd[1]: Unit user@65534.service entered
failed state.
Aug 15 07:27:28 jresid systemd[1]: user@65534.service stopping timed
out. Killing.
Aug 15 07:27:28 jresid systemd[1]: Unit user@65534.service entered
failed state.
The machine runs every day, so user-65534 skived off on the 8th, 9th
and 10th, and the shutdown was no slower than before systemd. I could
find no obvious service start failures on those days, though the boot
logs were missing on two of them (but not the third).
This is on a newly cloned (--set-selections) sid. The old system also
has a two minute shutdown, but I've no idea if it's the same thing, as
the journal hasn't been persistent since August 3rd, though it was
before that. I can find no explanation, and of course, no journald
logs. The live journals appear in /var/log/journal, but disappear
softly and silently on shutdown. As far as I can see, configuration is
default on both systems, and permissions are the same. Both are fully
updated to yesterday.
Any ideas?
--
Joe
Reply to: