#1255 Restart fails after upgrade
Closed: Fixed None Opened 8 years ago by edewata.

Sometimes Tomcat fails to restart after upgrade:

$ systemctl start pki-tomcatd@pki-tomcat.service
Failed to issue method call: Unit pki-tomcatd@pki-tomcat.service failed to load: No such file or directory.

To fix the problem the systemd configuration has to be reloaded:

$ systemctl daemon-reload

Possible solutions:

  • Investigate what operation during upgrade actually causes the problem and fix it.
  • Reload the systemd configuration automatically at the appropriate time during upgrade.

Proposed milestone: 10.2.2

Per 10.2.2 Triage meeting of 02/24/2015: 10.2.2

(Matt to assist with this ticket as needed)

In other cases systemctl just generates a warning:

$ systemctl restart pki-tomcatd@pki-tomcat.service
Warning: Unit file of pki-tomcatd@pki-tomcat.service changed on disk,
'systemctl daemon-reload' recommended.

The warning is generated because the unit file (i.e. /usr/lib/systemd/system/pki-tomcatd@.service) was updated during upgrade.

master: 7b1d897ba4cf9de1459d2aad37e969ce9a93a05a

10.2.1 branch: 95e7fb202d08452532a863a4919710fb07dbf12f

Metadata Update from @edewata:
- Issue assigned to edewata
- Issue set to the milestone: 10.2.2

6 years ago

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:

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.

Login to comment on this ticket.