[Bug 484209] Re: /etc/init/statd.conf: race with portmap startup

[Rolf Leggewie]

karmic has seen the end of its life and is no longer receiving any
updates. Marking the karmic task for this ticket as "Won't Fix".

** Changed in: nfs-utils (Ubuntu Karmic)
       Status: Triaged => Won't Fix

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to nfs-utils in Ubuntu.
https://bugs.launchpad.net/bugs/484209

Title:
  /etc/init/statd.conf: race with portmap startup

Status in nfs-utils package in Ubuntu:
  Fix Released
Status in nfs-utils source package in Lucid:
  Fix Released
Status in nfs-utils source package in Karmic:
  Won't Fix

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/statd.conf shows that the error
  is caused by statd's pre-start script attempting to start portmap when
  it is already started.  The pre-start script tries to avoid this by
  checking portmap's status:

          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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/484209/+subscriptions