cancel
Showing results for 
Search instead for 
Did you mean: 

NFS client start issue

manoj_pu
Regular Advisor

NFS client start issue


Hello all,

I am trying to setup nfs client on this server.

I am experiencing problem in starting nfs.client on one of hp-ux ll1 server.

Please find below error message when i tried to start the nfs.client.

root@server1:>./nfs.client start
starting NFS CLIENT networking

starting up the rpcbind
rpcbind already started, using pid: 7811
starting up the BIO daemons
/usr/sbin/biod 16
starting up the Status Monitor daemon
/usr/sbin/rpc.statd
starting up the Lock Manager daemon
/usr/sbin/rpc.lockd
mounting remote NFS file systems ...
FAILURE CODE: 126
Mount failed! Possible local filesystem mount.
If local filesystem, then nfs.server will mount it.

mounting CacheFS file systems ...
FAILURE CODE: 126
Mount failed! Possible local filesystem mount.
If local filesystem, then nfs.server will mount it.

Can anybody tell me what is causing this issue?

Thanks & regards
Manoj PU

Leave with out tense and try best you gets result
9 REPLIES
Horia Chirculescu
Honored Contributor

Re: NFS client start issue

>Mount failed! Possible local filesystem mount.
If local filesystem, then nfs.server will mount it.

Maybe your client is trying to mount a local filesystem.

Try to start also the server and then re-start the client.

nfs.client stop
nfs.server start
nfs.client start


Horia.
Best regards from Romania,
Horia.
manoj_pu
Regular Advisor

Re: NFS client start issue


Thanks for your response.

I tried as you suggested but no luck. any other suggestion please.

Thanks & regards
Manoj
Leave with out tense and try best you gets result
Horia Chirculescu
Honored Contributor

Re: NFS client start issue

You get the same error as the first time?

>Mount failed! Possible local filesystem mount.
If local filesystem, then nfs.server will mount it.

Please post the output for

nfs.client stop
nfs.server start
nfs.client start

Horia.
Best regards from Romania,
Horia.
manoj_pu
Regular Advisor

Re: NFS client start issue

root@server1:>./nfs.client stop
killing rpc.lockd
killing rpc.statd
killing biod

root@server1:>./nfs.server start
starting NFS SERVER networking

starting up the rpcbind daemon
rpcbind already started, using pid: 19091
starting up the Status Monitor daemon
/usr/sbin/rpc.statd
starting up the Lock Manager daemon
/usr/sbin/rpc.lockd

root@server1:>./nfs.client start
starting NFS CLIENT networking

starting up the rpcbind
rpcbind already started, using pid: 19091
starting up the BIO daemons
/usr/sbin/biod 16
starting up the Status Monitor daemon
rpc.statd already started, using pid: 23747
starting up the Lock Manager daemon
rpc.lockd already started, using pid: 23753
mounting remote NFS file systems ...
FAILURE CODE: 126
Mount failed! Possible local filesystem mount.
If local filesystem, then nfs.server will mount it.

mounting CacheFS file systems ...
FAILURE CODE: 126
Mount failed! Possible local filesystem mount.
If local filesystem, then nfs.server will mount it.
Leave with out tense and try best you gets result
Horia Chirculescu
Honored Contributor

Re: NFS client start issue

From /sbin/init.d/nfs.client:

--------------------------------
echo " mounting remote NFS file systems ..."
x=0
/sbin/mount -aQF nfs
set_return
if [ $x -ne 0 ];then
echo " Mount failed! Possible local filesystem mount."
echo " If local filesystem, then nfs.server will mount it."
echo ""
rval=0
fi

##
# mount the CacheFS file systems specified in /etc/fstab.
##

echo " mounting CacheFS file systems ..."
x=0
/sbin/mount -aQF cachefs
set_return
if [ $x -ne 0 ];then
echo " Mount failed! Possible local filesystem mount."
echo " If local filesystem, then nfs.server will mount it."
echo ""
rval=0
fi

--------------------------

mount -a ... How does it look like

/etc/fstab

cat /etc/fstab

Horia.
Best regards from Romania,
Horia.
manoj_pu
Regular Advisor

Re: NFS client start issue

Hi Horia,
Thanks for the feedback.

Problem has been resolved.

/sbin/mount file was empty.

FAILURE CODE: 126 was coming from the mount command exit code when nfs.client start command was issued.

exit code 126 represents permission denied.

Thanks again for the response.

Regards
Manoj
Leave with out tense and try best you gets result
Horia Chirculescu
Honored Contributor

Re: NFS client start issue

>/sbin/mount file was empty.

empty ?! And you had a running system? How does your filesystems were able to be mounted if the mount command was missing?

Horia.


Best regards from Romania,
Horia.
manoj_pu
Regular Advisor

Re: NFS client start issue


Hi Horia,

From the time stamp of the file,it seems like unkowingly /sbin/mount was nollified yesterday.

We would experienced problem with mounting filesystems if we restart the server.

Thanks & regards
Manoj
Leave with out tense and try best you gets result
manoj_pu
Regular Advisor

Re: NFS client start issue



Thanks & Regards
Manoj
Leave with out tense and try best you gets result