Runtime Issues and Bugs

Issues include information that you should know about, such as prerequisites, tips, troubleshooting hints, and bugs. Bugs are a subset of issues. Bugs have tracking numbers that are shown in parentheses. For updates on bugs and to obtain patches, see the SunSolve^SM web site at http://sunsolve.sun.com.

Runtime Issues

Attempting to Stop the Agent With the pa stop Command Results in the Message agent process (PID) error waiting for process to exit: child process lost (is SIGCHLD ignored or trapped?)

Workaround: You can safely ignore this message. To confirm that the agent has been stopped, run the command ps -elf | grep paAgent | grep -v grep.

Selecting PrimeAlert System Monitor > User Statistics > Console User value Always Reports None

The user whose TTY device is console, tty1, or :0 is reported as the console user. Either no user is logged into the console, or the TTY is not console, tty1, or :0.

Workaround: None.

The pa stop Command Indicates That the Agent Has Been Stopped, But the paAgent Process Still Exists

This rare condition is linked to multiple simultaneous attempts to start the agent.

Workaround: Kill the PID of the paAgent process. If that fails, use the kill -9 command.

Runtime Bugs

When PrimeAlert System Monitor Reports on Idle Processes, the Number of Sleeping Processes Does Not Match the Number Reported as State S in ps -elf (5009340)

The number of idle processes as reported in the PrimeAlert System Monitor module is the number of sleeping processes that are swapped in ps -elf. The arguments of such processes are encased in brackets ([] ). The number of sleeping processes reported in the System Monitor module is the number of sleeping processes minus the number of sleeping processes swapped out.

The Info Tab for the Linux Agent Host Is Missing Information (5010084)

The Info tab for the Linux Agent host in the Sun Management Center console is missing information. The netmask information is missing. Timezone is shown as unknown.

Workaround: None.

No es-setup Command on the Linux Agent to Change the Agent Setup After Installation (5007871)

Workaround: You can change settings for the Linux Agent by running the install script from the installation source directory or editing the domain-config.x file. For more information, see Reconfiguring the Linux Agent.

Linux Agent Does Not Support an Optional Install Directory (5010061)

Workaround: The agent is installed in /opt/PrimeAlert with configuration files in /var/opt/PrimeAlert. If another directory is more suitable, use a symbolic link.

If a DataView Table Is Made for a Linux Agent Property (such as Filesystem Usage/System Load), the Property Column Does Not list the Property Name But Shows N/A (5009314)

Workaround: None.