Bug#755904: libpam-systemd: error in log after upgrade

[Benoit Friry]

Package: libpam-systemd
Version: 208-6
Severity: minor

Dear Maintainer,

After upgrade, I get lots of error in auth.log:
Jul 24 11:45:17 host sshd[23128]: pam_systemd(sshd:session): Failed to create session: Invalid argument

I think I encountered the same behaviour previously, and it was solved
by rebooting.

I have not seen any correlated issue.

Thanks,
Benoit

-- System Information:
Debian Release: jessie/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.14-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages libpam-systemd depends on:
ii libc6 2.19-7
ii libcap2 1:2.22-1.2
ii libdbus-1-3 1.8.6-1
ii libpam-runtime 1.1.8-3
ii libpam0g 1.1.8-3
ii multiarch-support 2.19-7
ii systemd 208-6
ii systemd-sysv 208-6

libpam-systemd recommends no packages.

libpam-systemd suggests no packages.

-- no debconf information


--
To UNSUBSCRIBE, email to debian-bugs-...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org

[Michael Biebl]

Hi,

Am 24.07.2014 14:10, schrieb Benoit Friry:
> Package: libpam-systemd
> Version: 208-6
> Severity: minor
>
> Dear Maintainer,
>
> After upgrade, I get lots of error in auth.log:
> Jul 24 11:45:17 host sshd[23128]: pam_systemd(sshd:session): Failed to create session: Invalid argument
>

Is systemd-logind running?
What's the output of loginctl before and after you login via ssh?

Could you edit /etc/pam.d/common-session and append a "debug=true" to the
session optional pam_systemd.so
line

This should give you a more verbose log.
Do you get anything in the journal? Specifically by systemd-logind?
You can filter it via "journalctl --unit systemd-logind.service"

Michael
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

[Benoit Friry]

Bonjour,

>> After upgrade, I get lots of error in auth.log:
>> Jul 24 11:45:17 host sshd[23128]: pam_systemd(sshd:session): Failed to create session: Invalid argument

> Is systemd-logind running?

# ps -ef|grep -v grep|grep systemd
root 5244 1 0 juin29 ? 00:00:47 /lib/systemd/systemd-logind

> What's the output of loginctl before and after you login via ssh?

no change

# loginctl
SESSION UID USER SEAT
5835 1001 laetitia seat0
6240 1001 laetitia seat0
6825 1001 laetitia seat0
8175 1001 laetitia seat0
8800 1001 laetitia seat0
10457 1001 laetitia seat0
22932 1001 laetitia seat0
24252 1001 laetitia seat0
26832 1001 laetitia seat0
31435 1001 laetitia seat0
49651 1001 laetitia seat0
49654 1001 laetitia seat0
1197 1000 benoit seat0

13 sessions listed.

[login from somewhere else]

# loginctl
SESSION UID USER SEAT
5835 1001 laetitia seat0
6240 1001 laetitia seat0
6825 1001 laetitia seat0
8175 1001 laetitia seat0
8800 1001 laetitia seat0
10457 1001 laetitia seat0
22932 1001 laetitia seat0
24252 1001 laetitia seat0
26832 1001 laetitia seat0
31435 1001 laetitia seat0
49651 1001 laetitia seat0
49654 1001 laetitia seat0
1197 1000 benoit seat0

13 sessions listed.

> Could you edit /etc/pam.d/common-session and append a "debug=true" to the
> session optional pam_systemd.so
> line
>
> This should give you a more verbose log.
> Do you get anything in the journal? Specifically by systemd-logind?
> You can filter it via "journalctl --unit systemd-logind.service"

journalctl --unit systemd-logind.service
No journal files were found.

in /var/log/auth.log
Jul 24 15:16:52 tc2 sshd[1427]: Accepted password for benoit from xxx.xxx.xxx.xxx port 18475 ssh2
Jul 24 15:16:52 tc2 sshd[1427]: pam_unix(sshd:session): session opened for user benoit by (uid=0)
Jul 24 15:16:52 tc2 sshd[1427]: pam_systemd(sshd:session): pam-systemd initializing
Jul 24 15:16:52 tc2 sshd[1427]: pam_systemd(sshd:session): Asking logind to create session: uid=1000 pid=1427 service=sshd type=tty class=user seat= vtnr=0 tty= display= remote=yes remote_user= remote_host=xxx.xxx.xxx.xxx
Jul 24 15:16:52 tc2 sshd[1427]: pam_systemd(sshd:session): Failed to create session: Invalid argument
Jul 24 15:18:15 tc2 sshd[1427]: pam_unix(sshd:session): session closed for user benoit

Regards,
Benoit

[Michael Biebl]

Am 24.07.2014 15:20, schrieb Benoit Friry:
> Bonjour,
>
>>> After upgrade, I get lots of error in auth.log:
>>> Jul 24 11:45:17 host sshd[23128]: pam_systemd(sshd:session): Failed to create session: Invalid argument
>
>> Is systemd-logind running?
>
> # ps -ef|grep -v grep|grep systemd
> root 5244 1 0 juin29 ? 00:00:47 /lib/systemd/systemd-logind

Is that June 29th?

If so, you might have an old instance of logind running.
What's the output of "systemctl status systemd-logind.service"

If you run (as root) "systemctl restart systemd-logind.service", is the
problem gone?

[Benoit Friry]

>>>> After upgrade, I get lots of error in auth.log: Jul 24
>>>> 11:45:17 host sshd[23128]: pam_systemd(sshd:session): Failed
>>>> to create session: Invalid argument
>>
>>> Is systemd-logind running?
>>
>> # ps -ef|grep -v grep|grep systemd root 5244 1 0 juin29
>> ? 00:00:47 /lib/systemd/systemd-logind
>
> Is that June 29th?

yes

> If so, you might have an old instance of logind running. What's the
> output of "systemctl status systemd-logind.service"

# systemctl status systemd-logind.service
Failed to get D-Bus connection: No connection to service manager.

> If you run (as root) "systemctl restart systemd-logind.service", is
> the problem gone?

# systemctl restart systemd-logind.service
Failed to get D-Bus connection: No connection to service manager.

Seems something's wrong...

# /etc/init.d/dbus status
[ ok ] dbus is running.

[Benoit Friry]

>>> After a reboot your problem will be gone.

No more error in log after reboot. Bug report can be closed.

>> Is there any other way to fix that without rebooting?
>
> Unfortunately not. The new logind requires systemd as PID 1, which
> means you need to reboot.

Not a good news. :(

I used the opportunity of rebooting to test systemd
(init=/bin/systemd). I hope next upgrade will not need rebooting.

(First impression is rather bad: boot is slower, boot messages are
unreadable, and password prompt to luksOpen is hidden.)

Many thanks,

[Michael Biebl]

Am 24.07.2014 22:59, schrieb Benoit Friry:
>>>> After a reboot your problem will be gone.
>
> No more error in log after reboot. Bug report can be closed.
>
>>> Is there any other way to fix that without rebooting?
>>
>> Unfortunately not. The new logind requires systemd as PID 1, which
>> means you need to reboot.
>
> Not a good news. :(
>
> I used the opportunity of rebooting to test systemd
> (init=/bin/systemd). I hope next upgrade will not need rebooting.
>
> (First impression is rather bad: boot is slower, boot messages are
> unreadable, and password prompt to luksOpen is hidden.)

If you want a verbose boot, you can remove "quiet" from the kernel
command line.

Can you boot with "systemd.log_level=debug" on the kernel command line
and send me the output of "journalctl -alb".

Do you have any mount points in /etc/fstab which are not accessible
during boot?
Systemd has a 90 secs timeout for those.