[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#34580: Service ssh-daemon could not be started
From: |
Ludovic Courtès |
Subject: |
bug#34580: Service ssh-daemon could not be started |
Date: |
Tue, 24 Sep 2019 10:08:22 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/26.3 (gnu/linux) |
Hi Brant,
"Brant Gardner" <address@hidden> skribis:
> The most useful thing I could find in the logs:
>
> Sep 19 15:30:46 localhost sshd[261]: Server listening on 0.0.0.0 port 22.
> Sep 19 15:31:19 localhost shepherd[1]: Service ssh-daemon could not be
> started.
> Sep 19 15:39:58 localhost sshd[585]: Server listening on 0.0.0.0 port 22.
> Sep 19 15:39:58 localhost sshd[585]: Server listening on :: port 22.
> Sep 19 15:39:59 localhost shepherd[1]: Service ssh-daemon has been started.
As I witnessed before, it looks as though ‘sshd’ initially hanged while
trying to bind on the IPv6 address.
So I wonder if we’re just sometimes starting sshd a bit too early
wrt. to some IPv6 networking initialization, or something. It’d be
great to have the strace output when that happens.
Thanks,
Ludo’.
- bug#34580: Service ssh-daemon could not be started, Brant Gardner, 2019/09/20
- bug#34580: Service ssh-daemon could not be started,
Ludovic Courtès <=
- bug#34580: Service ssh-daemon could not be started, Brant Gardner, 2019/09/24
- bug#34580: Service ssh-daemon could not be started, Ludovic Courtès, 2019/09/26
- bug#34580: Service ssh-daemon could not be started, Brant Gardner, 2019/09/27
- bug#34580: Service ssh-daemon could not be started, Ludovic Courtès, 2019/09/28
- bug#34580: Service ssh-daemon could not be started, Brant Gardner, 2019/09/28
- bug#34580: Service ssh-daemon could not be started, pelzflorian (Florian Pelz), 2019/09/28
- bug#34580: Service ssh-daemon could not be started, Ludovic Courtès, 2019/09/28
- bug#34580: Service ssh-daemon could not be started, Danny Milosavljevic, 2019/09/28
- bug#34580: Service ssh-daemon could not be started, Danny Milosavljevic, 2019/09/28
- bug#34580: Service ssh-daemon could not be started, Ludovic Courtès, 2019/09/28