I'm getting something that sounds a lot like this bug in 12.04 LTS Server - I
have a dual interface home server with 2 nics. ssh, xinetd, and
isc-dhcp-server all fail to work correctly on boot and need to be restarted.
All 3 also have custom configurations for binding to one nic or the other.
This sounds a lot like what happened to me when the fix for this
defect was released:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/687535
I had to roll back to 5.3p1-3ubuntu4 to be able to restart Xen based
Lucid instances and have sshd restart reliably.
--
You received this bug
** Changed in: openssh (Ubuntu)
Status: Triaged = Fix Committed
--
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
reversed a mistake at the request of John Seeger
** Changed in: openssh (Ubuntu)
Status: Fix Committed = Triaged
--
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:
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
** Changed in: openssh (Ubuntu)
Importance: Undecided = Medium
** Changed in: openssh (Ubuntu)
Status: New = Triaged
--
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
--
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
--
Ubuntu-server-bugs mailing list
