Hide Forgot
Description of problem: When 'systemctl stop pki-cad' is called, CA process shuts down and exists with exit code 143. While pkicontrol is exiting with exit code 0, systemd still thinks the service has failed as main process exited with non-0 code. Version-Release number of selected component (if applicable): 9.0.17-1 How reproducible: always Steps to Reproduce: 1. Install Fedora 16 in minimal profile 2. Apply all updates from updates-testing 3. Install freeipa-server 4. Configure FreeIPA with ipa-server-install using (default) CA. Actual results: # grep pki-cad /var/log/messages Jan 23 17:20:03 master systemd[1]: pki-cad: control process exited, code=exited status=1 Jan 23 17:20:03 master systemd[1]: Unit pki-cad entered failed state. # systemctl status pki-cad pki-cad - PKI Certificate Authority Server pki-ca Loaded: loaded (/lib/systemd/system/pki-cad@.service; enabled) Active: active (running) since Mon, 23 Jan 2012 17:52:16 +0200; 1h 53min ago Process: 1070 ExecStart=/usr/bin/pkicontrol start ca %i (code=exited, status=0/SUCCESS) Main PID: 1128 (java) CGroup: name=systemd:/system/pki-cad@.service/pki-ca └ 1128 /usr/lib/jvm/jre/bin/java -classpath :/usr/share/tomcat6/bin/bootstrap.jar:/usr/share/tomcat6/bin/tomcat-juli.jar:/usr/share/java/commons-daemon.jar -Dcatalina.... # ipactl stop Stopping CA Service Stopping HTTP Service Stopping DNS Service Stopping KPASSWD Service Stopping KDC Service Stopping Directory Service # systemctl status pki-cad pki-cad - PKI Certificate Authority Server pki-ca Loaded: loaded (/lib/systemd/system/pki-cad@.service; enabled) Active: failed since Mon, 23 Jan 2012 19:45:28 +0200; 6s ago Process: 1555 ExecStopPost=/bin/rm -f /var/run/pki-ca.pid (code=exited, status=0/SUCCESS) Process: 1483 ExecStop=/usr/bin/pkicontrol stop ca %i (code=exited, status=0/SUCCESS) Process: 1070 ExecStart=/usr/bin/pkicontrol start ca %i (code=exited, status=0/SUCCESS) Main PID: 1128 (code=exited, status=143) CGroup: name=systemd:/system/pki-cad@.service/pki-ca Expected results: systemctl status should report service 'stopped'. Additional info:
This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '16'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 16's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 16 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.