bug-guix
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#34580: Service ssh-daemon could not be started


From: Brant Gardner
Subject: bug#34580: Service ssh-daemon could not be started
Date: Tue, 24 Sep 2019 07:20:10 -0500
User-agent: Cyrus-JMAP/3.1.7-238-g170a812-fmstable-20190913v1

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" <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’.
>





reply via email to

[Prev in Thread] Current Thread [Next in Thread]