On Fri, 2011-02-04 at 09:57 -0500, Tong Sun wrote: > Package: nfs-common > Version: 1:1.2.2-4 > Severity: important > > Symptom: > > The nfs-common failed to be installed properly: > > $ sudo apt-get install nfs-common > Reading package lists... Done > Building dependency tree > Reading state information... Done > The following NEW packages will be installed: > nfs-common > 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. > Need to get 250 kB of archives. > After this operation, 676 kB of additional disk space will be used. > Get:1 http://cdn.debian.net/debian/ testing/main nfs-common amd64 1:1.2.2-4 [250 kB] > Fetched 250 kB in 6s (41.4 kB/s) > Selecting previously deselected package nfs-common. > (Reading database ... 59010 files and directories currently installed.) > Unpacking nfs-common (from .../nfs-common_1%3a1.2.2-4_amd64.deb) ... > Processing triggers for man-db ... > Setting up nfs-common (1:1.2.2-4) ... > > Creating config file /etc/idmapd.conf with new version > > Creating config file /etc/default/nfs-common with new version > Starting NFS common utilities: statd failed! > invoke-rc.d: initscript nfs-common, action "start" failed. > dpkg: error processing nfs-common (--configure): > subprocess installed post-installation script returned error exit status 1 > configured to not write apport reports > Errors were encountered while processing: > nfs-common > > Launching it manually get the same error as well: > > % invoke-rc.d nfs-common start > Starting NFS common utilities: statd failed! > invoke-rc.d: initscript nfs-common, action "start" failed. > > The whole execution log of > > sudo bash -x /etc/init.d/nfs-common start > > is posted at http://pastebin.com/SQefWNQs > > On the surface, the reason of failure is the failure of > > statd+ start-stop-daemon --start --oknodo --quiet --exec /sbin/rpc.statd > -- > + RET=1 > > The symptom is confirmed as well by Dr. Ed Morbius, Chief Scientist, > Krell Power Systems Unlimited. See > http://thread.gmane.org/gmane.linux.debian.user/399917 > > The real reason is that the post install process of nfs-common > didn't deal with portmap: What do you mean, 'didn't deal with portmap'? nfs-common depends on portmap | rpcbind, so one of them must be installed before it and will also be started automatically. Did you disable portmap? > $ grep portmap /etc/runlevel.conf || echo not found > not found [...] What is runlevel.conf? Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse.
Attachment:
signature.asc
Description: This is a digitally signed message part