On Fri, 15 Aug 2014 21:24:38 +0200 Michael Biebl <bi...@debian.org> wrote:
> Am 15.08.2014 20:34, schrieb Joe: > > > > 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. <snip>> > Those might be cron jobs which start a new PAM session. > > Could you check the dates when cron is running? > > There are no custom cron jobs, it's all defaults. This doesn't fit weekly + monthly, and nearly everything is daily. Ah, a bit further. I've become dependent on the journald logs very quickly... looking further afield, I've found this in daemon.log: 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 08:32:09 jresid systemd[1]: Starting User Manager for 65534... Aug 12 08:32:09 jresid systemd[1]: Starting Session c1 of user nobody. Aug 12 08:32:09 jresid systemd[1]: Started Session c1 of user nobody. Aug 12 08:32:09 jresid systemd[2582]: Failed to open private bus connection: Failed to connect to socket /run/user/65534/dbus/user_bus_socket: No such file or directory Aug 12 08:32:09 jresid systemd[2582]: Starting Default. Aug 12 08:32:09 jresid systemd[2582]: Reached target Default. Aug 12 08:32:09 jresid systemd[2582]: Startup finished in 16ms. Aug 12 08:32:09 jresid systemd[1]: Started User Manager for 65534. Aug 12 08:32:09 jresid systemd[1]: Starting Session c2 of user nobody. Aug 12 08:32:09 jresid systemd[1]: Started Session c2 of user nobody. Aug 12 08:32:09 jresid systemd[1]: Starting Session c3 of user nobody. Aug 12 08:32:09 jresid systemd[1]: Started Session c3 of user nobody. Aug 12 08:32:09 jresid console-kit-daemon[2103]: GLib-CRITICAL: Source ID 27 was not found when attempting to remove it Aug 12 08:32:09 jresid console-kit-daemon[2103]: GLib-CRITICAL: Source ID 42 was not found when attempting to remove it Aug 12 08:32:09 jresid console-kit-daemon[2103]: console-kit-daemon[2103]: GLib-CRITICAL: Source ID 27 was not found when attempting to remove it Aug 12 08:32:09 jresid console-kit-daemon[2103]: console-kit-daemon[2103]: GLib-CRITICAL: Source ID 42 was not found when attempting to remove it I take it the 'c' in the session number is connected to 'console', and the two failed attempts are the reason for a shutdown problem. The trouble is, the Glib error seems fairly generic, and nobody seems to have seen exactly what I'm seeing. There is a Ubuntu bug, but it doesn't look relevant here. The 'failed to open private bus' happens with my user as well, and doesn't seem to stop my session working. No, a red herring here, daemon.log has the same entries for the 'good' days, when journalctl wasn't showing me any 65534 entries at all. I can see entries in daemon.log which should have turned up in my grep of journalctl and didn't. This is a can of worms, and I hereby abandon it. This is sid, I'll just put up with the shutdown problem until the worst bugs are weeded out of systemd and friends. If journald isn't logging and reporting everything, there's practically no chance of fixing this, and I don't have enough information to make a bug report. Thanks anyway, Michael. -- Joe -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140815213903.760a2...@jresid.jretrading.com
