nfs mount: get_fh

[ddeblance]

Sorry if this has been asked and answered, but I can't find this particual problem. I've had an Ignite server running for years on a small internal network with images we load on daily basis. Tried to load two servers, L2000 and C3600 , both with same problem.

# boot lan.192.168.2.2 install

The system boots from the server and after the configuration screens I get the following (repeated 5 times)

*Reading configuration from server

nfs mount: get_fh: 192.168.2.2:: 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.2.2: /var/opt/ignite/clients

Then the itool appears and I can select the image to load. Note, these images are loaded daily.
Load proceeds as normal. And I get the following.

*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.2.2:: 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.2.2::/array/ignite/archives/Rel_B.11.11"

ERROR: Command "sbin/fs/nfs/mount -oro 192.168.2.2::/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.2.2

[Mustafa Gulercan]

hi;

These messages indicate a problem locating the archive source. Please
validate on the ignite server the nfs_source line in the config files
for this client. The nfs_source line should contain IP address
of source:path to archive. For example:


nfs_source = 192.x.x.x:/var/opt/ignite/archives/Rel_B.11.11


To locate the config file containing this variable search the config files
defined in the stanza for the client in /var/opt/ignite/INDEX.

regards,
mustafa

[ddeblance]

I do not have IP addesses in by config files. I'm not sure why this is happening. No on has been on the Ignite server and it had no problems yesterday.

#vi /var/opt/ignite/INDEX

# /var/opt/ignite/INDEX
# This file is used to define the Ignite-UX configurations
# and to define which config files are associated with each # configuration. Se
e the ignite(5), instl_adm(4), and
# manage_index(1M) man pages for details.
#
# NOTE: The manage_index command is used to maintain this file.
# Comments, logic expressions and formatting changes are not
# preserved by manage_index.
#
# WARNING: User comments (lines beginning with '#' ), and any user
# formatting in the body of this file are _not_ preserved
# when the version of Ignite-UX is updated.
#

cfg "C3700 11i 64 Bit" {
"/opt/ignite/data/Rel_B.11.11/config"
"/var/opt/ignite/data/Rel_B.11.11/C37001111_cfg"
"/var/opt/ignite/data/Rel_B.11.11/apps_custom_cfg"
"/var/opt/ignite/config.local"
}

[Mustafa Gulercan]

try to add the nfs_source line like above example to the config file.

and checked that archives is exported on 192.168.2.2
you can check these files by;
#showmount -e

regards;
mustafa

[ddeblance]

I started ignite software and I received this message:
-----
Failed to update the client's ability to write to the server.
The command "/opt/ignite/lbin/setup_server -n" failed
See "/var/opt/ignitelogs/ignite for details
-----
#vi /var/opt/ignite/log/ignite

ERROR: This machine is not an NFS server (no nfsd running).
The -n option will not be processed.

SUMMARY: There was 1 error detected.

======= 02/06/07 13:52:14 CST End HP-UX Install Server

-----

#showmount -e
showmount: FOX1: RPC: Program not registered

There has never been an ip address in the config files so I'm not conviced that that's the option to take.

[Prashanth.D.S]

Hi Darren,

Reason is the same as your new query..

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