This issue was migrated from Pagure Issue #3080.Originally filed by cheimes on 2018-11-22
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
Proposal
Log systemd or journald output, e.g. journalctl -u pki-tomcatdpki-tomcat.service -n 30 -o cat or systemctl status pki-tomcatdpki-tomcat.service
This issue was migrated from Pagure Issue #3080.Originally filed by cheimes on 2018-11-22
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
Proposal
Log systemd or journald output, e.g.
journalctl -u pki-tomcatdpki-tomcat.service -n 30 -o catorsystemctl status pki-tomcatdpki-tomcat.service