Filter
Top Products
Chapter 4 51
Support Tools Manager (STM)
Common Problems
Common Problems
Exercisers sometimes enter a "Hung" state.
STM monitors the progress of all running tools and expects each tool to send a "heartbeat"
every minute or so. If these heartbeat indications are not received within a two-minute
window, the tool state is changed to "Hung". Two possible causes:
• Cause 1: Not enough CPU time The most probable cause is that the tool is not getting
enough CPU time. This situation may occur if the computer is extremely busy or if
several exercisers are executing simultaneously, especially with the "Maximum Stress"
option.
If the cause of the problem is not enough CPU time, the tool will eventually make
enough progress to send another heartbeat at which time its state will be changed back
to "Running". You may choose to suspend or abort the tool and wait for the system to
become less busy. If you want to run several exercisers simultaneously, use the
"Medium Stress" option.
• Cause 2: Tool has stopped executing Only rarely would the tool stop executing. Typically,
this behavior would be caused by a kernel driver that has stopped responding or
something of that nature.
The tool may eventually start executing again if it becomes unblocked, at which time its
state will be changed back to "Running". You may choose to abort the tool at this point.
If the tool is blocked due to a kernel resource such as in a driver, you not be able to abort
the tool. In this case, the tool will stay in an "abort pending" state indefinitely.
The user interface will not connect to a machine.
This problem usually occurs when the machine address cannot be resolved or because the
diagmond daemon is not running on the machine that is being connected to. Use
/etc/ping to verify that the host address can be resolved.
If ping works, check to see if diagmond is running on the host machine. If it is not, log
into the host machine, run STM on it, and use the "File — >Administration — >Local UUT
Logs" command to view the log files on the host machine and determine what the problem
is.
The remote machine must have:
• HP-UX 10.01 or higher.
• The bundle containing STM (OnlineDiag) loaded.
• The diagmond demon running.