dogtagpki

#482 pkidaemon should use getStatus servlet to determine status
Closed: wontfix Opened by mharmsen.

Closed: wontfix
Reopen Issue

The following was observed:

pkidaemon status tomcat pki-tomcat

Status for pki-tomcat: pki-tomcat is running ..
    [CA Status Definitions]
    Unsecure Port       = http://dogtag18.usersys.redhat.com:8080/ca/ee/ca
    Secure Agent Port   = https://dogtag18.usersys.redhat.com:8443/ca/agent/ca
    Secure EE Port      = https://dogtag18.usersys.redhat.com:8443/ca/ee/ca
    Secure Admin Port   = https://dogtag18.usersys.redhat.com:8443/ca/services
    EE Client Auth Port = https://dogtag18.usersys.redhat.com:8443/ca/eeca/ca
    PKI Console Port    = pkiconsole https://dogtag18.usersys.redhat.com:8443/ca
    Tomcat Port         = 8005 (for shutdown)
    [CA Configuration Definitions]
    PKI Instance Name:   pki-tomcat
    PKI Subsystem Type:  Root CA (Security Domain)
    Registered PKI Security Domain Information:
    ==========================================================================
    Name:  usersys.redhat.com Security Domain
    URL:   https://dogtag18.usersys.redhat.com:8443
    ==========================================================================

However, when attempting to perform a command-line 'pki' command, and then attempting to launch a browser to "http://dogtag18.usersys.redhat.com:8080/ca/services", an error 500 was returned, and it was determined that the server had not completely started up correctly.

It was suggested by alee that we should change 'pkidaemon' to utilize the getStatus servlet rather than just checking for a java process and/or port.

See also #1496.

The pkidaemon output often misleads investigation, so it should be fixed soon.

Metadata Update from @mharmsen:
- Issue set to the milestone: 10.4

This ticket will not be fixed since pkidaemon will be consolidated into pki-server:

https://pagure.io/dogtagpki/issue/1496 - Consolidate pkidaemon into pki-server.

Metadata Update from @mharmsen:
- Custom field component adjusted to General (was: Process Management)
- Custom field reviewer adjusted to ''
- Custom field version adjusted to ''
- Issue close_status updated to: wontfix
- Issue set to the milestone: 10.4.0 (was: 10.4)
- Issue status updated to: Closed (was: Open)

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/1053

If you want to receive further updates on the issue, please navigate to the
GitHub issue and click on Subscribe button.

Thank you for understanding, and we apologize for any inconvenience.
Metadata
None
None
None
None
Low
defect
General
Installer Cleanup/ Improvement
Community
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.