package nfs-common 1:1.1.4-1ubuntu1 failed to install/upgrade: subprocess post-installation script returned error exit status 1

I am confirming the issue. My output:

$ apt-get install nfs-common

...

Setting up nfs-common (1:1.1.4-1ubuntu1) ...

Creating config file /etc/idmapd.conf with new version

Creating config file /etc/default/nfs-common with new version
Adding system user `statd' (UID 111) ...
Adding new user `statd' (UID 111) with group `nogroup' ...
Not creating home directory `/var/lib/nfs'.
 * Starting NFS common utilities [fail]
invoke-rc.d: initscript nfs-common, action "start" failed.
dpkg: error processing nfs-common (--configure):
 subprocess post-installation script returned error exit status 1
Processing triggers for libc6 ...
ldconfig deferred processing now taking place
Errors were encountered while processing:
 nfs-common
E: Sub-process /usr/bin/dpkg returned an error code (1)

$ sudo apt-get -f install
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 36 not upgraded.
1 not fully installed or removed.
After this operation, 0B of additional disk space will be used.
Setting up nfs-common (1:1.1.4-1ubuntu1) ...
 * Starting NFS common utilities [fail]
invoke-rc.d: initscript nfs-common, action "start" failed.
dpkg: error processing nfs-common (--configure):
 subprocess post-installation script returned error exit status 1
Errors were encountered while processing:
 nfs-common
E: Sub-process /usr/bin/dpkg returned an error code (1)

$ sudo dpkg --configure -a
Setting up nfs-common (1:1.1.4-1ubuntu1) ...
 * Starting NFS common utilities [fail]
invoke-rc.d: initscript nfs-common, action "start" failed.
dpkg: error processing nfs-common (--configure):
 subprocess post-installation script returned error exit status 1
Errors were encountered while processing:
 nfs-common

$ apt-cache policy nfs-common
nfs-common:
  Installed: 1:1.1.4-1ubuntu1
  Candidate: 1:1.1.4-1ubuntu1
  Version table:
 *** 1:1.1.4-1ubuntu1 0
        500 http://archive.ubuntu.com jaunty/main Packages
        100 /var/lib/dpkg/status

$ lsb_release -rd
Description: Ubuntu jaunty (development branch)
Release: 9.04

In case anyone finds it interesting:

$ sudo rpc.statd -F
Cannot register service: RPC: Unable to receive; errno = Connection refused
: unable to register (statd, 1, udp).

And, not surprisingly:

$ sudo mount -t nfs myserver.local:/ /tmp/MYSERVER/
mount.nfs: rpc.statd is not running but is required for remote locking.
mount.nfs: Either use '-o nolock' to keep locks local, or start statd.

Mind you, again not surprisingly:

$ sudo mount -t nfs -o nolock myserver.local:/ /tmp/MYSERVER/
noel@jaunt...

I am wondering if the underlying cause isn't the issue raised by Bryce in Bug 305589.

Thomas, something changed today. I just did an install of another package, and this happened at the end:

 Setting up nfs-common (1:1.1.4-1ubuntu1) ...
  * Starting NFS common utilities [ OK ]

 Setting up mozilla-noscript (1.8.2.1-1ubuntu1) ...

 # ps auxwww | grep rpc
 statd 4398 0.0 0.0 10300 808 ? Ss 19:08 0:00 /sbin/rpc.statd
 root 12925 0.0 0.0 7488 912 pts/0 R+ 21:28 0:00 grep rpc

Can you check on your end, too?

Unfortunately, when doing the mount, I get:

Dec 19 21:56:40 jaunty kernel: [10094.988161] rpcbind: server localhost not responding, timed out
Dec 19 21:56:40 jaunty kernel: [10094.988205] RPC: failed to contact local rpcbind server (errno 5).
Dec 19 21:56:52 jaunty kernel: [10106.791657] RPC: failed to contact local rpcbind server (errno 512).
Dec 19 21:56:52 jaunty kernel: [10106.791718] RPC: failed to contact local rpcbind server (errno 5).
Dec 19 21:56:52 jaunty kernel: [10106.791770] RPC: failed to contact local rpcbind server (errno 5).

also:

Dec 19 21:37:06 jaunty kernel: [ 8920.968410] RPC: failed to contact local rpcbind server (errno 93).

But first things first ... are you seeing this thing think that it has updated now?

Yeah, once you get past this one, see Bug 306016.

Hi there,

It works fine for me now. Can you try:

root# apt-get install libntfs-3g-dev libntfs-3g31 libntfs-dev libntfs10 ; apt-get build-dep libntfs-3g-dev libntfs-3g31 libntfs-dev libntfs10 ; dpkg-reconfigure libntfs-3g-dev libntfs-3g31 libntfs-dev libntfs10 ; apt-get install nfs-common ; apt-get build-dep nfs-common ; dpkg-reconfigure nfs-common

After that you can create a mount point for your ntfs share: System > Administration > NTFS Configuration Tool

Enable internal and external devices.

After that, try and go to /media and right-click your nfs-share. Now create a mount point for this too. After that it just worked for me (before I even installed nfs-common!).

Anyway,

that is just what I experienced.

Cheers,

Thomas

Thomas,

I didn't have to do any of that. As you recall, nfs-common would not properly configure, despite multiple attempts. Then last night when I installed something else, all of a sudden, nfs-commons configured. Looking at the dpkg.log, I don't see anything that explains the change, but it dpkg --configure finally succeeded. At this point, my best guess is that it might have required a reboot, because nothing else was installed and/or configured that explains the change. If you think on the past day, does this match what you experienced?

Cannot reproduce anymore ... let's see if anyone else encounters it.

I am having exactly the same problem trying to upgrade from 8.09 to 9.04.

I have even tried purging nfs-common and nfs-kernel-server and then installing fresh ...

sudo dpkg --configure -a
Setting up nfs-common (1:1.1.4-1ubuntu1) ...
ucf: The Source directory is /usr/share/nfs-common/conffiles
ucf: The State directory is /var/lib/ucf
The hash file exists
egrep [[:space:]]\/etc\/idmapd\.conf$ /var/lib/ucf/hashfile
3e94f238294cc61b047e7ae50115dffc /etc/idmapd.conf
ucf: The Source directory is /usr/share/nfs-common/conffiles
ucf: The State directory is /var/lib/ucf
The hash file exists
dpkg: error processing nfs-common (--configure):
 subprocess post-installation script returned error exit status 128
dpkg: dependency problems prevent configuration of nfs-kernel-server:
 nfs-kernel-server depends on nfs-common (>= 1:1.0.8-1); however:
  Package nfs-common is not configured yet.
dpkg: error processing nfs-kernel-server (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 nfs-common
 nfs-kernel-server

I am having the same problem. nfs-common utilities failed to install because "Starting NFS common utilities" fails to start.

The only thing that I did non-standard was hard code a static IP for eth0 with ifconfig in /etc/init.d/networking and added a default route for my gateway. Could this problem be related to this?

Given that the init script has been entirely replaced with a set of upstart jobs in karmic, I believe this bug is resolved. If anyone is still seeing package installation failures with Ubuntu 9.10 beta, please open a separate bug report.