dogtagpki

#318 Dogtag 10: systemctl is not removing PID file
Closed: Invalid Opened by mharmsen.

Closed: Invalid
Reopen Issue

When utilizing an instance created via "pkispawn", neither "pkidestroy" nor, more appropriately, "systemctl stop" as called by "pkidestroy", are removing the pid file under /var/run.

While this may have been broken at sometime in the past, it no longer appears to be an issue.

Tested with the following packages:

  • pki-server-10.0.0-2.fc18.noarch (/usr/sbin/pkispawn, /usr/sbin/pkidestroy)
  • systemd-195-10.fc18.x86_64 (/bin/systemctl)

The pid file located under '/var/run/pki/tomcat/pki-tomcat.pid' was always created when a 'systemctl start pki-tomcat.service' was performed (presuming one did not already exist, removed when a 'systemctl stop pki-tomcatd@pki-tomcat.service ' was performed, and re-created when a 'systemctl restart pki-tomcatd@pki-tomcat.service' was performed.

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

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

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
Normal
defect
Process Management
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.