Your message dated Thu, 24 Jul 2014 16:01:00 +0200
with message-id <[email protected]>
and subject line Re: Bug#755904: libpam-systemd: error in log after upgrade
has caused the Debian Bug report #755904,
regarding libpam-systemd: error in log after upgrade
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
755904: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755904
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
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
--- End Message ---
--- Begin Message ---
Am 24.07.2014 15:50, schrieb 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.
>
Oh, you're still booted into sysvinit? Well, yeah. That would explain
things. You have the old (v204) logind running and the new
libpam-systemd v208 talking to it.
After a reboot your problem will be gone.
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
--- End Message ---
_______________________________________________
Pkg-systemd-maintainers mailing list
[email protected]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
