RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1077358 - pki-tomcat cannot be started after installation of ipa replica with ca
Summary: pki-tomcat cannot be started after installation of ipa replica with ca
Keywords:
Status: CLOSED DUPLICATE of bug 1077348
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: pki-core
Version: 7.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Matthew Harmsen
QA Contact: Asha Akkiangady
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-03-17 19:40 UTC by Matthew Harmsen
Modified: 2020-10-04 20:39 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-03-17 19:55:02 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github dogtagpki pki issues 1383 0 None None None 2020-10-04 20:39:32 UTC

Description Matthew Harmsen 2014-03-17 19:40:22 UTC
This bug is created as a clone of upstream ticket:
https://fedorahosted.org/pki/ticket/816

I tried to install ipa replica (from fedora 19 -> fedora 20)
with command 
**ipa-replica-install --setup-ca --setup-dns --no-forwarders /var/lib/ipa/replica-info-vm-171.idm.lab.example.com.gpg**
but installation of replica failed, because certificate server instance could not be started
{{{
Configuring certificate server (pki-tomcatd): Estimated time 3 minutes 30 seconds
  [1/19]: creating certificate server user
  [2/19]: configuring certificate server instance
  [3/19]: stopping certificate server instance to update CS.cfg
  [4/19]: disabling nonces
  [5/19]: set up CRL publishing
  [6/19]: starting certificate server instance

Your system may be partly configured.
Run /usr/sbin/ipa-server-install --uninstall to clean up.

CA did not start in 240s
}}}

I think that the most important part from log files is:
{{{
bash# cat pki/pki-tomcat/ca/system
0.localhost-startStop-1 - [11/Dec/2013:17:42:55 CET] [3] [3] Cannot build CA chain. Error java.security.cert.CertificateException: Certificate is not a PKCS #11 certificate
0.localhost-startStop-1 - [11/Dec/2013:17:42:56 CET] [13] [3] authz instance DirAclAuthz initialization failed and skipped, error=Property internaldb.ldapconn.port missing value
}}}


Version of installed software:
{{{
bash# rpm -q freeipa-server pki-ca
freeipa-server-3.3.3-2.fc20.x86_64
pki-ca-10.1.0-1.fc20.noarch
}}}

Additional informations:
I was able to install ipa replica with ca (from fedora 19 -> fedora 19)
{{{
bash# rpm -q freeipa-server pki-ca
freeipa-server-3.3.3-2.fc19.x86_64
pki-ca-10.0.6-1.fc19.noarch
}}}

I will attach all log files and I can provide any other information to fix this bug.

Comment 1 Nathan Kinder 2014-03-17 19:55:02 UTC

*** This bug has been marked as a duplicate of bug 1077348 ***


Note You need to log in before you can comment on or make changes to this bug.