Ignite-UX Administration Guide for HP-UX 11i (B3921-90080, November 2013)

rbootd daemon is running. The rbootd daemon always runs, whereas instl_bootd is
started using inetd and only runs when needed.
Also, for these older clients, there is an intentional delay built into the rbootd process when
a client wants to do an installation boot (as opposed to a diskless boot). This prevents the
server from showing up during the first search. Retrying the search two or three times may be
necessary.
The bootsys Command Fails with Insufficient Space
The bootsys command fails due to insufficient space in the /stand volume.
The bootsys command must copy the two files,
/opt/ignite/boot/Rel_release/[W|V|I]INSTALL and
/opt/ignite/boot/Rel_release/[W|V|I]INSTALLFS
from the server into the client’s /stand directory. This error indicates that there is not enough
space in /stand. To correct this situation, you may need to remove any backup kernels. Also,
check for kernels in the /stand/build/ directory (like vmunix_test).
TUI Does Not Accept User Input
The text fields in the TUI do not accept keyboard input during client installations.
The text fields within the TUI do not recognize keyboard input, causing dialogs to reopen or loop.
This occurs when the Insert key is active so you must ensure that the Insert key is deactivated by
pressing it to enter data in the TUI.
Installing from Media
DCE/RPC Errors
DCE / RPC errors (RPC exceptions) occur during the configuration stage, and a failure message is
printed at the end of the installation.
There is an apparent problem with certain SD operations (for example, swacl) when only loopback
networking is enabled. This would occur if the "media only" installation option is selected. The
work-around is to install using the "media with networking enabled" option and set up (perhaps
temporary) networking parameters: hostname, IP address, netmask, routing, etc. SD operations
will complete normally.
Installing from Golden Images
Cannot Find Specified Archive
Errors: gunzip: stdin: unexpected end of file
pax_iux: The archive is empty.
ERROR: Cannot load OS archive (HP-UX Core Operating System
Archives)
The NFS mount probably succeeded, but the file was not accessible from the client. Check these
possibilities:
• File has a different name (check your configuration files).
• File has the wrong permissions such that it is not readable. Check /etc/exports for HP-UX
11i v1 and 11i v2 systems, and /etc/dfs/dfstab for HP-UX 11i v3 systems.
Missing .conf Files
The /etc/nsswitch.conf and /etc/resolv.conf files from the archive do not end up on
the installation client.
230 Troubleshooting