Job for ssh.service failed because the control process exited with error code. See "systemctl status ssh.service" and "journalctl -xe" for details.

[agus supriyadi]

ssh.service - OpenBSD Secure Shell server
   Loaded: loaded (/lib/systemd/system/ssh.service; enabled; vendor preset: enab
   Active: failed (Result: exit-code) since Mon 2017-09-11 12:18:44 WIB; 1min 33
  Process: 18799 ExecStart=/usr/sbin/sshd -D $SSHD_OPTS (code=exited, status=255
 Main PID: 18799 (code=exited, status=255)

Sep 11 12:18:44 mutiara systemd[1]: Starting OpenBSD Secure Shell server...
Sep 11 12:18:44 mutiara sshd[18799]: /etc/ssh/sshd_config line 89: Subsystem 'sf
Sep 11 12:18:44 mutiara systemd[1]: ssh.service: Main process exited, code=exite
Sep 11 12:18:44 mutiara systemd[1]: Failed to start OpenBSD Secure Shell server.
Sep 11 12:18:44 mutiara systemd[1]: ssh.service: Unit entered failed state.
Sep 11 12:18:44 mutiara systemd[1]: ssh.service: Failed with result 'exit-code'.

[Colin Watson (cjwatson)]

You need to get the full contents of the line in the status output that talks about a problem with /etc/ssh/sshd_config. "systemctl status -l ssh.service | grep sshd_config" should print it.

[Launchpad Janitor (janitor)]

[Expired for openssh (Ubuntu) because there has been no activity for 60 days.]