Bug#794755: [qwer at 9398.at: Re: Bug#794755: systemd kills ssh-server]

[qwer at vienna.at]

----- Forwarded message from qwer at 9398.at -----

Date: Thu, 6 Aug 2015 18:03:43 +0200
From: qwer at 9398.at
To: Michael Biebl <biebl at debian.org>
Subject: Re: Bug#794755: systemd kills ssh-server
User-Agent: Mutt/1.5.23 (2014-03-12)

On Thu, Aug 06, 2015 at 04:10:28PM +0200, Michael Biebl wrote:
> [please always CC the bug report]

Sorry, number lost.
 
> Am 06.08.2015 um 14:58 schrieb qwer at vienna.at:
> > On Thu, Aug 06, 2015 at 01:25:59PM +0200, Michael Biebl wrote:
> >> It looks like ssh service is restarted too often within a short period
> > Perfectly true.
> >> of time due to some external process (most likely the if-up.d hook).
> > Yes.
> >> Therefor systemd marks the service as failed, it's not that systemd
> >> kills ssh-server.
> > But how to restart the ssh-server?
> > Well, I did have to change one ethernet-card serving the ssh-server.
> > And /etc/init.d/ssh of course not can be used.
> > journalctl -xb shows quite nice that the ssh-server can't be started.
> > But I really would like to have it again in spite of using telnet-SSL.
> > But I don't know how to do it.
> You can reset the failed-state via
> systemctl reset-failed foo.service

systemctl status ssh

• ssh.service - OpenBSD Secure Shell server
   Loaded: loaded (/lib/systemd/system/ssh.service; enabled; vendor preset: enabled)
   Active: failed (Result: start-limit) since Don 2015-08-06 16:36:43 CEST; 2min 38s ago
  Process: 30254 ExecStart=/usr/sbin/sshd -D $SSHD_OPTS (code=exited, status=255)
 Main PID: 30254 (code=exited, status=255)

systemctl reset-failed

systemctl start ssh

[21619.081803] systemd[1]: Failed to start OpenBSD Secure Shell server
............................

[Cd]

systemctl status ssh

• ssh.service - OpenBSD Secure Shell server
   Loaded: loaded (/lib/systemd/system/ssh.service; enabled; vendor preset: enabled)
   Active: failed (Result: start-limit) since Don 2015-08-06 16:42:43 CEST; 40s ago
  Process: 30348 ExecStart=/usr/sbin/sshd -D $SSHD_OPTS (code=exited, status=255)
 Main PID: 30348 (code=exited, status=255)

ps aux | grep sshd

root     30377  0.0  0.0   2260   612 tty1     S+   16:45   0:00 sh -c ps aux | grep sshd
root     30379  0.0  0.0   4572  2240 tty1     S+   16:45   0:00 grep sshd
 
> Btw, it seems the return code from ssh was 255.
> That typically indicates a configuration error which you might investigate.
> journalctl -u ssh.service
> should give you the full log.

...~# journalctl -u ssh.service
-- Logs begin at Don 2015-08-06 17:03:03 CEST, end at Don 2015-08-06 17:58:08 CEST. --
Aug 06 17:04:33 9398 systemd[1]: Stopped OpenBSD Secure Shell server.
Aug 06 17:06:30 9398 systemd[1]: Started OpenBSD Secure Shell server.
Aug 06 17:06:30 9398 systemd[1]: Starting OpenBSD Secure Shell server...
Aug 06 17:06:33 9398 sshd[2259]: Missing privilege separation directory: /var/run/sshd
Aug 06 17:06:33 9398 systemd[1]: ssh.service: Main process exited, code=exited, status=255/n/a
Aug 06 17:06:33 9398 systemd[1]: ssh.service: Unit entered failed state.
Aug 06 17:06:33 9398 systemd[1]: ssh.service: Failed with result 'exit-code'.
Aug 06 17:06:33 9398 systemd[1]: ssh.service: Service hold-off time over, scheduling restart.
Aug 06 17:06:33 9398 systemd[1]: Started OpenBSD Secure Shell server.
Aug 06 17:06:33 9398 systemd[1]: Starting OpenBSD Secure Shell server...
Aug 06 17:06:33 9398 sshd[2564]: Missing privilege separation directory: /var/run/sshd
Aug 06 17:06:33 9398 systemd[1]: ssh.service: Main process exited, code=exited, status=255/n/a
Aug 06 17:06:33 9398 systemd[1]: ssh.service: Unit entered failed state.
Aug 06 17:06:33 9398 systemd[1]: ssh.service: Failed with result 'exit-code'.
Aug 06 17:06:33 9398 systemd[1]: ssh.service: Service hold-off time over, scheduling restart.
Aug 06 17:06:33 9398 systemd[1]: Started OpenBSD Secure Shell server.
Aug 06 17:06:33 9398 systemd[1]: Starting OpenBSD Secure Shell server...
Aug 06 17:06:33 9398 sshd[2572]: Missing privilege separation directory: /var/run/sshd
Aug 06 17:06:33 9398 systemd[1]: ssh.service: Main process exited, code=exited, status=255/n/a
Aug 06 17:06:33 9398 systemd[1]: ssh.service: Unit entered failed state.
Aug 06 17:06:33 9398 systemd[1]: ssh.service: Failed with result 'exit-code'.
Aug 06 17:06:34 9398 systemd[1]: ssh.service: Service hold-off time over, scheduling restart.
Aug 06 17:06:34 9398 systemd[1]: Started OpenBSD Secure Shell server.
Aug 06 17:06:34 9398 systemd[1]: Starting OpenBSD Secure Shell server...
Aug 06 17:06:34 9398 sshd[2575]: Missing privilege separation directory: /var/run/sshd
Aug 06 17:06:34 9398 systemd[1]: ssh.service: Main process exited, code=exited, status=255/n/a
Aug 06 17:06:34 9398 systemd[1]: ssh.service: Unit entered failed state.
Aug 06 17:06:34 9398 systemd[1]: ssh.service: Failed with result 'exit-code'.
Aug 06 17:06:34 9398 systemd[1]: ssh.service: Service hold-off time over, scheduling restart.
Aug 06 17:06:34 9398 systemd[1]: Started OpenBSD Secure Shell server.
Aug 06 17:06:34 9398 systemd[1]: Starting OpenBSD Secure Shell server...
Aug 06 17:06:34 9398 sshd[2583]: Missing privilege separation directory: /var/run/sshd
Aug 06 17:06:34 9398 systemd[1]: ssh.service: Main process exited, code=exited, status=255/n/a
Aug 06 17:06:34 9398 systemd[1]: ssh.service: Unit entered failed state.
Aug 06 17:06:34 9398 systemd[1]: ssh.service: Failed with result 'exit-code'.
Aug 06 17:06:34 9398 systemd[1]: ssh.service: Service hold-off time over, scheduling restart.
Aug 06 17:06:34 9398 systemd[1]: ssh.service: Start request repeated too quickly.
Aug 06 17:06:34 9398 systemd[1]: Failed to start OpenBSD Secure Shell server.
Aug 06 17:06:34 9398 systemd[1]: ssh.service: Unit entered failed state.
Aug 06 17:06:34 9398 systemd[1]: ssh.service: Failed with result 'start-limit'.

As you thought, tried to often.
The mistake must happen earlier but journalctl -xb ist much too long.

Thnak for your engagement up to now....


----- End forwarded message -----