init: failed exec() and "expect" cause hang or missing pid
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| upstart |
Triaged
|
Medium
|
Unassigned | ||
| upstart (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Bug Description
Binary package hint: upstart
Trying to start the attached sample upstart job results in a status of 'started/running', but with no PID.
Ran into this in the gssd job, which on my system unavoidably races the mounting of /usr since NFS mounts will be attempted in parallel to local filesystem mounts, and rpc.gssd sits on /usr. Will work around this in the gssd job (after reviewing, I don't see any reason to have a 'script' here instead of exec'ing directly, which fixes the problem that upstart doesn't see the exec() failure).
ProblemType: Bug
Architecture: amd64
Date: Tue Mar 23 19:16:47 2010
DistroRelease: Ubuntu 10.04
Package: upstart 0.6.5-5
ProcEnviron:
PATH=(custom, user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSign
SourcePackage: upstart
Uname: Linux 2.6.32-16-generic x86_64
| Steve Langasek (vorlon) wrote | #1 |
| Steve Langasek (vorlon) wrote | #2 |
| Scott James Remnant (Canonical) (canonical-scott) wrote | #3 |
| summary: |
- 'expect fork'+'respawn'+script+ENOENT => start/running w/o PID + init: failed exec() and "expect" cause hang or missing pid |
| Changed in upstart (Ubuntu): | |
| status: | New → Invalid |
| Changed in upstart: | |
| status: | New → Triaged |
| importance: | Undecided → Medium |
The funny thing is that I have this one written down in my notes, but never filed a bug for it. Thanks