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.