While configuring subsystems(with ECC) using pkispawn it takes large amount of time. For installing KRA, it took 18 minutes nearly and for other subsystems also it is taking long time.
<code snip> 2016-01-05 04:04:09 pkispawn : INFO ....... rm -f /opt/FoobarKRA1/kra/alias/noise 2016-01-05 04:04:09 pkispawn : INFO ....... BtoA /opt/FoobarKRA1/kra/alias/admin_pkcs10.bin /opt/FoobarKRA1/kra/alias/admin_pkcs10.bin.asc 2016-01-05 04:04:09 pkispawn : INFO ....... configuring PKI configuration data. 2016-01-05 04:22:42 pkispawn : DEBUG ....... status: 0 2016-01-05 04:22:42 pkispawn : DEBUG ....... tag: transport 2016-01-05 04:22:42 pkispawn : DEBUG ....... cert </code snip>
<code snip> 2016-01-05 04:23:43 pkispawn : INFO ....... rm -f /opt/FoobarOCSP/ocsp/alias/noise 2016-01-05 04:23:43 pkispawn : INFO ....... BtoA /opt/FoobarOCSP/ocsp/alias/admin_pkcs10.bin /opt/FoobarOCSP/ocsp/alias/admin_pkcs10.bin.asc 2016-01-05 04:23:43 pkispawn : INFO ....... configuring PKI configuration data. 2016-01-05 04:35:17 pkispawn : DEBUG ....... status: 0 2016-01-05 04:35:17 pkispawn : DEBUG ....... tag: signing 2016-01-05 04:35:17 pkispawn : DEBUG ....... cert: </code snip>
Steps to Reproduce:
1.Use the configuration file attached 2.use pkispawn in silent mode and install all subsystems. 3.Monitor logs and timestamp to see how much time it took.
Actual results:
Installation is very slow.Takes sometimes 35 minutes also.
Expected results:
Installation of subsystems should be quicker
Additional Information:
The logs and cfg files used are attached to the associated bug.
The issue turned out to be a lack of entropy on a VM.
This was addressed by using haveged as a work-around.
Metadata Update from @gkapoor: - Issue set to the milestone: 10.3.0
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/2274
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.