NFS mounting issue

[Neil Herring_1]

When starting up the nfs.client service I receive the following output:
starting NFS CLIENT networking

starting up the rpcbind
rpcbind already started, using pid: 22935
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
starting up the Automount daemon
/usr/sbin/automount -f /etc/auto_master
mounting remote NFS file systems ...
nfs mount: get_fh: meskpdb:: RPC: Rpcbind failure - RPC: Timed out
nfs mount: get_fh: meskpdb:: RPC: Rpcbind failure - RPC: Timed out
nfs mount: retry: retrying(1) for: /acube/measkp/km/km_web/km/images/marketing after 5 seconds
nfs mount: retry: giving up on: /acube/measkp/km/km_web/km/images/marketing
FAILURE CODE: 1
Mount failed! Possible local filesystem mount.
If local filesystem, then nfs.server will mount it.

mounting CacheFS file systems ..

I have set up the /etc/exports file correctly and tested the mount point by mounting on another server altogether. Also checked firewall restrictions and obviously the forums site too.

Any ideas would be gratefully received.

[Arunvijai_4]

Hi Neil,

Are you able to ping or telnet to the NFS server? Whether your NFS server is using /var/adm/inet.sec ? Check those.

-஠ர௠னà¯

[spex]

Neil,

What does the relevant stanza from /etc/exports look like?

PCS

[Neil Herring_1]

The /etc/exports file looks like this:
/acube/measkp/webcms/interface -root=meskpweb:eurodev

I can confirm that this NFS mount works on eurodev but not meskpweb so the syntax must be correct.

There is no inetd.sec file in place.

[spex]

Check that /etc/xtab matches /etc/exports ('exportfs'). Can the nfs server find the client by hostname (e.g. 'traceroute meskpweb')?

PCS

[Timothy P. Jackson]

Hi Neil,

Try doing a exportfs -au this clear the xtab and then do a exportfs -a to rebuild it. I have seen nfs mounts not work because this file is not correct.

Good luck,


Tim