HP Ignite-UX Applications Hang After Igniting, Problems Pointing to Client Over Network

—Check to see if there are other systems on the network that may also be replying to the booting client system.

—Check to see if the system booting is on a different subnet to the bootp server to ensure that any router between the two allows the forwarding of bootp requests. The configuration is router specific.

3.Check tftpd:

—Check the tftp line in /etc/inetd.conf to make certain that the /opt/ignite and /var/opt/ignite directories are listed.

—Check the tftpd connection manually by using the tftp command, for example:

a.$ tftp [server-name]

b.tftp> get /opt/ignite/boot/nbp.efi /tmp/nbp.efi

Received [n] bytes in [s] seconds

c.tftp> quit

Problems Pointing to Client Over Network

The control_from_server=true and run_ui=false variables are in [WVI]INSTALLFS, but I still get prompted for information on the client.

Possible problems are:

•If the dialog box is showing the client name in an editable field and a Cancel button at the bottom of the dialog box, then all is well and there should be an icon waiting for you on the Ignite-UX GUI. The text box enables you to change the icon name or switch to a client side install.

•If the dialog box is showing two or more LAN interfaces to choose from, then there was not enough information in the configuration files to tell it which LAN to use. Once you select a LAN and select Install HP-UX, you should be set.

•If the dialog box is prompting you for networking information, then either DHCP did not respond or there is no entry in /etc/bootptab for the client. Enter the network information, select Install HP-UX and continue the install.

Applications Hang After Igniting

Some applications and shells hang over NFS after igniting.

The reason for the hang is most likely due to a problem with the NFS file locking daemons, rpc.statd and rpc.lockd, caused by the action of reinstalling the system. Many applications use file locking and can hang in this situation. Most common are user home directories that are NFS mounted, in which case sh and ksh will attempt to lock the .sh_history file and hang before giving you a prompt.

When a system is running and has an active NFS mount with a server in which files have been previously locked, both the client and server cache information about each other. Part of the information that is cached is what RPC port number to use to contact the rpc.lockd daemon on the server and client.

This RPC port information is cached in memory of the running rpc.statd/rpc.lockd process on both the server and client sides. The rpc.statd process keeps a file in the directory /var/ statmon/sm for each system that it knows it should contact in the event that the system reboots (or rpc.statd/rpc.lockd restarts). During a normal reboot or crash, rpc.statd will contact all systems in /var/statmon/sm and inform them to flush their cache regarding this client.

Installing Systems with Ignite-UX 227