initctl: debugging start should show commands run

Bug #559910 reported by Gerben on 2010-04-10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
upstart (Ubuntu)

Bug Description

Binary package hint: upstart

ubuntu server 10.04 beta amd-64

ii upstart 0.6.5-6

start <service> log-priority debug should work as described in manpage
start <service> log-priority debug should write verbose information of what is happening/executed
(or start --debug <service> should write verbose information of what is happening/executed)

I got no information at all. I needed to search all files under /etc for those files that might be involved in the service. I managed to find a file and set some options, but clearly didn't have a clue... (partly due to 'start' being new to me).

In stead of log-priority I've tried the following as well:
    -l debut --log-priority debug log-priority=debug, etc.

I've found some files under /etc/default and /etc/init to tamper with the service parameters.

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: upstart 0.6.5-6
ProcVersionSignature: Ubuntu 2.6.32-16.25-generic
Uname: Linux 2.6.32-16-generic x86_64
Architecture: amd64
Date: Sat Apr 10 11:28:46 2010
InstallationMedia: Ubuntu-Server 10.04 "Lucid Lynx" - Beta amd64 (20100317)
 PATH=(custom, no user)
SourcePackage: upstart

Gerben (gerbgeus) wrote :

There are no "log-priority" or "--debug" options for "start", I believe you have confused the man page.

There are separate commands to initctl, for example:

  initctl log-priority debug
  initctl start <service>

The first changes Upstart's logging priority, and the second starts the service; you'll see more verbose log messages in the log as a result

Changed in upstart (Ubuntu):
status: New → Invalid
Gerben (gerbgeus) wrote :

"man start" presented me with page initctl(8), I didn't realize my entry to that page. I was mixing the start command with initcl parameters.

I can see more verbose logging (syslog, debug and daemon.log), it looks to me initctl's view to all the services it it handling.

What I would like to see is a debugging session of the script being run when a service is starting. Like putting extra "-v -v -v" or "-x" to the line "#!/bin/sh -e" to the script (or shell process) starting a service to find out where it fails.

Maybe I missed some documentation in this direction?

Seem like a valid request to me, I'll add this as a wishlist to Upstart

summary: - start debug options do not work
+ initctl: debugging start should show commands run
Changed in upstart:
status: New → Triaged
importance: Undecided → Wishlist
Gerben (gerbgeus) wrote :


Not to rush anyone into anything, just to provide a possible solution and also, I don't know the complexity involved in the whole process.

Maybe it could be an idea to generate a script that in turn could be used for debugging in stead of debugging within upstart itself. upstart Collects all the basics from the /etc filesystem (e.g. sourcing of all the various scripts that come into play) to be printed over stdout. People can then debug that script using "-x -v".

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

Other bug subscribers