We did as described above, and the log files did not yield any helpful information. My next step is to revert back to openssh_5.3p1-3ubuntu4, since that seemed to be reliable.
As for the fact that this didn't show up in any testing prior to committing the patch, I would point out that, just like Jan above, our instances are running as Xen guests (since we're running in EC2). So perhaps that has something to do with it. I can't tell from the bug comments, but I'm curious as to whether or not these sort of changes get tested in a Xen based environment. My guess is that their not, at least not consistently. -- 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 -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
