The PKI server generates the following message when it is started for the first time during installation before being configured by pkispawn:
Sep 23 14:14:16 server.example.com server[13604]: CMS Warning: FAILURE: Cannot build CA chain. Error java.security.cert.CertificateException: Certificate is not a PKCS #11 certificate|FAILURE: authz instance DirAclAuthz initialization failed and skipped, error=Property internaldb.ldapconn.port missing value|
This is actually a normal part of the installation. If the installation works fine, usually the error message can be ignored safely. However, if the installation fails, the message can be misleading the investigation so the actual error does not get resolved as quickly.
Possible solutions: 1. The code that generates the error message should be disabled during installation. 2. The pkispawn should prepare everything needed by the server before running it for the first time.
Per CS/DS Meeting of 10/12/2015 - 10.3 - Nice to Have
This code change should be encountered during normal QE testing, and therefore does not merit its own specific Bugzilla Bug.
Per PKI Bug Council of 06/23/2016: 10.4
See also ticket #2400.
See also https://bugzilla.redhat.com/show_bug.cgi?id=1392636.
See also https://bugzilla.redhat.com/show_bug.cgi?id=1322059.
See also https://bugzilla.redhat.com/show_bug.cgi?id=1398600.
Metadata Update from @edewata: - Issue assigned to edewata - Issue set to the milestone: UNTRIAGED
Metadata Update from @mharmsen: - Custom field feature adjusted to None - Custom field proposedmilestone adjusted to None - Custom field proposedpriority adjusted to None - Custom field reviewer adjusted to None - Custom field version adjusted to None - Issue close_status updated to: None - Issue set to the milestone: 10.5 (was: UNTRIAGED)
[20171025] - Offline Triage ==> 10.6
Metadata Update from @mharmsen: - Issue set to the milestone: 10.6 (was: 10.5)
Per 10.5.x/10.6 Triage: FUTURE
RHBZ: CLOSED UPSTREAM
alee: benign error message
Metadata Update from @mharmsen: - Custom field rhbz reset (from https://bugzilla.redhat.com/show_bug.cgi?id=1378037) - Issue set to the milestone: FUTURE (was: 10.6)
Dogtag PKI is moving from Pagure issues to GitHub issues. This means that existing or new issues will be reported and tracked through Dogtag PKI's GitHub Issue tracker.
This issue has been cloned to GitHub and is available here: https://github.com/dogtagpki/pki/issues/2174
If you want to receive further updates on the issue, please navigate to the GitHub issue and click on Subscribe button.
Subscribe
Thank you for understanding, and we apologize for any inconvenience.
Metadata Update from @dmoluguw: - Issue close_status updated to: migrated - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.