how to trace upstart scripts at boot

Asked by Marc Zonzon on 2010-05-25

I had a bad bug within mountall (just reported as, and I have had a very hard time to find which upstart init script was faulty. I would have needed to know which script begin and end, and I have found no way to get this on log (except add some lines in each conf file!).
In this case it would also be very important to serialise the start of scripts, to be able to reproduce the bug.

Moreover my bug (see report) was occurring only on standard boot but not by doing the init on a shell and launching upstart afterward so making impossible to watch init from a console as advised on the Upstart Debugging page in the wiki.

Can you tell if there is any way to trace the global activity of upstart at boot.

Question information

English Edit question
Needs information
upstart Edit question
No assignee Edit question
Last query:
Last reply:
Daniel (hackie) said : #1

Ich have the same problem. Not the bug Marc mentioned, but the upstart debugging issue. Since my update to precise, 3.2.0-kernels don't boot, my system freezes while booting. And one of 100 upstart jobs is causing the freeze. I modified upstart a bit to have a 10 second sleep after each job start. This seems to work good for debugging, but something changes the log level or output of upstart after mounting the file systems and I still can't see which job causes the kernel to freeze.

Someone here to give more help?

I have this debugging problem too.

Can you help with this problem?

Provide an answer of your own, or ask Marc Zonzon for more information if necessary.

To post a message you must log in.