vmunix: NFS server not responding

[lastgreatone]

We had to shutdown the primary DNS for troubleshooting, so we had to modify the resolver on the production and development servers to point to the secondary DNS. On the production server there was an NFS mount prior to changing the resolve. Why wouldn't the secondary DNS resolve the nfs mount request? This resulted in a serious backlog of oracle requests on the production server. The exact msg: vmunix: NFS server (pid634@/hp260/nsdb) not responding, still trying. Any clues?

[Sanjay_6 · Accepted solution]

Hi Frankie,

After modifying your /etc/resolv.conf, is your system able to resolve the name and ip of your NFS server. Looks like name and ip resolution problem to me.

Hope this helps.

regds

[Sanjay_6]

Hi Frankie,

If The NFS is still giving problem, you can try and restart the NFS client subsystem.

Hope this helps.

Regds

[Sanjay_6]

Hi Frankie,

Here is a thread from ITRC to help you out,

http://us-support.external.hp.com/cki/bin/doc.pl/sid=c99b04ba00e7017303/screen=ckiDisplayDocument?docId=200000054626548

Hope this helps.

Regds

[Roger Baptiste]

<>

It''s alway good to have the primary and secondary on the resolv.conf file to avoid last minute hassles.
Does the modified resolver work? to confirm it do:
nslookup
It should show the default name server as the secondary.
in the nslookup prompt give
the NFS server name and see whether it gets resolved correctly. Also do a reverse lookup on the IP address.

<>

that's because NFS has a mind of it''s own ;-)
If you are sure the resolver is working fine both at the secondary dns and the client systems, then look at it as NFS issue.

At the NFS server end ,do
showmount -a
to see whether all the clients are connected.

As a last resort restart the
nfs.client daemons.
/sbin/init.d/nfs.client stop
/sbin/init.d/nfs.client start.

HTH
raj

[lastgreatone]

Thanks for your assistance. I believe it was an NFS issue, as I was not the adm who set it up originally, but plan on getting on top of it.