Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- root@167:/# service ssh status
- ● ssh.service - OpenBSD Secure Shell server
- Loaded: loaded (/lib/systemd/system/ssh.service; enabled; vendor preset: enabled)
- Active: failed (Result: start-limit-hit) since Fri 2019-01-18 04:56:42 EST; 24min ago
- Process: 983 ExecStartPre=/usr/sbin/sshd -t (code=exited, status=255)
- Jan 18 04:56:42 167 systemd[1]: Failed to start OpenBSD Secure Shell server.
- Jan 18 04:56:42 167 systemd[1]: ssh.service: Unit entered failed state.
- Jan 18 04:56:42 167 systemd[1]: ssh.service: Failed with result 'exit-code'.
- Jan 18 04:56:42 167 systemd[1]: ssh.service: Service hold-off time over, scheduling restart.
- Jan 18 04:56:42 167 systemd[1]: Stopped OpenBSD Secure Shell server.
- Jan 18 04:56:42 167 systemd[1]: ssh.service: Start request repeated too quickly.
- Jan 18 04:56:42 167 systemd[1]: Failed to start OpenBSD Secure Shell server.
- Jan 18 04:56:42 167 systemd[1]: ssh.service: Unit entered failed state.
- Jan 18 04:56:42 167 systemd[1]: ssh.service: Failed with result 'start-limit-hit'.
- root@167:/# service ssh start
- Job for ssh.service failed because the control process exited with error code. See "systemctl status ssh.service" and "journalctl -xe" for details.
- root@167:/# sshd -t
- Missing privilege separation directory: /var/run/sshd
Add Comment
Please, Sign In to add comment