On Wed, 20.04.11 10:01, Vasiliy G Tolstov (v.tols...@selfip.ru) wrote: > Hello. > > After upgrade to systemd-24 my sshd.socket after some time die. > > netstat -nal | grep 22 says nothing. > > systemctl status sshd.socket says: > Active: failed > Accepted: 2652 Connected:1
Can you check syslog for any message regarding sshd.socket itself? Usually you shold find a message like "foobar entered failed state" or so. > > In mesages: > > getty@tty1.service holdoff timer over, scheduling restart. > sshd@188.127.24148:22-85.142.60.148:33355.service stoping timed out. > Killing. This usually indicates a frozen process of some kind, but should not be fatal. And I presume this is stopping, not stoping? > sshd@.service contains: > ExecStart=-/usr/sbni/sshd -i > StandardInput=socket I presume that's sbin, not sbni? Lennart -- Lennart Poettering - Red Hat, Inc. _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
