mount nfs fails

[ddeblance]

Ignite server is used by network install. From client we initiate boot lan.192.168.x.x install.
From there I can configure the configure the network information, but after that it reads

*NFS mounting clients directory

nfs mount: get_fh: 192.168.x.x:: RPC: Program not registered

nfs mount: retry: retrying(1) for: /var/opt/ignite/clients after 5 seconds

nfs mount: retry: giving up on: /var/opt/ignite/clients

NOTE: Retrying: "/sbin/fs/nfs/mount -oro 192.168.x.x: /var/opt/ignite/clients

Then the itool appears and I can select the image to load. Which in this instance is 11.11

*Downloading_mini-system complete
*Loading Software: Begin
*Installing boot area on disk
*Enabling swap area
*Backing up LVM configuration from vg00
*Processing the archive source (HP-UX Core Operating System Archives)

nfs mount: get_fh: 192.168.x.x:: RPC: Program not registered

nfs mount: get_fh: 192.168.2.2:: RPC: Program not registered

nfs mount: retry: retrying(1) for: /tmp/ign_configure/archive_nfs after 5 seconds

nfs mount: retry: giving up on: /tmp/ign_configure/archive_nfs

NOTE: Retrying: "/sbin/fs/nfs/mount -oro 192.168.x.x::/array/ignite/archives/Rel_B.11.11"

ERROR: Command "sbin/fs/nfs/mount -oro 192.168.x.x::/array/ignite/archives/Rel_B.11.11 /tmp/ign_configure/archive_nfs" failed. Insure that /array/ignite/archives/Rel_B.11.11 is propery exported on 192.168.x.x


This problem just started yesterday and it seems like the problem is with nfs.

[Steven E. Protter]

Shalom,

Yes, its a problem with nfs.

Check the nfs configuration of the ignite server.

/etc/exports
Make sure there are no access limits in this file that would prevent access.

See that the paths are correct and the permissions on said paths are reasonable.


See that nfs.core nfs.server are running on the system.

Also note that to boot off of Ignite you either need to be on the same subnet or have a boot helper server. Seems you have booted though.

SEP

[Prashanth.D.S]

Hi Darren,

Check this error "nfsmount: RPC: Program not registered"

The problem is that rpc.mountd on the HPUX machine is not being started.
This is started from the inetd program. To start this, edit the
file /etc/inetd.conf on the HPUX machine.

The line that follows should be uncommented:

rpc dgram udp wait root /usr/etc/rpc.mountd 100005 1 rpc.mountd

Then, issue the command:

/etc/inetd -c &

This will reread the /etc/inetd.conf file and rpc.mountd will
now start when a mount request comes in from a foreign node.

Best Regards,
Prashanth

[ddeblance]

Steven,

#vi /etc/export
/var/opt/ignite/clients -anon=2
/var/opt/ignite/archives -ro
/var/opt/ignite/scripts -ro
/var/opt/ignite/clients -ro


Not sure how to check the rest of your requests.
This server has been running for, I believe, six years. I has been working flawlessly up until yesterday morning.

Parashanth,
#vi /etc/inetd.conf


##
#
# NCPM programs.
# Do not uncomment these unless you are using NCPM.
#
##

#ncpm-pm dgram udp wait root /opt/ncpm/bin/ncpmd ncpmd
#ncpm-hip dgram udp wait root /opt/ncpm/bin/hipd hipd

dtspc stream tcp nowait root /usr/dt/bin/dtspcd /usr/dt/bin/dtspcd
rpc xti tcp swait root /usr/dt/bin/rpc.ttdbserver 100083 1 /usr/dt/bin/rpc.ttdbs
erver
registrar stream tcp nowait root /etc/opt/resmon/lbin/registrar /etc/opt/resmon/
lbin/registrar
recserv stream tcp nowait root /usr/lbin/recserv recserv -display :0
rpc dgram udp wait root /usr/dt/bin/rpc.cmsd 100068 2-5 rpc.cmsd
swat stream tcp nowait.400 root /opt/samba/bin/swat swat
instl_boots dgram udp wait root /opt/ignite/lbin/instl_bootd instl_bootd

[ddeblance]

My server is back up and running smoothly. I edited /etc/rc.config.d/netconf and changed NFS_SERVER="1". Then I received a new messege when booting client over network that all files and directories need to be owned by "bin". I made the changes, rebooted the server and tried to load a client over network. Load completed with no errors.
Thanks for the help. I'm giving points for stepping up giving advise.