topic Re: NFS issues in Operating System - HP-UX

NFS issues

dictum9 — Mon, 09 Oct 2006 17:12:22 GMT

I am using Ignite-UX and am having issues with NFS. On the client, I cannot mount the directory from the server. The directory is correctly exported.

ignclnt:/#:mount ignsvr:/var/opt/ignite/recovery/archives/ignclnt /tmp/test
Permission denied

Re: NFS issues

Steven E. Protter — Mon, 09 Oct 2006 17:38:14 GMT

Shalom,

there is a message in /var/adm/syslog/syslog.log that may explain further.

Either ownership permissions does not permit it or the limits in /etc/exports on the server is blocking it.

Also TCP wrappers, which I recently learned how to properly use on the RHCE can block access by network/hostnamme etc.

SEP

Re: NFS issues

Sandman! — Mon, 09 Oct 2006 18:22:25 GMT

Could you elaborate on what you are trying to do? Additionally look into the syslog for relevant error messages and post them here.

thanks!

Re: NFS issues

dictum9 — Tue, 10 Oct 2006 10:02:37 GMT

Nothing in syslog

I am trying to add a system for recovery (make_net_recovery) in Ignite-UX, and it's having problems mounting its filesystems.

Re: NFS issues

IT_2007 — Tue, 10 Oct 2006 10:08:40 GMT

you have export the following from Ignite server.

/etc/exports file:

/var/opt/ignite/clients -anon=2
/depot/ignite/archive/Rel_B.11.11 -ro,anon=2

exportfs -av

Re: NFS issues

Doug O'Leary — Tue, 10 Oct 2006 10:15:21 GMT

Hey;

On the client, verify the exported filesystems from the server:

showmount -e ignsvr

Assuming that shows what you're expecting,

ssh ignsvr # Login
tty # Note the tty number
who -R | grep ${tty} # Note the hostname.

Verify the hostname matches what you're using in the exports if you're using host based access lists on the exports.

HTH;

Doug

Re: NFS issues

Jon Ward_3 — Wed, 11 Oct 2006 07:39:57 GMT

Also check the time/date on the systems. If they are to far out of sync NFS will reject you for security reasons.

Re: NFS issues

Dave Olker — Wed, 11 Oct 2006 14:07:05 GMT

Hi,

If you've exhausted all of the normal troubleshooting options (i.e. make sure all the daemons are running, make sure the filesystem is exported properly, make sure the client is in any access lists for the filesystem, etc.) and you're still not able to get the filesystem to mount then you should try enabling debug logging for the rpc.mountd daemon on the server and repeat the failed operation. The resulting log file will give us a lot more information about why the server is rejecting the mount request.

To enable debug rpc.mountd logging, use ps to find the running rpc.mountd daemon and send that daemon a SIGUSR2 (i.e. kill -17 ). The daemon will begin logging to the /var/adm/mountd.log file. Once logging is started issue the failing mount request from the client and then send another SIGUSR2 to the rpc.mountd on the server to turn debug logging off.

Please post the debug rpc.mountd logfile here so that I can examine the contents and hopefully determine why the server is rejecting the mount request.

Regards,

Dave