Ignite-UX Frequently Asked Questions

At this point in the process, Ignite-UX attempts to start swagentd.
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 appears:
NOTE: run_cmd: Process: 223 (/usr/sbin/swagentd): killed by signal: 2.
ERROR: swagentd returned an error.
You are asked if you want to push a shell, and you should answer yes.
You can exit, and then ask 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 in fact running. Assuming no other problems occur, the
installation should complete successfully.
Ignite-UX has incorporated patched versions of swagentd into its
SYSCMDS archives. However, if you are using an operating system
archive the archive may contain an older unpatched swagentd that gets
deposited on top of the SYSCMDS version. This older, unpatched
version then gets used and the hang may 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 that changing seemingly unrelated things like disk drives, file
system layout, language choice, and so forth, may eliminate the hang
though this is not guaranteed.
===============================================================================
5.9
Q: How large can I create a single swap space using Ignite-UX?
A: On HP-UX 11.23 and above the restriction on swap spaces being less
than or equal to 32GB has been removed. The same is not true of
HP-UX 11.11, Ignite-UX will limit the size of a swap space to be 32GB
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.
If the amount of swap created is more than 32 GB, you must increase
the kernel tunable swchunk from its default of 2048. Ignite-UX will
not do this automatically. If there is insufficient kernel resources
configured to allow you to use the swap being created, you a message
appears indicating this during the installation process. This
message may not be accurate if you change swchunk using a
configuration file as Ignite-UX assumes that swchunk is 2048 and does
not take into account any changes to its value.
You can manually increase swchunk once the installation process is
complete using SAM. To increase swchunk during an Ignite-UX
installation you can place a line like the following in the Ignite-UX
configuration:
mod_kernel += "swchunk 4096"
With swchunk set to 4096, you are able to utilize up to 64 GB of
swap, assuming that Ignite-UX had to set maxswapchunks to its maximum
value of 16384.