Comment 5 for bug 504776

Revision history for this message
K-B (debinix) wrote :

I tried to confirm the 'race-free fix' in nfs-utils 1:1.2.0-2ubuntu9 (which is not released for karmic) - see bug #484209.

        start portmap || true
        status portmap | grep -q start/running

I added one logger debug line, after the first line in /etc/init/statd.conf (see below)
=============================================================================
# statd - NSM status monitor

start on (started portmap or mount TYPE=nfs)
stop on stopping portmap

expect fork
respawn

env DEFAULTFILE=/etc/default/nfs-common

pre-start script
 if [ -f "$DEFAULTFILE" ]; then
     . "$DEFAULTFILE"
 fi

 [ "x$NEED_STATD" != xno ] || { stop; exit 0; }

 start portmap || true
 status portmap | logger -p local0.debug -t NFS
 status portmap | grep -q start/running
 exec sm-notify
end script

script
 if [ -f "$DEFAULTFILE" ]; then
     . "$DEFAULTFILE"
 fi

 if [ "x$NEED_STATD" != xno ]; then
  exec rpc.statd -L $STATDOPTS
 fi
end script
=======================================================================
Then a restart of the system.
In /var/log/debug:
Jan 17 13:46:08 odin NFS: portmap start/running, process 836
--> no screen error message, but NO working NFS mount either.

Then I tried to get the system back to the original state, aka re-install network-manager, and enable avahi-daemon in /etc/default/avahi-daemon (AVAHI_DAEMON_DETECT_LOCAL=1). These package/new install actions requires 'restart'.

In var/log/debug:
Jan 17 13:58:14 odin NFS: portmap start/spawned, process 816
Jan 17 13:58:15 odin NFS: portmap start/running, process 845
--> Original set of error messages on screen, but WORKING NFS mount.

another restart system directly after above.
In var/log/debug:
Jan 17 14:02:13 odin NFS: portmap start/running, process 846
--> no screen error messages, but NO working NFS mount either.

Definitely we are close, but I can not prove that the fix solves my problem. The behavior is consistent, the bug is in some way related to occasions when a reboot is required. Directly following, the first restart my system mounts OK, but not any following restarts. The error messages are not consistent as reported before (bug #504224)