systemd killing sshd
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:
systemctl start ssh
it runs fine:
systemctl status ssh
ssh.service - OpenBSD Secure Shell server
Loaded: loaded (/lib/systemd/system/ssh.service; enabled)
Active: active (running) since Fri 2014-08-29 12:59:22 BST; 12s ago
Main PID: 4375 (sshd)
CGroup: /system.slice/ssh.service
└─4375 /usr/sbin/sshd -D
Aug 29 12:59:22 weezer systemd[1]: Starting OpenBSD Secure Shell server...
Aug 29 12:59:22 weezer systemd[1]: Started OpenBSD Secure Shell server.
Aug 29 12:59:22 weezer sshd[4375]: Server listening on 0.0.0.0 port 22.
Aug 29 12:59:22 weezer sshd[4375]: Server listening on :: port 22.
journalctl _SYSTEMD_UNIT=ssh.service
does not show anything interesting as the logs stop on 21st august.
Ta
Iain
Reply to: