Am 06.08.2015 um 12:28 schrieb Thomas Schmidt: ug 06 10:43:50 9398 systemd[1]: ssh.service: Main process exited, code=exited, status=255/n/a > Aug 06 10:43:50 9398 systemd[1]: ssh.service: Unit entered failed state. > Aug 06 10:43:50 9398 systemd[1]: ssh.service: Failed with result 'exit-code'. > Aug 06 10:43:50 9398 audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=ssh comm="systemd" exe="/lib/syAug 06 10:43:50 9398 NetworkManager[2046]: <info> keyfile: new connection /etc/NetworkManager/system-connections/Wired connectiAug 06 10:43:50 9398 smartd[2415]: Device: /dev/sda [SAT], is SMART capable. Adding to "monitor" list. > Aug 06 10:43:50 9398 avahi-daemon[2379]: Service "9398" (/services/udisks.service) successfully established. > Aug 06 10:43:50 9398 systemd[1]: ssh.service: Service hold-off time over, scheduling restart. > Aug 06 10:43:50 9398 audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=ssh comm="systemd" exe="/lib/sAug 06 10:43:50 9398 audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=ssh comm="systemd" exe="/lib/syAug 06 10:43:50 9398 systemd[1]: ssh.service: Start request repeated too quickly. > Aug 06 10:43:50 9398 systemd[1]: Failed to start OpenBSD Secure Shell server. > -- Subject: Unit ssh.service has failed > -- Defined-By: systemd > -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel > -- > -- Unit ssh.service has failed. > -- > -- The result is failed. > It looks like ssh service is restarted too often within a short period of time due to some external process (most likely the if-up.d hook). Therefor systemd marks the service as failed, it's not that systemd kills ssh-server. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
Attachment:
signature.asc
Description: OpenPGP digital signature