[Bug 719833] [NEW] ssh upstart job fails to actually bring up ssh
Kees Cook
kees at ubuntu.com
Wed Feb 16 07:08:25 UTC 2011
Public bug reported:
When I reboot my router, ssh does not start.
Feb 15 22:51:32 router init: ssh main process (897) terminated with status 255
Feb 15 22:51:32 router init: ssh main process ended, respawning
Feb 15 22:51:32 router init: ssh main process (915) terminated with status 255
Feb 15 22:51:32 router init: ssh respawning too fast, stopped
I do not bind to 0.0.0.0, so I must have networking up fully before ssh
can start. Because "filesystem" happens before "networking" has
started, the job fails. We might want to consider changing the upstart
job to:
start on filesystem and started networking
ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: openssh-server 1:5.5p1-4ubuntu5
ProcVersionSignature: Ubuntu 2.6.35-25.44-generic-pae 2.6.35.10
Uname: Linux 2.6.35-25-generic-pae i686
Architecture: i386
Date: Tue Feb 15 23:03:11 2011
ProcEnviron:
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: openssh
** Affects: openssh (Ubuntu)
Importance: Undecided
Status: New
** Tags: apport-bug i386 maverick
--
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/719833
Title:
ssh upstart job fails to actually bring up ssh
More information about the Ubuntu-server-bugs
mailing list