Services don't start on boot after Upstart update

Bug #511387 reported by Lars Ola Liavåg
34
This bug affects 6 people
Affects Status Importance Assigned to Milestone
upstart (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: upstart

Running on a freshly installed 32-bit Karmic, I've got the same symptoms as in bug #497299. After boot, pulseaudio is the only service that runs. Manually running sudo modprobe vboxdrv will allow me to use my VM's and sudo service cups start will let me print again.

The workarounds reported for bug #497299 don't work for me. I've got a correct /etc/network/interfaces file and sudo initctl list says that "network-interface (lo) start/running". Downgrading Upstart to 0.6.3.10 doesn't work either. Not even the Upstart update that came today helped.

I see other people have the same thing but was instructed to open a separate bug for it. What can I provide to help debugging?

Revision history for this message
pnoewbe (muckblit) wrote :

lucid 10.04 (beta 2 or so)

upstart 0.6.3-11build1

runlevel shows "N 2" but no eth0 or dbus or expected daemons from /etc/init.d sysvinit.

I didn't learn anything from logs or /etc/init.d upstart scripting.

I reinstalled upstart and its deps. initscripts sysv-rc sysvinit-utils mountall upstart ureadahead libdbus-1-3 libudev0

Now this is really weird. I had just used the same install iso to install to two usb keys before this one, and did not have the problem! Too many variables to help then, but another instance of the problem and there are other bug threads on this or similar. Some might be distinctly diff bug reports since they have an unknown runlevel.

I don't have pulseaudio or gstreamer, can't, and dbus won't start manually. Sometimes ck-launch-session can't run, and startxfce4, and kdm and gdm can never run or take over the tty. Maybe those are dbus related. There is no dbus socket in /var/run/dbus and that crashes many apps.

I have another desktop running upstart 0.6.3-11 without the problem. Hmm.

Revision history for this message
Christopher (soft-kristal) wrote :

This issue was also reported in bug 495726 where cups has to be manually started with every boot. It affects some Karmic distributions (not mine) and Lucid in mine.

Revision history for this message
Lars Ola Liavåg (l-liavag) wrote :

Finally, somebody stumbled across a solution that worked also for me (http://ubuntuforums.org/showthread.php?p=8728987&posted=1#post8728987). The trick was to stop using CONCURRENCY=shell in /etc/init.d/rc and instead revert to CONCURRENCY=none.

But honestly, CONCURRENCY=shell is a long-running trick for speeding up boot on multi-core processors. I've even seen it in printed books in shops. And before applying it on my Karmic install (I've used it since Hardy), I did make sure the various web pages giving speed-tweak hints were still recommending it. And after all, it did work fine until around the time when Upstart 0.6.3-11 came. Downgrading Upstart didn't help me, though, so maybe one of the other updates around that time is what broke my system.

I think somebody should follow up this a bit still.

Revision history for this message
Christopher (soft-kristal) wrote :

I installed the Boot Manager and saw cups was not being loaded. It seems OK now; loading on boot.

Revision history for this message
fable (fable) wrote :

When I noticed the problem, I looked for /etc/init.d/rc
but the line CONCURRENCY=none
was already there.

(upstart/lucid uptodate 0.6.5-6)

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.