10.2. Debugging Self-Tests Failures

In the event of self-test failure, the Certificate System instance will stop completely and will not respond to any HTTP or HTTPS requests.

To diagnose a manually run self-test failure, refer to the various logs described in Section 10.2.1, “Self-Test Logging”. Often other logs are useful as well, including debug logs. For more information on subsystem logs, refer to Chapter 13, Configuring Subsystem Logs. For more information on debug logs, refer to the Logs section under the Certificate System Architecture Overview in the Red Hat Certificate System Planning, Installation, and Deployment Guide (Common Criteria Edition).

Common causes of self-test failures are services (such as LDAP) are down or unreachable, certificates are expired, or the system configuration is wrong. A precise cause of self-test failure is given in the logs.

After the cause of the self-test failure is identified and fixed, please restart the Certificate System server to resume normal operations:

systemctl restart pki-tomcatd-nuxwdog@instance_name.service

# systemctl restart pki-tomcatd-nuxwdog@instance_name.service