Comment 9 for bug 506727

Hmm, well, as well as not being able to startup. I also find I can not shutdown!

I can switch to a console and press ctrl-alt-del and (I exec'd init
with -v --debug) see a lot of messages fly by; and then something
stops upstart from proceeding to shutdown the system.

Likewise I can press the power button, a lot of message and the system
is still operational.

It seems that upstart is waiting for some kind of lock / event to
occur before allowing the shutdown to finish. My guess is that the
same lock is preventing successful startup.

I am stumped asto how to debug this at all; I'm not even able to log
the messages that upstart sends out. Redirection does not seem to be
working from the point of sulogin.

Is there a logging option, or anything further I can use?

Thanks,
Anand

On Tue, Jan 19, 2010 at 2:06 PM, Johan Kiviniemi
<email address hidden> wrote:
> Nothing so far indicates you’re encountering a bug in Upstart.
>
> The problem seems to lie with something in Ubuntu that’s supposed to get
> the lo interface up properly. Upstart’s upstream code has nothing to do
> with this.
>
> --
> upstart fails to start system into multiuser mode
> https://bugs.launchpad.net/bugs/506727
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in NULL Project: Invalid
> Status in Ubuntu: Confirmed
>
> Bug description:
>
> Unfortunately I am not able to get upstart to start my system.
>
> Initially this was because of #505530, but with the supplied patch applied, mountall succeeds and I am no longer dropped into 'mountall-shell.conf'
>
> Instead the system boots, Upstart runs but it never gets to the point where it goes to runlevel 2 (i.e. start rc RUNLEVEL=2).
>
> Unfortunately I do not know of any way I can capture the output of '/sbin/init -v --debug' (which might have some clues); even booting the system with 'init=/bin/bash' and then trying to redirect things does not work.
>
> The only way I have been able to bring my system up is by:
>  - booting with 'init=/bin/bash'
>  - modifying /etc/init/mountall.conf and placing in its 'post-script script' the line 'start tty2'
>  - logging in and running X (manually in failsafe mode, normal mode does not work).
>
> The kernel version is 2.6.32-9-generic (2.6.32-10-generic fails to boot) and upstart is 0.6.3-11
>
> What would be really useful is a command line option to tell you what upstart (init) would run, in what order, but not actually do it. What would also be useful is something to indicate which jobs had already been run.
>
> Any debugging assistance would be greatly appreciated.
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/null/+bug/506727/+subscribe
>
>