While trying to run pki CLI, I run into the class loading problem for SLF4J.
The following is the trace of the error:
[root@localhost /]# pki -d ~/.dogtag/pki-tomcat/ca/alias client-cert-find SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder". SLF4J: Defaulting to no-operation (NOP) logger implementation SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details. --------------------- No certificates found ---------------------
Metadata Update from @mharmsen: - Custom field component adjusted to General - Custom field feature adjusted to '' - Custom field origin adjusted to Community - Custom field proposedmilestone adjusted to '' - Custom field proposedpriority adjusted to '' - Custom field reviewer adjusted to '' - Custom field type adjusted to defect - Custom field version adjusted to '' - Issue set to the milestone: 0.0 NEEDS_TRIAGE
Fixed in master:
Metadata Update from @edewata: - Issue close_status updated to: fixed - Issue priority set to: major - Issue set to the milestone: 10.4.7 (was: 0.0 NEEDS_TRIAGE) - Issue status updated to: Closed (was: Open)
Metadata Update from @edewata: - Issue assigned to edewata
Metadata Update from @mharmsen: - Custom field fixedinversion adjusted to pki-core-10.4.7-1.fc27
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/2834
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.
Login to comment on this ticket.