The server has crashed or shut itself down

PingAuthorize Server was shut down by an administrator. Unless the server was forcefully terminated (for example, using kill -9), then messages are written to the error and server.out logs explaining the reason for the shutdown.

PingAuthorize Server was shut down when the underlying system crashed or was rebooted. If this is the case, then running the uptime command on the underlying system shows that it was recently booted.

The PingAuthorize Server process was terminated by the underlying operating system for some reason (for example, the out-of-memory killer on Linux). If this happens, then a message is written to the system error log.

PingAuthorize Server decided to shut itself down in response to a serious problem. At present, this should only occur if the server has detected that the amount of usable disk space has become critically low, or if significant errors during processing have left the server without any remaining worker threads to process operations. If this happens, then messages are written to the error and server.out logs (if disk space is available) to provide the reason for the shutdown.

The JVM in which PingAuthorize Server was running crashed. If this happens, then the JVM should dump a fatal error log (an hs_err_pid<processID>.log file) and potentially a core file.