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

Bug#502444: sshd fails at boot-time following reload by /etc/network/if-up.d/openssh-server presumably due to race condition



On Tue, Jan 13, 2009 at 11:00:52PM +0100, Kevin Price wrote:
> Sorry even debug level 3 does not seem to help us any further:
> 
> Jan 13 22:52:30 leeloo3 sshd[2057]: debug2: fd 3 setting O_NONBLOCK
> Jan 13 22:52:30 leeloo3 sshd[2057]: debug1: Bind to port 22 on 0.0.0.0.
> Jan 13 22:52:30 leeloo3 sshd[2057]: Server listening on 0.0.0.0 port 22.
> Jan 13 22:52:30 leeloo3 sshd[2057]: socket: Address family not supported
> by protocol
> Jan 13 22:52:30 leeloo3 sshd[2057]: Received SIGHUP; restarting.
> 
> That's all process 2057 ever logged before dying. Is there anything else
> I can do? Please let me know what and whether to leave your patch in
> /etc/network/if-up.d/openssh-server or to revert it to original.

OK, thanks for testing. I need to get a fix in sharpish in order for it
to make lenny, so I'm going to regretfully change to 'restart' rather
than 'reload' for the time being.

I'm going to keep looking into this and trying to figure out why SIGHUP
might be failing, though. I note that both you and Tim are on amd64,
which could conceivably be relevant.

-- 
Colin Watson                                       [cjwatson@debian.org]



Reply to: