[Bug 1154040] Re: Upgrading to 1.7 on raring caused system to crash

[James Hunt]

The problem might be related to the root filesystem being mounted ro
(although Jonathan is making dpkg remount the FS rw (see
http://wiki.debian.org/ReadonlyRoot#Make_apt-get_remount_.2F_if_needed).
That said, problem is not now reproducible even with same kernel +
package upgrade scenario.

Problem may actually be a kernel issue (nuls in syslog look suspicious)
although difficult to say at this stage due to lack of meaningful log
info.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to upstart in Ubuntu.
https://bugs.launchpad.net/bugs/1154040

Title:
  Upgrading to 1.7 on raring caused system to crash

Status in “upstart” package in Ubuntu:
  New

Bug description:
  Upgrading Upstart from 1.6.1-1ubuntu3 → 1.7-0ubuntu1 caused a system
  to crash (happened twice to me now). The system required a hard reboot
  to start again.

  There was nothing on the console, and the last thing I saw via SSH
  was:

  "Install new configuration file /etc/dbus-1/system.d/Upstart.conf..."

  Brief IRC chat about this:

  < jpds> Because that's twice it's happened to me.
  < Laney> killing how?
  < jpds> Laney: As in, it needs a hard reboot to come back.
  < jpds> Last thing I see is: "Install new configuration file /etc/dbus-1/system.d/Upstart.conf..."
  < infinity> Re-execing it is ending in sadness?
  < jpds> infinity: Well, this was done over SSH, and everything just stopped.
  < infinity> jpds: Over SSH makes things a bit scarier.  I was about to ask you to try running "telinit u" to see if it does the same thing.  But the same thing sounds undesirable. :P
  < jpds> infinity: Well, the first time it happened (on my laptop), I couldn't get any response out of it.
  < jpds> Now the same thing happened on my desktop.
  < infinity> jpds: Right, I gathered that.  I was asking if you could run "telinit u" on one of the affected systems after a reboot.
  < infinity> jpds: To isolate if it's a consistent issue with your machines/setup, or if it's isolated to only happening during upgrade (which is still bad, but different).
  < jpds> infinity: Nothing happened running "telinit u" on my laptop.
  < infinity> (as root)
  < jpds> Yep.
  < infinity> And "initctl version" confirms that it's 1.7ish?
  < jpds> Yes.
  < infinity> Alright.  Then upstart's postinst may be doing something curiously silly.
  < jpds> Upstart went from 1.6.1-1ubuntu3 → 1.7-0ubuntu1.
  < infinity> My assumption is that your locking up was actually a kernel panic because init died.
  < infinity> The kernel hates init going away.
  < infinity> But, of course, that's really not meant to happen.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1154040/+subscriptions