STM Online Help: cstm Online Help (command-line interface)

UI cannot connect to a system
One indication that you have encountered this situation is that an invalid user name or password error will be displayed
to you.
If "ping" works for the IP address, but not for the hostname, use the IP address.
When checking "uname -s" and "nslookup", ensure that the hostname portions match; for example,
"uname -s" returns "hprdstl6"
"nslookup" returns "hprdstl6.rose.hp.com"
In the following instances, you must make the system independent of the network and the nameserver:
When the nameserver is down
When there are hostname or IP address conflicts
When the system is not connected to the network
To do this, move the "/etc/resolv.conf" nameserver file, and create a local "/etc/hosts" file, which contains the local
hostname and IP address. This will allow you to override the nameserver, permitting the system to run locally.
Consult the following (on the UUT) for the information needed to determine the cause of a failure to connect to the
UUT:
Syslog
LocalSysActLog
LocalMapLog
When running STM locally on a system which had a problem performing a remote connect, errors may be displayed
when STM attempts to perform a local connect: you may safely ignore these error messages.
You may have to restart "diagmond": you must be root in order to do so (STMStartup).
Top
Tool goes into HUNG state
This is one of the more common problems you may encounter with the operation of the STM. Tools may move into
and out of the "HUNG" state in the following instances:
When the system is very busy
When you attempt to start many tools simultaneously
When you already have multiple tools running (especially true if any of the tools is set to Maximum stress or
Coverage level)
When the system has limited resources
If any of the above conditions is true, update the "diagmond" configuration so that it waits longer before marking a
tool as "HUNG" (the default wait time is 4 minutes).
If a tool stays in the "HUNG" state, determine if there is an error by examining the activity log for the tool you are
running (e.g., Verify Tool Activity Log) for errors, and/or to determine the last time the tool logged, compared to the
current time. You may also want to examine the process, using the "ps -ef" command.
If the activity log for the tool you are running is actually hung, attempt to abort the tool. If the tool remains in the