During installation pki-spawn starts pki-tomcat.service and waits until the service is available. Sometimes pki-tomcat fails to start. The pki-spawn log does not contain any information why the service fails to start. As an engineer I would like to have better debug information in the pki-spawn log
Log systemd or journald output, e.g. journalctl -u pki-tomcatd@pki-tomcat.service -n 30 -o cat or systemctl status pki-tomcatd@pki-tomcat.service
journalctl -u pki-tomcatd@pki-tomcat.service -n 30 -o cat
systemctl status pki-tomcatd@pki-tomcat.service
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/3197
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.