1) analysis: this is what is going wrong w.r.t. nfs-utils during
shutdown

# the script S20sendsigs in  /etc/rc0.d/ is run
->  the call to killall5 -15 ... kills rpc.statd

# at the same time upstart tries to keep rpc.statd alive due to "respawn" in 
/etc/init/statd.conf
-> rpc.statd is restarted

These two conflicting actions repeat at least two times due to
S20sendsigs containing multiple killall5 invocations. Maybe more often
when upstart does all this in parallel.

2) possible solutions (I know too less to get this right myself, but
post three suggestions)

a) if rpc.statd is needed as long as S31umountnfs.sh has not yet been run
  then it should be protected from the killall5 like portmap is 
(/lib/init/rw/sendsigs.omit.d/portmap)

b) if rpc.statd is no longer needed at that time it should get a statement like
   "stop on (stopping portmap or runlevel [06])" 
  in /etc/init.statd.conf
  so that it is no longer present when S20sendsigs runs

c) or, maybe, the respawn mechanism of upstart should be deactivated
before running S20sendsigs


** Summary changed:

- message at least two times during system shutdown: "statd main process ended" 
"respawning"
+ rpc.statd is killed and restarted during shutdown multiple times

** Description changed:

+ the following message appears during system shutdown at least two times:
+ "statd main process ended" "respawning"
+ 
  this looks like some inconsistency in the upstart configuration of nfs-
  common
  
  ProblemType: Bug
  Architecture: i386
  Date: Mon Nov  9 13:56:30 2009
  DistroRelease: Ubuntu 9.10
  NonfreeKernelModules: fglrx
  Package: nfs-common 1:1.2.0-2ubuntu8
  ProcEnviron:
-  LANGUAGE=
-  PATH=(custom, user)
-  LANG=de_DE.UTF-8
-  SHELL=/bin/bash
+  LANGUAGE=
+  PATH=(custom, user)
+  LANG=de_DE.UTF-8
+  SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
  SourcePackage: nfs-utils
  Uname: Linux 2.6.31-14-generic i686

-- 
rpc.statd is killed and restarted during shutdown multiple times
https://bugs.launchpad.net/bugs/479137
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