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
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:
$ grep portmap /etc/runlevel.conf || echo not found
not found
I.e., the portmap is not enabled by default as the daemon.
Kernel: Linux 2.6.36-grml64 (SMP w/1 CPU core; PREEMPT)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Versions of packages nfs-common depends on:
ii adduser 3.112+nmu2 add and remove users and groups
ii initscripts 2.88dsf-13.1 scripts for initializing and shutt
ii libc6 2.11.2-10 Embedded GNU C Library: Shared lib
ii libcap2 1:2.19-3 support for getting/setting POSIX.
ii libcomerr2 1.41.12-2 common error description library
ii libevent-1.4-2 1.4.13-stable-1 An asynchronous event notification
ii libgssapi-krb5-2 1.8.3+dfsg-4 MIT Kerberos runtime libraries - k
ii libgssglue1 0.1-4 mechanism-switch gssapi library
ii libk5crypto3 1.8.3+dfsg-4 MIT Kerberos runtime libraries - C
ii libkrb5-3 1.8.3+dfsg-4 MIT Kerberos runtime libraries
ii libnfsidmap2 0.23-2 An nfs idmapping library
ii librpcsecgss3 0.19-2 allows secure rpc communication us
ii libwrap0 7.6.q-19 Wietse Venema's TCP wrappers libra
ii lsb-base 3.2-23.2squeeze1 Linux Standard Base 3.2 init scrip
ii netbase 4.45 Basic TCP/IP networking system
ii portmap 6.0.0-2 RPC port mapper
ii ucf 3.0025+nmu1 Update Configuration File: preserv
nfs-common recommends no packages.
nfs-common suggests no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 201102041457.p14Evclx016229@helios.selfip.org">htt p://lists.debian.org/201102041457.p14Evclx016229@helios.selfip.org
02-15-2011, 01:57 AM
Ben Hutchings
Bug#612002: Starting NFS common utilities failed
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.
03-11-2011, 10:22 AM
Tom H
Bug#612002: Starting NFS common utilities failed
On Feb 14, 2011, at 9:57 PM, Ben Hutchings wrote:
On Fri, 2011-02-04 at 09:57 -0500, Tong Sun wrote:
>> $ grep portmap /etc/runlevel.conf || echo not found
>> not found
> What is runlevel.conf?
The configuration file (or one of configuration files, I don't use it)
of file-rc (alternative to sysv-rc).
--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: AANLkTikLSYe9Q8ur=7HZf7FObBLsmFXcPKdt3A0bnqBS@mail .gmail.com">http://lists.debian.org/AANLkTikLSYe9Q8ur=7HZf7FObBLsmFXcPKdt3A0bnqBS@mail .gmail.com