Ignite-UX Release Notes (769572-001, March 2014)

6 Known problems and workarounds
This section describes known problems with the Ignite-UX product as well as workarounds to these
problems. More detail is often available in the FAQ available from: http://www.hp.com/go/
ignite-ux.
Required patches
Patch PHCO_31903, s700_800 B.11.11 libc cumulative patch, is required for the correct execution
of list_expander on B.11.11 systems, and patch PHKL_31500 is required on B.11.23 systems
that are running B.11.23 September 2004 or later.
These patches supply a fix for nftw that stops it from running stat on symlinks. In an automounter
situation if there is a nonresponding NFS file system, it causes list_expander to hang on any symlink
pointing into it. The defect was not in libc.1, only in libc.2 from B.11.11 onwards.
When creating a system archive via make_sys_image or make_net_recovery, the pax utility
is used. You must install the latest patch for pax on the machine(s) on which you will be creating
your archive and generating disk space impacts.
The patch numbers are:
B.11.11: PHCO_35998 s700_800 11.11 pax(1) cumulative patch
B.11.23: PHCO_39677 s700_800 11.23 Cumulative changes to pax(1)
B.11.31: PHCO_38835 11.31 pax(1) cumulative patch
If you wish to use the pax format of the pax command with make_sys_image,
make_net_recovery or make_net_recovery on B.11.23, then you will also need the PAX-Enh
product installed on the client system you intend to create the archive for.
• When creating large system archives (greater than 2 GB) over an NFS mount (which is the
case when using make_net_recovery), both the client and server must be capable of NFS
PV3. All currently supported HP-UX releases support NFS PV3.
• When an Ignite-UX server's IP address is changed via set_parms, it is desirable for the
default install server information set by instl_adm (in the install kernels) to be changed to
reflect the server's new IP address. This functionality is enabled by patches PHCO_34837
(B.11.11) and PHCO_34838 (B.11.23).
General issues
This section describes some general problems with the Ignite-UX product as well as workarounds
to these problems.
• A problem occurred while using the March 2013 HP-UX OE media as install media. This issue
is common with the following configurations, but there can be other instances too:
◦ HPVM Guest or vPar using virtual or physical DVD
◦ Ignite-UX Server based cold installation is initiated on HP Integrity rx5670 systems
The following are the symptoms associated with the issue:
◦ During installation of HP-UX 11i v3 March 2013 from physical or virtual media, the
installation aborts unexpectedly and displays the following error:
Checking configuration for consistency...
NOTE: run_cmd: Process: 113 (net_cfg_prep): killed by signal:
11.
ERROR: Could not open /tmp/env.vars: No such file or directory
(errno = 2).
22 Known problems and workarounds