Public bug reported:

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/statd.conf{.orig,}
--- /etc/init/statd.conf.orig   2010-04-21 23:04:08.000000000 +0200
+++ /etc/init/statd.conf        2010-04-21 22:52:26.000000000 +0200
@@ -3,7 +3,7 @@
 description    "NSM status monitor"
 author         "Steve Langasek <steve.langa...@canonical.com>"
 
-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

** Affects: nfs-utils (Ubuntu)
     Importance: Undecided
         Status: New

-- 
"init: statd main process ended, respawning" upstart problem
https://bugs.launchpad.net/bugs/568082
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to