Actually I remember it now - the /etc/hosts file was busted, I think to the effect that 127.0.0.1 pointed to some other host, not localhost, not the machine's name. this was due to an error in cfengine at a site, and another time was due to a configuration error from someone changing the hostname improperly. Apache had issues restarting, and the upgrade broke because of it - fix apache, then the upgrade went smoothly.
thanks dave Dave Kempe wrote: > Perhaps apache was already stopped? > haven't tried it myself with this one, but have found in the past that > if apache had an invalid config, upgrades might not work > > dave > > Michael Vogt wrote: >> Removing apache2-common ... >> * Stopping apache 2.0 web server... >> * Stopping apache 2.0 web server... >> >> * Stopping apache 2.0 web server... >> [fail] >> invoke-rc.d: initscript apache2, action "stop" failed. >> dpkg: error processing apache2-common (--remove): >> subprocess pre-removal script returned error exit status 1 >> Errors were encountered while processing: >> apache2-common >> > > > -- ubuntu-server mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
