Control: forcemerge 839607 -1 Am 11.10.2016 um 23:43 schrieb Keller Fuchs: > Package: systemd > Version: 215-17+deb8u4 > Severity: important > File: systemd-logind > > Dear maintainers, > > On a shell server I co-administer (to1.hashbang.sh), systemd-logind got > stuck in a restart loop, forcing us to reboot the system. > > logind not working is problematic, both due to the loss of functionality > and due to pam_systemd having to wait for timeout. > > > Here are the journal contents for unit systemd-journald: > >> [seemingly working fine until that point] >> Oct 11 01:34:27 to1 systemd[1]: systemd-logind.service watchdog timeout >> (limit 1min)!
Did someone trigger the systemd-notify bug? This sounds like it could be a duplicate of https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839607 Any user with shell access could be able to trigger the empty systemd-notify message. The result is exactly what you see, systemd-logind being killed by the watchdog. journald seems to be in a failed state as well. So I assume this is the same issue and will merge the two bug reports. -- 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
