Re: Anybody know who user-65534 is?

[Joe <joe@jretrading.com>]

On Fri, 15 Aug 2014 21:39:03 +0100
Joe <joe@jretrading.com> wrote:


> 
> This is a can of worms, and I hereby abandon it.

OK, I lied. I was bored...

A little further on... journald *has* been keeping persistent journals,
but with different user permissions, now root:systemd-journal 640.

journalctl still shows entries up to August 3rd, but journalctl --user
shows all entries to date. If I change the permissions of the files
back to 755, this behaviour stays the same, except that I no longer
need to be a group member of systemd-journal, as expected. Something
changed on August 3rd, and I think it was the switch to systemd at pid
1. The cloned system had systemd at pid 1 from the beginning, or at
least as soon as systemd was installed. That system shows all entries
with just journalctl, it doesn't need --user.

I've persuaded journalctl to show me the logs for user 65534
(journalctl -u user-65534.slice as root) and they give little away.
Beyond doubt, this is the 90-second culprit, but it still isn't clear
why.

Aug 16 00:02:02 jresid systemd[26220]: pam_unix(systemd-user:session):
session opened for user nobody by (uid=0) 
Aug 16 00:02:03 jresid systemd[26220]:
pam_ck_connector(systemd-user:session): cannot determine display-device 
Aug 16 00:02:03 jresid systemd[2913]: Stopping Default. 
Aug 16 00:02:03 jresid systemd[2913]: Stopped target Default.
Aug 16 00:02:03 jresid systemd[2913]: Starting Shutdown. 
Aug 16 00:02:03 jresid systemd[2913]: Reached target Shutdown. 
Aug 16 00:02:03 jresid systemd[2913]: Starting Exit the Session... 
Aug 16 00:02:03 jresid systemd[2913]: systemd-exit.service: main
process exited, code=exited, status=200/CHDIR 
Aug 16 00:02:03 jresid systemd[2913]: Failed to start Exit the Session. 
Aug 16 00:02:03 jresid systemd[2913]: Dependency failed for Exit the
Session. 
Aug 16 00:02:03 jresid systemd[2913]: Unit systemd-exit.service entered
failed state. 
Aug 16 00:03:33 jresid systemd[1]: Stopping user-65534.slice. 
Aug 16 00:03:33 jresid systemd[1]: Removed slice user-65534.slice. --
Reboot --


What I need to know now is what dependency is failing. How do I find
out?

Here is systemd-exit.service:

#  This file is part of systemd.
#
#  systemd is free software; you can redistribute it and/or modify it
#  under the terms of the GNU Lesser General Public License as
published by
#  the Free Software Foundation; either version 2.1 of the License, or
#  (at your option) any later version.

[Unit]
Description=Exit the Session
Documentation=man:systemd.special(7)
DefaultDependencies=no
Requires=shutdown.target
After=shutdown.target

[Service]
Type=oneshot
ExecStart=/bin/kill -s 58 $MANAGERPID

Target shutdown had run, and /bin/kill exists. What other dependency
might there be? If the relevant PID wasn't found, would this cause a
'dependency' fault?

-- 
Joe