Hide Forgot
Description of problem: at ipa startup, customer has the following error: Restarting CA Service Stopping pki-ca: waiting for processes 16466 to exit killing 16466 which did not stop after 30 seconds [WARNING] [ OK ] Traceback (most recent call last): File "/usr/sbin/pki-server", line 89, in <module> cli.execute(sys.argv) File "/usr/sbin/pki-server", line 84, in execute super(PKIServerCLI, self).execute(args) File "/usr/lib/python2.6/site-packages/pki/cli.py", line 195, in execute module.execute(module_args) File "/usr/lib/python2.6/site-packages/pki/server/cli/upgrade.py", line 103, in execute scriptlet.execute() File "/usr/lib/python2.6/site-packages/pki/server/upgrade/__init__.py", line 50, in execute cert = self.subsystem.get_system_cert('subsystem') File "/usr/lib/python2.6/site-packages/pki/server/__init__.py", line 93, in get_system_cert cert['request'] = base64.b64decode(self.config['%s.%s.certreq' % (self.prefix, tag)]) KeyError: 'ca.subsystem.certreq' Starting pki-ca: [ OK ] Version-Release number of selected component (if applicable): pki-ca-9.0.3-45.el6_7.noarch How reproducible: I don't know the root cause of why the value dissapear. Steps to Reproduce: N/A Expected results: Additional info: Fraser has found the workaround in freeipa alias ========================================================= You can resolve the issue by stopping pki-cad, adding 'ca.subsystem.certreq=' (empty value) to CS.cfg, then restarting pki-cad. AFAICT the absense of the certreq field will not cause any problems. I'm still investigating what caused the 'ca.subsystem.certreq' config to disappear from CS.cfg in the first place. =========================================================== thanks, German.
Fix checked into rhel 6.8 branch .. Counting objects: 62, done. Compressing objects: 100% (31/31), done. Writing objects: 100% (32/32), 5.18 KiB, done. Total 32 (delta 18), reused 0 (delta 0) To ssh://git.app.eng.bos.redhat.com/srv/git/pki.git 3637b1f..dd5039f DOGTAG_9_0_RHEL_BRANCH -> DOGTAG_9_0_RHEL_BRANCH Matt will be creating builds. This fix ensures that we only attempt to retrieve this parameter if it exists. Currently, we make no use of this parameter - and if we need it later, we can retrieve it from the database. So, if the parameter does not exist, no error should be seen.
I would suggest something like the following for doc text: Occasionally, upon IPA server startup, an error would be encountered due to a missing *ca.subsystem.certreq* parameter in the from PKI configuration file 'CS.cfg'. Currently, since neither PKI nor IPA services utilize this parameter, code has been added to PKI to ensure that this parameter is only retrieved if it exists.
Verified using version :: pki-*-9.0.3-49.el6.noarch ipa-server-3.0.0-50.el6.x86_64 For verification step refer attachment.
Created attachment 1141155 [details] console.log
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2016-0909.html