On a host I have installed CA, KRA, OCSP and TKS on one Tomcat Instance as masters and CA, KRA, TKS clones on another tomcat instance. If i try to clone the master OCSP I get the following error.
Exception from Java Configuration Servlet: Errors in configuring CA publishing to OCSP: LDAP operation failure - cn=CN-PKI CA Signing Certificate_O-redhat,dc=pki-ocsp netscape.ldap.LDAPException: error result (68)
Clone OCSP parameters config file cloneocsp_instance.inf
Master OCSP config file ocsp_instance.inf
Per CS/DS meeting of 06/30/2014, proposed Milestone: Dogtag 10.2.3
I tried doing a browser configuration for clone OCSP using the parameters skip_configuration= True in pkispawn clone ocsp file but it failed.
I get this error in spawn log:
2014-08-06 13:31:30 pkispawn : DEBUG ........... No connection - server may still be down 2014-08-06 13:31:30 pkispawn : DEBUG ........... No connection - exception thrown: HTTPSConnectionPool(host='zippyvm5.idm.lab.eng.rdu2.redhat.com', port=30002): Max retries exceeded with url: /ocsp/admin/ocsp/getStatus (Caused by : [Errno 111] Connection refused) 2014-08-06 13:31:31 pkispawn : DEBUG ........... No connection - server may still be down 2014-08-06 13:31:31 pkispawn : DEBUG ........... No connection - exception thrown: HTTPSConnectionPool(host='zippyvm5.idm.lab.eng.rdu2.redhat.com', port=30002): Max retries exceeded with url: /ocsp/admin/ocsp/getStatus (Caused by : [Errno 111] Connection refused) 2014-08-06 13:31:43 pkispawn : DEBUG ........... 0OCSPrunning10.2.0-0.1.20140701T0343zgit7b28698.fc20 2014-08-06 13:31:44 pkispawn : INFO ....... constructing PKI configuration data. 2014-08-06 13:31:44 pkispawn : INFO ....... configuring PKI configuration data. 2014-08-06 13:31:49 pkispawn : DEBUG ....... Error Type: ParseError 2014-08-06 13:31:49 pkispawn : DEBUG ....... Error Message: not well-formed (invalid token): line 1, column 0 2014-08-06 13:31:49 pkispawn : DEBUG ....... File "/usr/sbin/pkispawn", line 514, in main rv = instance.spawn(deployer) File "/usr/lib/python2.7/site-packages/pki/server/deployment/scriptlets/configuration.py", line 131, in spawn json.dumps(data, cls=pki.encoder.CustomTypeEncoder)) File "/usr/lib/python2.7/site-packages/pki/server/deployment/pkihelper.py", line 3559, in configure_pki_data root = ET.fromstring(e.response.text) File "/usr/lib64/python2.7/xml/etree/ElementTree.py", line 1300, in XML parser.feed(text) File "/usr/lib64/python2.7/xml/etree/ElementTree.py", line 1642, in feed self._raiseerror(v) File "/usr/lib64/python2.7/xml/etree/ElementTree.py", line 1506, in _raiseerror raise err
The journal log errors are: Aug 06 13:31:20 zippyvm5.idm.lab.eng.rdu2.redhat.com server[24136]: INFO: Initializing ProtocolHandler ["http-bio-30002"] Aug 06 13:31:20 zippyvm5.idm.lab.eng.rdu2.redhat.com server[24136]: JSSSocketFactory init - exception thrown:java.lang.NullPointerException Aug 06 13:31:20 zippyvm5.idm.lab.eng.rdu2.redhat.com server[24136]: Aug 06, 2014 1:31:20 PM org.apache.catalina.startup.Catalina load
proposed Milestone: 10.2.2 - Per Dogtag 10.2.3 meeting of 09/25/2014
Per Dogtag 10.2.X meeting of 01/14/2015: Milestone 10.2 Backlog
Per 10.2.3 TRIAGE meeting of 02/26/2015: 10.3
NOTE: Moved from 10.2 Backlog since it was not a documentation/man page issue.
Fix checked in. OCSP clone now can be installed and operates as expected.
Metadata Update from @saipandi: - Issue assigned to jmagne - Issue set to the milestone: 10.2.4
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/1623
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.