Comment 3 for bug 451556

Revision history for this message
Michael Vogt (mvo) wrote :

initctrl will give me a proper error message and report it fails to connect to socket /com/ubuntu/upstart. There are a bunch of (not critial) /etc/init.d/$daemon restart failed messages for the same reason in the logs as well.

So it looks like the upstart tools from 0.6 can not talk to the (still running) upstart 0.3 from jaunty (incompatible wire protocol on the socket). I tried to send SIGHUP to init as a workaround (simulating ctrl-alt-del) but other than a message on the console nothing happend.