On Monday, 5 June 2017 9:38:13 AM AEST Colin Watson wrote:
> Would you like to look into why that didn't work on your system?
Probably due to failure of (non essential) mount point or unrelated service...
It happened again today:
~~~~
Jul 17 09:14:00 deblab systemd[1]: Starting OpenBSD Secure Shell server...
Jul 17 09:14:00 deblab sshd[153531]: Missing privilege separation directory: /run/sshd
Jul 17 09:14:00 deblab systemd[1]: ssh.service: Main process exited, code=exited, status=255/n/a
Jul 17 09:14:00 deblab systemd[1]: Failed to start OpenBSD Secure Shell server.
Jul 17 09:14:00 deblab systemd[1]: ssh.service: Unit entered failed state.
Jul 17 09:14:00 deblab systemd[1]: ssh.service: Failed with result 'exit-code'.
~~~~
So I had a chance to try another fix to the problem: I was able to start
"ssh.service" again after adding the following line:
RuntimeDirectory=sshd
Perhaps that would be a reliable way to fix the problem...
See [1] for details.
[1]: https://www.freedesktop.org/software/systemd/man/systemd.exec.html#RuntimeDirectory=
--
Regards,
Dmitry Smirnov.
Attachment:
signature.asc
Description: This is a digitally signed message part.