Am 29.08.2014 14:08, schrieb Iain M Conochie: > I just updated my jessie box, and noticed ssh was no longer running: > > systemctl status ssh > ssh.service - OpenBSD Secure Shell server > Loaded: loaded (/lib/systemd/system/ssh.service; enabled) > Active: failed (Result: start-limit) since Fri 2014-08-29 10:33:29 BST; > 2h 25min ago > Main PID: 16698 (code=exited, status=0/SUCCESS) > CGroup: /system.slice/ssh.service > > Aug 29 10:33:28 weezer systemd[1]: Starting OpenBSD Secure Shell server... > Aug 29 10:33:28 weezer systemd[1]: Started OpenBSD Secure Shell server. > Aug 29 10:33:28 weezer sshd[16698]: Server listening on 0.0.0.0 port 22. > Aug 29 10:33:28 weezer sshd[16698]: Server listening on :: port 22. > Aug 29 10:33:29 weezer systemd[1]: Stopping OpenBSD Secure Shell server... > Aug 29 10:33:29 weezer systemd[1]: Starting OpenBSD Secure Shell server... > Aug 29 10:33:29 weezer systemd[1]: ssh.service start request repeated > too quickly, refusing to start. > Aug 29 10:33:29 weezer systemd[1]: Failed to start OpenBSD Secure Shell > server. > Aug 29 10:33:29 weezer systemd[1]: Unit ssh.service entered failed state. > > Does anyone have any idea why systemd wants to stop ssh after it has > started? After I run:
Sounds like https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756547 Caused by the ifupdown hook /etc/network/if-up.d/openssh-server rapidly restarting the ssh service (if you have multiple interfaces) in a short time frame. -- 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
