topic Re: Ignite Client NFS Failure in Operating System - HP-UX

Ignite Client NFS Failure

Dan Matlock_1 — Mon, 11 Jul 2005 12:26:55 GMT

Maybe I have missed something, but after changing a client to another subnet, my ignites fail. Not really a ignite issue as of yet, since command line NFS mount fails as well. Just thought others have seen this.... It use to work, not it doesn't! nslookup resolves name/ip correctly from client/server

Re: Ignite Client NFS Failure

Rick Garland — Mon, 11 Jul 2005 12:28:58 GMT

Did you re-export?

Any changes require re-export.
Also you mention changing to another subnet. Look at the "helper" section of boot a client from an Ignite server. This will be an issue.

Re: Ignite Client NFS Failure

Dan Matlock_1 — Mon, 11 Jul 2005 12:37:23 GMT

yup re-exported, even bounce nfsd on server... It was placed in the same subnet as others that do work w/ignite server.

Re: Ignite Client NFS Failure

Rick Garland — Mon, 11 Jul 2005 12:48:12 GMT

Command line NFS fails as well, there would be some configuration problem.

mount $SYSNAME:dir

What kind of error is reported?

Re: Ignite Client NFS Failure

Dan Matlock_1 — Mon, 11 Jul 2005 13:28:18 GMT

# mount -F nfs eaip2:/var/opt/ignite/recovery/archives/tecdb1 /tmp/dan
Permission denied

Re: Ignite Client NFS Failure

Rick Garland — Mon, 11 Jul 2005 13:53:21 GMT

This could be an export issue.

Check the /etc/xtab file. Is this path listed?

Re: Ignite Client NFS Failure

Dan Matlock_1 — Mon, 11 Jul 2005 14:14:05 GMT

/etc/xtab looks good....

Re: Ignite Client NFS Failure

Rick Garland — Mon, 11 Jul 2005 14:50:10 GMT

The 2 lines in the /etc/exports needed would be;
/var/opt/ignite/clients -anon=2
/var/opt/ignite/recovery/archives/$HOST -anon=2,access=$HOST

I would unexport them and then run through the exportfs command again.

Re: Ignite Client NFS Failure

Dan Matlock_1 — Tue, 19 Jul 2005 11:11:54 GMT

found duplicate system entry in DNS, which caused name resolv. issues that prevented NFS from working.