NFS server (pid712@/net) not responding still trying

[Prasanth Thomas]

Hi All..

i have a problem with my nis server, it is giving the error,NFS server (pid712@/net) not responding still trying..so i cannot able to update my nis on client because the the home is exported to nis server.please find the below deatails.

while starting the nfs.client it is giving the same error
========

root@uk204:/> /sbin/init.d/nfs.client start
starting NFS CLIENT networking

killing rpc.lockd
killing rpc.statd
killing nfsd
starting up the rpcbind
rpcbind already started, using pid: 4679
starting up the BIO daemons
/usr/sbin/biod 4
Reading in /etc/exports
starting up the Status Monitor daemon
/usr/sbin/rpc.statd
starting up the Lock Manager daemon
/usr/sbin/rpc.lockd
starting up the Automount daemon
/usr/sbin/automount -f /etc/auto_master
NFS server (pid712@/net) not responding still trying
root@uk204:/> /usr/sbin/automount -f /etc/auto_master
NFS server (pid712@/net) not responding still trying
NFS server (pid712@/net) not responding still trying
NFS server (pid712@/net) not responding still trying
NFS server (pid712@/net) not responding still trying
NFS server (pid712@/net) not responding still trying
NFS server (pid712@/net) not responding still trying
root@uk204:/>


Thanks in Advance
Prasant Thomas

[Nido]

Hello Prashant,

>>>>NFS server (pid712@/net) not responding still trying
Check the Network Settings at both the end (NFS Server & Client). Your NFS Client is not able to get the NFS Server over Network or vice-versa.

Fix the Networking on either end and let me know the outcome.

Thanks,

[Dave Olker]

This is the automounter not responding. If you actually need AutoFS you could try troubleshooting it by sending the running daemon a SIGUSR2 signal and looking at the messages logged to /var/adm/automount.log. If you don't need AutoFS then disable it in the /etc/rc.config.d/nfsconf file.

Regards,

Dave

[Prasanth Thomas]

Hi all
Thankd for the reply !!

have checked the coneectivity b/w servers it s ok.

one of my colleague bymistakely killed the pid 712 which is for /net after that it is not coming up. is there is any solution without restart.

thanks
Prasanth Thomas

[Sajjad Sahir]

Dear Prasanth

u have to restart the process.

thanks and regards

Sajjad Sahir

[Dave Olker]

If you're running an OS prior to 11.31 you can try doing an:

/sbin/init.d/nfs.client stop

followed by

/sbin/init.d/nfs.client start

If you're running 11.31 the AutoFS subsystem has its own stop/start script so the commands would be:

/sbin/init.d/autofs stop
/sbin/init.d/autofs start

Hopefully that will gracefully restart the AutoFS processes correctly.

Dave

[Prasanth Thomas]

Hi all

But while starting the nfs.client it is giving the below error...

root@uk204:/> /sbin/init.d/nfs.client start
starting NFS CLIENT networking

killing rpc.lockd
killing rpc.statd
killing nfsd
starting up the rpcbind
rpcbind already started, using pid: 4679
starting up the BIO daemons
/usr/sbin/biod 4
Reading in /etc/exports
starting up the Status Monitor daemon
/usr/sbin/rpc.statd
starting up the Lock Manager daemon
/usr/sbin/rpc.lockd
starting up the Automount daemon
/usr/sbin/automount -f /etc/auto_master
NFS server (pid712@/net) not responding still trying
root@uk204:/> /usr/sbin/automount -f /etc/auto_master
NFS server (pid712@/net) not responding still trying
NFS server (pid712@/net) not responding still trying
NFS server (pid712@/net) not responding still trying
NFS server (pid712@/net) not responding still trying
NFS server (pid712@/net) not responding still trying
NFS server (pid712@/net) not responding still trying
root@uk204:/>

I tried from from both client and server side but no luck...

Thanks
Prasant Thomas.

[Mel Burslan]

if nfs.client stop then start sequence failed, unfortunately, the only thing left to solve your problem is to reboot the machine. Sorry to be the bearer of the bad news.

[Dave Olker]

Mel is correct, but you might be able to forcibly start AutoFS and get rid of these messages without rebooting. It's worth a shot anyway.

What I would do is use "ps -ef" and look for automountd and then terminate it if possible. If it won't die with a regular terminate you shouldn't bother with terminate -9 because that usually leaves the system in a state where AutoFS won't work anyway (I'm starting to wonder if that's what your colleague did to get into this mess).

If you can cleanly terminate automountd then I would try manually starting it (/usr/sbin/automountd) and then issue the /usr/sbin/automount command. If those work then you can try to manually unmount any NFS filesystems managed by AutoFS and then unmount any AutoFS filesystems:

# umountall -F nfs
# umountall -F autofs

If you can get rid of all the NFS and AutoFS filesystems then you might be able to salvage the system without a reboot.

Dave