/etc/init/statd.conf: race with portmap startup
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
nfs-utils (Ubuntu) |
Fix Released
|
Medium
|
Steve Langasek | ||
Karmic |
Won't Fix
|
Undecided
|
Unassigned | ||
Lucid |
Fix Released
|
Medium
|
Steve Langasek |
Bug Description
On my system (a Xen virtual machine running karmic and acting as an NFS client), I see the following during boot:
init: statd pre-start process (831) terminated with status 1
mountall: Event failed
Enabling console output in /etc/init/
status portmap | grep -q start/running || start portmap
However adding debug statements showed that portmap's status at this point was "start/spawned" rather than "start/running". I.e. portmap was already in the process of being started but was not yet "running".
Simply changing that line to
status portmap | grep -q start/ || start portmap
solved the problem for me.
Changed in nfs-utils (Ubuntu Karmic): | |
status: | New → Triaged |
Confirmed, there's a race condition here. The race-free fix would be:
start portmap || true
status portmap | grep -q start/running