Failed starting rpc.mountd

Rick Stevens rstevens at vitalstream.com
Tue Jul 26 19:27:45 UTC 2005


Anthony J Placilla wrote:
> On Tue, 2005-07-26 at 15:08 -0400, Reuben D. Budiardja wrote:
> 
>>On Tuesday 26 July 2005 14:53, Anthony J Placilla wrote:
>>
>>>On Tue, 2005-07-26 at 14:44 -0400, Reuben D. Budiardja wrote:
>>>
>>>>Hello,
>>>>When I boot my machine, I often get something like the following :
>>>>
>>>>Starting NFS mountd:                                       [  Failed  ]
>>
>><snip>
>>
>>>Is portmapper running?
>>
>>Yes, I think so.
>>
>>
>>>What's the output of
>>>rpcinfo -p
>>
>>It's included below. As I said, it only fail during booting, immediately after 
>>booting I can login as root and restart nfs and it would work fine. Is it 
>>possible that the order when stuff get runs is not right or something ?
>>
>># rpcinfo -p
>>   program vers proto   port
>>    100000    2   tcp    111  portmapper
>>    100000    2   udp    111  portmapper
>>    100024    1   udp  32768  status
>>    100024    1   tcp  32769  status
>>    100021    1   udp  32769  nlockmgr
>>    100021    3   udp  32769  nlockmgr
>>    100021    4   udp  32769  nlockmgr
>>    100021    1   tcp  32774  nlockmgr
>>    100021    3   tcp  32774  nlockmgr
>>    100021    4   tcp  32774  nlockmgr
>>    100007    2   udp    700  ypbind
>>    100007    1   udp    700  ypbind
>>    100007    2   tcp    703  ypbind
>>    100007    1   tcp    703  ypbind
>>    100011    1   udp    850  rquotad
>>    100011    2   udp    850  rquotad
>>    100011    1   tcp    865  rquotad
>>    100011    2   tcp    865  rquotad
>>    100003    2   udp   2049  nfs
>>    100003    3   udp   2049  nfs
>>    100003    4   udp   2049  nfs
>>    100003    2   tcp   2049  nfs
>>    100003    3   tcp   2049  nfs
>>    100003    4   tcp   2049  nfs
>>    100005    1   udp    857  mountd
>>    100005    1   tcp    870  mountd
>>    100005    2   udp    857  mountd
>>    100005    2   tcp    870  mountd
>>    100005    3   udp    857  mountd
>>    100005    3   tcp    870  mountd
>>
>>Thanks.
>>
>>RDB
>>
> 
> 
> Possibly start script order related, yes. 
> 
> My (working) box:
> rpcinfo -p
>    program vers proto   port
>     100000    2   tcp    111  portmapper
>     100000    2   udp    111  portmapper
>     100024    1   udp  32768  status
>     100024    1   tcp  32768  status
>     100003    2   udp   2049  nfs
>     100003    3   udp   2049  nfs
>     100003    4   udp   2049  nfs
>     100003    2   tcp   2049  nfs
>     100003    3   tcp   2049  nfs
>     100003    4   tcp   2049  nfs
>     100021    1   udp  32770  nlockmgr
>     100021    3   udp  32770  nlockmgr
>     100021    4   udp  32770  nlockmgr
>     100021    1   tcp  32769  nlockmgr
>     100021    3   tcp  32769  nlockmgr
>     100021    4   tcp  32769  nlockmgr
>     100005    1   udp    800  mountd
>     100005    1   tcp    803  mountd
>     100005    2   udp    800  mountd
>     100005    2   tcp    803  mountd
>     100005    3   udp    800  mountd
>     100005    3   tcp    803  mountd
> 
> and the start up scripts are
> S13portmap
> S14nfslock 
> S25netfs
> S60nfs 

Note that the "S60nfs" starts the NFS _server_.  The mount is done by
the "S25netfs" script.
----------------------------------------------------------------------
- Rick Stevens, Senior Systems Engineer     rstevens at vitalstream.com -
- VitalStream, Inc.                       http://www.vitalstream.com -
-                                                                    -
-    I don't suffer from insanity...I enjoy every minute of it!      -
----------------------------------------------------------------------




More information about the fedora-list mailing list