Ignite-UX (IUX) Frequently Asked Questions (July 2013)
# SAMTERM=dtterm ignite
or
# SAMTERM=xterm ignite
This variable is only supported on 11.23 with PHSS_31817 installed. 11.31
will use xterm, which does not have the hostname resolution problem. On
11.11 or 11.23 systems without the patch, you should specify an IP address
in the DISPLAY variable.
=============================================================================
==
1.21
Q: Why am I getting the following message?
pax: Cannot access /sbin/pax_enh : No such file or directory.
A: If you try archiving using pax format, you see the following message:
pax: Cannot access /sbin/pax_enh: No such file or directory
pax: PAX-ENH product needs to be installed to enable the options -A, -o
exclude and -o graph.
WARNING: The pax command returned a non-zero exit status (exit status 1).
You need to install PAX-ENH product to create pax format tape archives
using make_tape_recovery, even on 11.31.
=============================================================================
==
1.22
Q: Why do I see a problem while using March 2013 HP-UX OE media as install
media?
A: 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
Some standalone systems, such as rx5670
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).
ERROR: Could not execute net_cfg_prep
NOTE: System rebooting...
Shutdown at 10:36 (in 0 minutes)
System shutdown time has arrived
This is caused by an Ignite-UX issue and is tracked in QXCR1001268768.
While installing an rx5670 via the network, when the installation
settings are finalized and installation started, the following
error message is displayed on the client console:
* Loading configuration utility...
* Beginning installation from source: 16.113.12.86