setuid error is very hard to debug

Bug #1165013 reported by Olathe
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
upstart
Confirmed
Wishlist
Unassigned

Bug Description

Using the Upstart setuid line with a nonexistent username is very, very hard to debug. No logs are generated and the incredibly uninformative error message when starting the job manually is:

start: Job failed to start

Please put a message about a nonexistent user in the job's log file.

Revision history for this message
James Hunt (jamesodhunt) wrote :

All you need to do is put Upstart into debug mode:

$ sudo initctl log-priority debug
$ sudo start foo
$ sudo dmesg|grep setuid
[ 4942.908486] init: Failed to spawn foo main process: unable to find setuid user

I've added this to the Upstart Cookbook here:

http://upstart.ubuntu.com/cookbook/#setuid

We are not logging the invalid username, hence we'll make this a wishlist item.

Changed in upstart:
importance: Undecided → Wishlist
Changed in upstart:
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.