Sure thing: $ sudo systemctl status ssh [sudo] password for andrewta: ● ssh.service - OpenBSD Secure Shell server Loaded: loaded (/lib/systemd/system/ssh.service; enabled; vendor preset: enabled) Active: failed (Result: start-limit) since Wed 2016-02-24 14:44:04 CST; 20s ago Process: 918 ExecStart=/usr/sbin/sshd -D $SSHD_OPTS (code=exited, status=255) Main PID: 918 (code=exited, status=255)
Feb 24 14:44:04 janus-40 systemd[1]: ssh.service: Main process exited, code.../a Feb 24 14:44:04 janus-40 systemd[1]: ssh.service: Unit entered failed state. Feb 24 14:44:04 janus-40 systemd[1]: ssh.service: Failed with result 'exit-...'. Feb 24 14:44:04 janus-40 systemd[1]: ssh.service: Service hold-off time ove...t. Feb 24 14:44:04 janus-40 systemd[1]: Stopped OpenBSD Secure Shell server. Feb 24 14:44:04 janus-40 systemd[1]: ssh.service: Start request repeated to...y. Feb 24 14:44:04 janus-40 systemd[1]: Failed to start OpenBSD Secure Shell s...r. Feb 24 14:44:04 janus-40 systemd[1]: ssh.service: Unit entered failed state. Feb 24 14:44:04 janus-40 systemd[1]: ssh.service: Failed with result 'start...'. Hint: Some lines were ellipsized, use -l to show in full. journalctl -u ssh -- Logs begin at Wed 2016-02-24 14:44:03 CST, end at Sat 2016-02-27 12:32:17 CST. -- Feb 24 14:44:03 janus-40 systemd[1]: Started OpenBSD Secure Shell server. Feb 24 14:44:03 janus-40 systemd[1]: ssh.service: Main process exited, code=exited, status=255/n/a Feb 24 14:44:03 janus-40 systemd[1]: ssh.service: Unit entered failed state. Feb 24 14:44:03 janus-40 systemd[1]: ssh.service: Failed with result 'exit-code'. Feb 24 14:44:03 janus-40 systemd[1]: ssh.service: Service hold-off time over, scheduling restart. Feb 24 14:44:03 janus-40 systemd[1]: Stopped OpenBSD Secure Shell server. Feb 24 14:44:03 janus-40 systemd[1]: Started OpenBSD Secure Shell server. Feb 24 14:44:03 janus-40 systemd[1]: ssh.service: Main process exited, code=exited, status=255/n/a Feb 24 14:44:03 janus-40 systemd[1]: ssh.service: Unit entered failed state. Feb 24 14:44:03 janus-40 systemd[1]: ssh.service: Failed with result 'exit-code'. Feb 24 14:44:03 janus-40 systemd[1]: ssh.service: Service hold-off time over, scheduling restart. Feb 24 14:44:03 janus-40 systemd[1]: Stopped OpenBSD Secure Shell server. Feb 24 14:44:03 janus-40 systemd[1]: Started OpenBSD Secure Shell server. Feb 24 14:44:03 janus-40 systemd[1]: ssh.service: Main process exited, code=exited, status=255/n/a Feb 24 14:44:03 janus-40 systemd[1]: ssh.service: Unit entered failed state. Feb 24 14:44:03 janus-40 systemd[1]: ssh.service: Failed with result 'exit-code'. Feb 24 14:44:04 janus-40 systemd[1]: ssh.service: Service hold-off time over, scheduling restart. Feb 24 14:44:04 janus-40 systemd[1]: Stopped OpenBSD Secure Shell server. Feb 24 14:44:04 janus-40 systemd[1]: Started OpenBSD Secure Shell server. Feb 24 14:44:04 janus-40 systemd[1]: ssh.service: Main process exited, code=exited, status=255/n/a Feb 24 14:44:04 janus-40 systemd[1]: ssh.service: Unit entered failed state. Feb 24 14:44:04 janus-40 systemd[1]: ssh.service: Failed with result 'exit-code'. Feb 24 14:44:04 janus-40 systemd[1]: ssh.service: Service hold-off time over, scheduling restart. Feb 24 14:44:04 janus-40 systemd[1]: Stopped OpenBSD Secure Shell server. Feb 24 14:44:04 janus-40 systemd[1]: Started OpenBSD Secure Shell server. Feb 24 14:44:04 janus-40 systemd[1]: ssh.service: Main process exited, code=exited, status=255/n/a -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1549473 Title: ssh will not start at boot: systemctl status ssh -> output is listed as failed 255. Status in openssh package in Ubuntu: Incomplete Bug description: Using apt I have reinstalled and purged both ssh and openssh-server. apt-get remove --purge ssh openssh-server reinstalled updated and on boot the ctl status is failed 255 After much forum research and attempts to default solutions, the final word was that reinstall usually fixes this issue. With the issue usually stemming from ssh service trying to start before network services are available. Currently I have no logs available with journalctl -u sshd | tail -100 I can provide info pertaining to this on request. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: ssh 1:6.9p1-2ubuntu0.1 ProcVersionSignature: Ubuntu 4.2.0-30.35-generic 4.2.8-ckt3 Uname: Linux 4.2.0-30-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: LXDE Date: Wed Feb 24 14:27:55 2016 InstallationDate: Installed on 2016-02-09 (15 days ago) InstallationMedia: Lubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) PackageArchitecture: all SourcePackage: openssh UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1549473/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
