Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Starting NFS common utilities failed!

296 views
Skip to first unread message

T o n g

unread,
Feb 3, 2011, 4:00:01 PM2/3/11
to

Hi,

How do I fix this problem?

% invoke-rc.d nfs-common start
Starting NFS common utilities: statd failed!
invoke-rc.d: initscript nfs-common, action "start" failed.

Apparently, it's a common error but nobody knows the answer:

http://help.lockergnome.com/linux/Bug-562737-installation-failed-Starting-
NFS-common-utilities--ftopict512091.html
http://www.linux4one.com/forum/index.php?topic=1888.0
http://man-linux.comli.com/?p=154

All are just symptom report with no solution.

debian testing,

$ apt-cache policy nfs-common
nfs-common:
Installed: 1:1.2.2-4
Candidate: 1:1.2.2-4
Version table:
*** 1:1.2.2-4 0
360 http://cdn.debian.net/debian/ testing/main amd64 Packages
50 http://cdn.debian.net/debian/ unstable/main amd64 Packages
100 /var/lib/dpkg/status

Please help. thx.

--
Tong (remove underscore(s) to reply)
http://xpt.sourceforge.net/techdocs/
http://xpt.sourceforge.net/tools/


--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: http://lists.debian.org/iif4fa$c87$1...@dough.gmane.org

Dr. Ed Morbius

unread,
Feb 3, 2011, 5:10:02 PM2/3/11
to
on 20:50 Thu 03 Feb, T o n g (mlist4...@yahoo.com) wrote:
>
> Hi,
>
> How do I fix this problem?
>
> % invoke-rc.d nfs-common start
> Starting NFS common utilities: statd failed!
> invoke-rc.d: initscript nfs-common, action "start" failed.
>
> Apparently, it's a common error but nobody knows the answer:
>
> http://help.lockergnome.com/linux/Bug-562737-installation-failed-Starting-
> NFS-common-utilities--ftopict512091.html
> http://www.linux4one.com/forum/index.php?topic=1888.0
> http://man-linux.comli.com/?p=154
>
> All are just symptom report with no solution.
>
> debian testing,
>
> $ apt-cache policy nfs-common
> nfs-common:
> Installed: 1:1.2.2-4
> Candidate: 1:1.2.2-4
> Version table:
> *** 1:1.2.2-4 0
> 360 http://cdn.debian.net/debian/ testing/main amd64 Packages
> 50 http://cdn.debian.net/debian/ unstable/main amd64 Packages
> 100 /var/lib/dpkg/status

A good first debugging step is to run the script via 'bash -x':

sudo bash -x /etc/init.d/nfs-common start

... which will show steps being executed, as well as the error(s).

You might also try 'bash -ex <script>' to force an exit on the first
error (though the init script may override this).

--
Dr. Ed Morbius
Chief Scientist
Krell Power Systems Unlimited


--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org

Archive: http://lists.debian.org/2011020322...@altaira.krellpowersys.exo

T o n g

unread,
Feb 3, 2011, 10:40:01 PM2/3/11
to
On Thu, 03 Feb 2011 14:04:52 -0800, Dr. Ed Morbius wrote:

>> How do I fix this problem?
>>
>> % invoke-rc.d nfs-common start
>> Starting NFS common utilities: statd failed! invoke-rc.d: initscript
>> nfs-common, action "start" failed.
>>
>> Apparently, it's a common error but nobody knows the answer:
>>

>> http://. . .

>>
>> All are just symptom report with no solution.
>>
>> debian testing,
>>
>> $ apt-cache policy nfs-common
>> nfs-common:
>> Installed: 1:1.2.2-4
>> Candidate: 1:1.2.2-4
>> Version table:
>> *** 1:1.2.2-4 0
>> 360 http://cdn.debian.net/debian/ testing/main amd64 Packages
>> 50 http://cdn.debian.net/debian/ unstable/main amd64 Packages
>> 100 /var/lib/dpkg/status
>
> A good first debugging step is to run the script via 'bash -x':
>
> sudo bash -x /etc/init.d/nfs-common start

Thanks for the reply. The whole execution log is posted at
http://pastebin.com/SQefWNQs

Seems to me that the reason of failure is the failure of

statd+ start-stop-daemon --start --oknodo --quiet --exec /sbin/rpc.statd
--
+ RET=1

$ file /sbin/start-stop-daemon
/sbin/start-stop-daemon: ELF 64-bit LSB executable

$ ls -l /sbin/rpc.statd
-rwxr-xr-x 1 root root 65776 2010-08-26 23:25 /sbin/rpc.statd*

Rings any bell?

Thx

--
Tong (remove underscore(s) to reply)
http://xpt.sourceforge.net/techdocs/
http://xpt.sourceforge.net/tools/

--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org

Archive: http://lists.debian.org/iifs23$rju$1...@dough.gmane.org

Dr. Ed Morbius

unread,
Feb 4, 2011, 2:50:01 AM2/4/11
to

Yep, same here.



> $ file /sbin/start-stop-daemon
> /sbin/start-stop-daemon: ELF 64-bit LSB executable
>
> $ ls -l /sbin/rpc.statd
> -rwxr-xr-x 1 root root 65776 2010-08-26 23:25 /sbin/rpc.statd*
>
> Rings any bell?

Not off the top of my head. Or the bottom.

Try launching the daemon manually, with the '-d' (debug) option. See
if that gives you anything more.

strace would be my next try. Googling suggests a missing config file or
state file -- does /var/lib/nfs/ exist, and is it populated?

/var/lib/nfs/statd/sm/state
/var/lib/nfs/statd/sm/*
/var/lib/nfs/statd/sm.bak/*


--
Dr. Ed Morbius
Chief Scientist
Krell Power Systems Unlimited

--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org

Archive: http://lists.debian.org/2011020407...@altaira.krellpowersys.exo

T o n g

unread,
Feb 4, 2011, 10:40:02 AM2/4/11
to
On Thu, 03 Feb 2011 23:40:57 -0800, Dr. Ed Morbius wrote:

>> statd+ start-stop-daemon --start --oknodo --quiet --exec
>> /sbin/rpc.statd
>> --
>> + RET=1
>
> Yep, same here.

Thanks for your helps, Dr. Morbius. I found the real reason, and file a
bug report:

Starting NFS common utilities failed
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=612002

"
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.

Starting it manually solve the problem: . . .
"

check http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=612002
for details.

> . . . Googling suggests a missing config file or


> state file -- does /var/lib/nfs/ exist, and is it populated?
>
> /var/lib/nfs/statd/sm/state
> /var/lib/nfs/statd/sm/*
> /var/lib/nfs/statd/sm.bak/*

Just for the archive, in Debian the files are:

$ find /var/lib/nfs/
/var/lib/nfs/
/var/lib/nfs/sm.bak
/var/lib/nfs/state
/var/lib/nfs/sm
/var/lib/nfs/rpc_pipefs

Thanks again.

--
Tong (remove underscore(s) to reply)
http://xpt.sourceforge.net/techdocs/
http://xpt.sourceforge.net/tools/

--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org

Archive: http://lists.debian.org/iih64d$i91$1...@dough.gmane.org

0 new messages