I've been unable to reproduce this, but there are a ton of duplicates so there is no doubt that there is something wrong with the lucid updates.
I actually think this is directly related to bug #736348 . By calling 'restart' directly, we are not re-loading the new job file. So until the system is rebooted, squid will still be run with 'expect fork' and without -N. I am suspicious that this is just exposing *more* issues with the way that squid forks, since the bug we were originally trying to fix involves how squid handles SIGHUP, its conceivable that it handles SIGTERM in a way that is incompatible w/ upstart's expect fork as well. I'm not ready to mark this as a duplicate of that bug, but I think it may be. I'm hoping somebody can provide us with some more information regarding the state of their system *before* the upgrade, that may suggest what state causes the restart to fail. In the mean time, it makes sense to get that fix into natty for testing, especially as people start to try natty out as it approaches beta. It also seems at least one person has hit upstart bug #406397 , which also suggests further that this is caused by mixing expect fork with daemons that don't fork in the way upstart suggests. Unfortunately that is a particularly nasty bug whose only workaround is to make a program that forks until the pid that has gone missing can be recreated. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/729288 Title: squid failed to restart after update to squid 2.7.STABLE7-1ubuntu12.2 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
