[Bug 687535] Re: upstart loses track of ssh daemon after reload ssh

[Clint Byrum]

On Wed, 2011-02-23 at 05:19 +0000, gorism wrote:
> I just updated to the openssh-server_5.3p1-3ubuntu5 package for a Lucid
> instance, and now I can't get SSH to start.  Or, rather, I'm running
> into what Jan mentioned above, with the respawning/terminating loop that
> eventually results in init deciding that SSH isn't going to start, and
> giving up.  Something like:
> 
> init: ssh main process (430) terminated with status 255
> init: ssh main process ended, respawning
> init: ssh main process (449) terminated with status 255
> init: ssh main process ended, respawning
> init: ssh main process (456) terminated with status 255
> init: ssh main process ended, respawning
> ...
> init: ssh main process (468) terminated with status 255
> init: ssh respawning too fast, stopped
> 
> The real trouble here is, this is an EC2 instance that was just
> restarted, so now I have no means by which I can get on that machine to
> do any additional troubleshooting or ultimately fix this.  But this was
> not caused by me executing an /etc/init.d/ssh stop, so I don't think
> this is bug #531912.
> 

If you restarted the instance and this is happening, its definitely not
bug #531912, as that one still results in an sshd that works on bootup.

If this is an EBS root instance, can you snapshot it and mount it from
another instance? If so, you should be able to view the contents
of /var/log and paste any errors from sshd. If you can't find anything
there, you can mount the  volume r/w and add 'console output'
to /etc/init/ssh.conf and then check the console output when it fails to
start up.

If its fully instance store, I'm not sure there's much you can do though
EC2 experts may have some tricks.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in ubuntu.
https://bugs.launchpad.net/bugs/687535

Title:
  upstart loses track of ssh daemon after reload ssh