"init: statd main process ended, respawning" upstart problem
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
nfs-utils (Ubuntu) |
Incomplete
|
Undecided
|
Unassigned | ||
Bug Description
statd fails to start during upstart with following messages:
$ fgrep statd /var/log/boot.log
init: statd main process (937) terminated with status 1
[...]
init: statd main process ended, respawning
init: statd main process (1036) terminated with status 1
init: statd respawning too fast, stopped
The following change fixes the issue:
$ diff -u /etc/init/
--- /etc/init/
+++ /etc/init/
@@ -3,7 +3,7 @@
description "NSM status monitor"
author "Steve Langasek <email address hidden>"
-start on (started portmap or mounting TYPE=nfs)
+start on ((started portmap or mounting TYPE=nfs) and stopped networking)
stop on stopping portmap
expect fork
NB: I'm not sure if I understand it right, but the "stopped networking" condition seems to make upstart wait until all network interfaces are up before starting the service. Can someone confirm this?
Note that I have no NFS mount in /etc/fstab. NFS is mounted via autofs (for partitions that are NOT needed during the boot process).
$ lsb_release -rd; uname -a
Description: Ubuntu lucid (development branch)
Release: 10.04
Linux ced-workstation 2.6.32-21-generic #32-Ubuntu SMP Fri Apr 16 08:09:38 UTC 2010 x86_64 GNU/Linux
$ apt-cache policy nfs-common
nfs-common:
Installed: 1:1.2.0-4ubuntu4
Thank you for taking the time to report this bug and help to improve Ubuntu.
The proposed change is wrong, rpc.statd doesn't require the network to be up before it starts. Do you happen to have your /var on a separate filesystem?