On 07/06/2015 08:09 AM, Christoph Anton Mitterer wrote:
In that case, we're looking at two separate issues. I tested the add/reboot/reboot/purge/reboot/reboot cycle on multiple systems and found the behavior to be consistently reproducible, where installing libpam-systemd would consistently and completely resolve the issue I was seeing. The remote systems I tested are all running fresh, minimal installs of Debian 8.On Sat, 2015-07-04 at 14:40 -0700, Daniel Kauffman wrote:If sshd is configured with UsePAM yes, then after installing libpam -systemd to a remote system and rebooting, ssh sessions are cleanly terminated, but after purging libpam-systemd and rebooting, ssh session are not cleanly terminated.I'd guess that this is just some timing coincidence. I still see the issue from time to time, even though I have PAM enabled. E.g. just a few minutes ago it happened again with: # reboot PolicyKit daemon disconnected from the bus. We are no longer a registered authentication agent. g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting. <here it hangs>
Before installing libpam-systemd, on reboot, the terminal would hang for some time, then display:
Write failed: Broken pipe After which the terminal would return to the local prompt.After installing libpam-systemd and rebooting, on the next reboot, the terminal immediately displays:
Connection to N.N.N.N closed by remote host. Connection to N.N.N.N closed. After which the terminal immediately returns to the local prompt. -- Daniel Kauffman Lead Developer Rock Solid Solutions, LLC 877.239.9195 toll-free 208.699.9699 mobile