Comment 15 for bug 717397

Revision history for this message
Tim Nicholas (tjn) wrote :

This fix appears to have broken the upgrade process.

On two systems, it ended up failing to finish the upgrade. After killing the upgrade processes I was unable to stop the still running squid using 'service squid stop' or 'stop squid' or '/etc/init.d/squid stop' or anything else.

After that I couldn't do anything with squid as it was in a 'stop/killed' (with a PID that doesn't exist). See bug: https://bugs.launchpad.net/upstart/+bug/406397

Can I suggest an upgrade to this crazy new init system I've heard of called 'System V'. It sounds badass. And reliable/predictable.

Also, any hints as to starting the daemon without rebooting would be appreciated.