416 Chapter 10
Tuning, Troubleshooting, Security, and Maintenance
Troubleshooting: Specific Problems
Problem Automatic or operator-initiated action, scheduled action, command
broadcast, or application hangs and does not terminate.
Description Due to programming errors or requests for user input, automatic and/or
operator-initiated actions, or scheduled actions can hang and not finish.
Solution Determine the process ID of the endlessly running action using the ps
command. Issue a kill command for the specific process ID.
Problem Distribution of scripts or programs belonging to actions, monitor, or
commands components fails.
Description A No disk space is available to store scripts/programs in a temporary or
target directory. See Table 6-2 on page 308 and Table 6-3 on page 310.
Solution A Provide enough disk space and redistribute the appropriate components.
Description B An instance of the program is running and cannot be overridden on UNIX
platforms. ITO moves the actions|cmds|monitor directory to a
directory with the same name and the extension .old before installing
the latest binaries. Afterwards, all files in .old are erased. If this is not
possible because text files are “busy”, the file and the directory are left.
During reinstallation of the actions|cmds|monitor binaries, ITO tries
once again to delete the entries in the .old directories. If this is not
possible, the ITO control agent generates an error message and stops. For
the location of the actions|cmds|monitor directories and .old
directories see Table 6-3 on page 310.
Solution B Find the still running instance of the actions|cmds|monitor binary
and kill it manually; afterwards re-distribute the actions,, comands, etc.
