Administrator's Guide
Troubleshooting
Troubleshooting
Appendix G
248
System Manager appears to hang
❏ This may result if the System Manager is in the process of resyncing a large number
of alerts from a specific host. There are two possible workarounds for this problem:
• Wait. The System Manager will resume normal behavior when it completes
resynchronizing.
• Kill the System Manager. Move the file /var/opt/ids/alert.log to another
name on the agent host with which the System Manager is attempting to
resynchronize; then restart the System Manager.
❏ The System Manager may also hang and not refresh itself as a result of interaction
with the System Manager screen (for example, when a user attempts to resize the
screen). This appears to be a synchronization problem between the native window
manager (typically, mwm) and the Java windowing manager. Restarting the native
window manager may resolve the problem; if not, the System Manager should be
restarted.
System Manager does not let you save files to specific directories
❏ Verify that the user ids has read/write permission for the directory to which you are
trying to save a file.
System Manager does not start after idsgui is started
❏ Verify that the DISPLAY environment variable is set correctly.
❏ Verify that the correct Java version and required patches are installed. Refer to the
Release Notes cited in “Documentation” on page 2 for specific version information.
Check /var/opt/ids/gui/guiError.log for Java errors.
❏ If Java is properly installed, the swlist command may be running too slowly. Verify
this by running swlist. If the problem persists, contact HP support.
System Manager starts with no borders or title bar in X client
programs on Windows
❏ This sometimes happens when Reflection X (or other X client programs on Microsoft
Windows) has been running for a while. Quit, restart the program, relogin to your
HP-UX HIDS administration system, and restart the System Manager. If the
problem persists, contact HP support.
System Manager times out on agent functions such as Activate
and Status Poll
❏ This may be the result of one of these problems: (1) idsagent has hung, (2) idsagent
has died or is not responding properly, or (3) the System Manager is expecting
responses back from the idsagent too quickly.
•Ifidsagent appears to have hung, restart idsagent. See “Forcing Active Agent
to Reread Configuration File” on page 205.