Ignite-UX (IUX) Document for Frequently Asked Questions (FAQ) (762793-001, March 2014) (Edition: 3)

My installations are hanging; what is going on?
In certain circumstances installations might hang and this can be due to a problem with swagentd.
If you are using an operating system archive, the hang occurs after the following message appears:
* Running /opt/upgrade/bin/tlinstall -v and correcting transition link
permissions.
If you are using swinstall only, the hang occurs after the following message appears in
install.log:
* Setting primary boot path to <some hardware path>
At this point in the process, Ignite-UX starts swagentd daemon. Because of a signal problem with
swagentd, the parent process waits infinitely for a signal from the child process, which cannot
occur. If you press Ctrl+C on the client console, you see a message similar to the following:
NOTE: run_cmd: Process: 223 (/usr/sbin/swagentd): killed by signal: 2.
ERROR: swagentd returned an error.
Select the option, Push a shell. After the execution of command, enter exit2. Select the option
Ignore to continue installation. This results in an error because the child process is
running. Installation must be completed successfully.
When you are asked if you want to push a shell, enter yes. Enter Exit2, to exit the process and
click Ignore Ignite-UX to ignore the problem to continue the installation. Ignite-UX falsely believes
that swagentd has not started and attempts to start it whenever it does a subsequent swinstall.
This results in an error because the child process is running. Assuming no other problems occur,
the installation must complete successfully.
Patch versions of swagentd is incorporated into SYSCMDS archives of Ignite-UX. However, if you
are using an operating system archive, the archive might contain an older unpatched swagentd
that gets deposited on top of the SYSCMDS version. This older, unpatched version then gets used
and the hang might occur. In this case, the operating system archive requires a patched swagentd
to fix the problem, and then it must be rebuilt. If this is not possible, you can instead use a
post_load_cmd script to copy a fixed swagentd from the Ignite-UX server onto the client after
the archive is unpacked.
NOTE: Changing seemingly unrelated things like disk drives, file system layout, language choice,
and so forth, might eliminate the hang though this is not guaranteed.
How large can I create a single swap space using Ignite-UX?
On HP-UX 11.23 and above the restriction on swap spaces being less than or equal to 32 GB
has been removed. The same is not true for HP-UX 11.11, Ignite-UX will limit the size of a swap
space to be 32 GB or less.
To fully enable any amount exceeding 32 GB on HP-UX 11.11, it requires adjustment of the kernel
parameters swchunk and maxswapchunks post installation.
There are individual size restrictions on the primary swap and all dump logical volumes that depend
on operating system revision and firmware limitations in disk controllers. These volumes are limited
in how far they can span from the beginning of the physical disk. The limits for HP-UX 11.11 and
later are 4 GB or limited only by size of disk, depending on firmware. (Most PCI controllers and
more modern systems do not impose specific limits. Older systems, like K and D series, do have
restrictions on dump.)
If these limits are exceeded, Ignite-UX produces an error message and the installation is not allowed
to proceed.
To use a large amount of swap, you must ensure that you have sized the swap related kernel
parameters to allow for the total swap space configured. Ignite-UX automatically increases the
kernel tunable maxswapchunks up to its maximum of 16384 to allow for more swap.
28 General installation