Ignite-UX (IUX) Frequently Asked Questions (July 2013)

Most users have found that installing about twenty (20) clients at a
time, from a single server, is the limit while maintaining reasonable
performance and avoiding network errors. This seems to be a
reasonable number for you to keep track of and test when the
installations complete. Also, you may find it useful to stagger the
installations so that they are not all doing the same operation at
the same time, thus do not all complete at the same time.
Using the NFS access method to access archives is suggested in order
to avoid a problem that occurs when installing many clients using the
ftp access method. When many ftp and tftp processes are running to a
server at once, the tftp commands start generating the following
error:
tftp: recvfile: recvfrom: Can't assign requested address
Note: You may need to make SD configuration changes to cope with
a large number of concurrently installing clients, please read the
section "Performance considerations for SD-UX based installs" in the
manual "Ignite-UX Custom Configuration Files" available at:
http://www.docs.hp.com/en/IUX/infolib.html
=============================================================================
==
5.8
Q: My installations are hanging; what is going on?
A: In certain circumstances installations may hang and could be due to a
problem with swagentd. If you are using an operating system archive,
the hang occurs after the following message appears in:
* 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 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.