GNU bug report logs -
#34580
'ssh-daemon' fails to start
Previous Next
Reported by: Andreas Enge <andreas <at> enge.fr>
Date: Tue, 19 Feb 2019 21:22:02 UTC
Severity: important
Tags: fixed, unreproducible
Merged with 30993,
33299,
37309
Done: maxim.cournoyer <at> gmail.com
Bug is archived. No further changes may be made.
Full log
View this message in rfc822 format
I'll cheerfully do the experiment, but I don't know how - can you direct me for how to add strace where you need it to a booting system?
--
Brant Gardner
On Tue, Sep 24, 2019, at 03:08, Ludovic Courtès wrote:
> Hi Brant,
>
> "Brant Gardner" <mail <at> lnklnx.com> 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’.
>
This bug report was last modified 4 years and 222 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.