Hide Forgot
This bug is created as a clone of upstream ticket: https://pagure.io/dogtagpki/issue/2699 Currently if selftest fails during startup the subsystem will undeploy (i.e. disable) itself to prevent partially running service which could confuse other services that depend on it. The admin is expected to investigate and fix the failure, then reenable the subsystem manually with this command (see http://pki.fedoraproject.org/wiki/SelfTest): $ pki-server subsystem-enable ca The selftest error and the instruction to reenable the subsystem is written into the log, but often times the admin does not notice that immediately, leading to confusions. One possible solution is to automatically reenable all subsystems on Tomcat restart. If the selftest is still failing the subsystem will shut itself down as before, but at least the admin is no longer required to reenable the subsystem manually.
Fixed in master: * https://github.com/dogtagpki/pki/commit/8016ed7972d9211e7f0db14e45bc9658a7b292ef
FYI, the auto-enable behavior can be configured using the PKI_SERVER_AUTO_ENABLE_SUBSYSTEMS property in pki.conf. See http://pki.fedoraproject.org/wiki/SelfTest
*** Bug 1432229 has been marked as a duplicate of this bug. ***
[root@csqa4-guest01 hsm_setup]# rpm -qi pki-server Name : pki-server Version : 10.4.1 Release : 10.el7 Architecture: noarch Install Date: Friday 23 June 2017 12:09:25 AM EDT Group : System Environment/Base Size : 4634270 License : GPLv2 Signature : (none) Source RPM : pki-core-10.4.1-10.el7.src.rpm Build Date : Tuesday 20 June 2017 01:23:22 AM EDT Build Host : ppc-046.build.eng.bos.redhat.com Relocations : (not relocatable) Packager : Red Hat, Inc. <http://bugzilla.redhat.com/bugzilla> Vendor : Red Hat, Inc. URL : http://pki.fedoraproject.org/ Summary : Certificate System - PKI Server Framework After setting PKI_SERVER_AUTO_ENABLE_SUBSYSTEMS=True in /etc/pki/pki.conf the subsystem is not disabled, when the selftests fail the subsystem is simply shutdown instead of being disabled.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2017:2110