ssh upstart job fails to actually bring up ssh
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
openssh (Ubuntu) |
Triaged
|
Medium
|
Unassigned |
Bug Description
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
ProcVersionSign
Uname: Linux 2.6.35-
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
Changed in openssh (Ubuntu): | |
importance: | Undecided → Medium |
status: | New → Triaged |
Changed in openssh (Ubuntu): | |
status: | Triaged → Fix Committed |
Actually, this goes even further. All services that have the possibility not bind to 0.0.0.0 should only be started after the last network interface is up. I'm on a machine with 10 IP addresses and have to use something like
start on (filesystem
and net-device-up IFACE=venet0:8)
in squid.conf and ssh.conf.
That's gonna be a tricky one.