Comment 8 for bug 543506

Revision history for this message
Wout (wout-bliepbliep) wrote : Re: [Bug 543506] Re: Upstart not starting jobs on boot

Thanks for the message!

I have the same spawn rc message in my logs.
I see that in /etc/init/rc.conf it mentions 'console output' which makes
upstart try to open the console.
That fails. Probably a race condition. Possibly /dev/console is not yet
available when upstart wants to start rc?

I see you have a ticket open for this so no need for me to add anything (a
relief seeing how hostile Ubuntu appears to be to bug reporting).

Kind regards,
Wout

On Sun, Apr 25, 2010 at 19:29, David <email address hidden> wrote:

> I've encountered the same problem with Mythbuntu 10.04 with all updates
> installed. I recognized it because lirc sometimes started and sometimes not.
> After some investigation I saw the following line in my syslog:
> init: Failed to spawn rc main process: unable to open console: Input/output
> error
>
> apt-cache policy upstart
> upstart:
> Installiert: 0.6.5-6
> Kandidat: 0.6.5-6
> Versions-Tabelle:
> *** 0.6.5-6 0
> 500 http://de.archive.ubuntu.com/ubuntu/ lucid/main Packages
> 100 /var/lib/dpkg/status
>
> --
> Upstart not starting jobs on boot
> https://bugs.launchpad.net/bugs/543506
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “upstart” package in Ubuntu: New
>
> Bug description:
> Binary package hint: upstart
>
> On Lucid with:
>
> # apt-cache policy upstart
> upstart:
> Installed: 0.6.5-4
> Candidate: 0.6.5-4
> Version table:
> *** 0.6.5-4 0
> 500 http://apt.interlinx.bc.ca lucid/main Packages
> 100 /var/lib/dpkg/status
>
> during boot, upstart just seems to stop starting jobs. A number of jobs
> are started but all of the jobs that should be started never gets complete.
> I end up (though having a job that starts a shell on a tty) having to
> manually:
>
> # service ssh start
> # service rc-sysinit start
> (at least)
>
> to get the system up into a semblance of a multi-user run-level.
>
> I'd be happy to provide more information but I'm at a bit of a loss as to
> how to debug this situation.
>
> FWIW, my "debug shell" job which gives me a shell that I can debug upstart
> from is:
>
> description "Start a debug shell"
>
> start on startup
>
> expect fork
>
> script
> exec /root/open -c 12 /bin/bash
> end script
>
> I have no doubt it's probably not 100% correct as I'm really only just
> cribbing it up from what I can see in other jobs. Hopefully I have not
> exacerbated the problem with that job.
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/543506/+subscribe
>