Ask Ubuntu is a question and answer site for Ubuntu users and developers. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

This question already has an answer here:

I'd like to be able to debug the execution order of the jobs started by Upstart (ideally without injecting dumping code into every job file). How can I do this?

share|improve this question

marked as duplicate by Eric Carvalho, Charles Green, v2r, Rohith Madhavan, mikewhatever Jan 1 '15 at 20:38

This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.

up vote 5 down vote accepted

Boot your system adding '--debug' to the grub command line, and once the system has booted, look at your system log file (for example '/var/log/syslog' on modern versions of Ubuntu). This will give you information on events emitted and jobs changing state. Here's an example of the format:

See also:

share|improve this answer

Run initctl2dot command and view the with your favorite Graphviz dot viewer it outputted for nice graphical view on how the system boots.

share|improve this answer
Further info on this approach is here:… – Elder Geek Aug 6 '14 at 20:41

/var/log/boot.log should give you some indication about when jobs are firing but you might want to change the logging verbosity at boot so you can better see things.

There's more about that and other techniques on Upstart's Debugging page.

share|improve this answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.