Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Found in Dogtag cloning.
-----------------------------------------------------------------
When Dogtag clone is uninstalled and reinstalled on the same slapd instance, the slapd will crash consistently. Reinstalling non-replicated Dogtag does not crash slapd, so this is probably related to replication.
Step to reproduce (see http://pki.fedoraproject.org/wiki/Quick_Start):
1. On master, create DS instance and CA instance.
2. On replica, create DS instance and CA clone.
3. On replica, remove CA clone.
4. On replica, create CA clone again.
During step #4 the slapd will crash and the CA clone installation will be stuck waiting for slapd.
CA clone installation output:
...
pkispawn : INFO ....... executing 'systemctl start pki-tomcatd'
pkispawn : INFO ....... constructing PKI configuration data.
pkispawn : INFO ....... configuring PKI configuration data.
CA clone debug log:
...
[26/Nov/2014:01:17:15][http-bio-8443-exec-3]: Still checking wait_dn 'cn=index1160589769, cn=index, cn=tasks, cn=config' (netscape.ldap.LDAPException: failed to connect to server ldap://vm-064.idm.lab.bos.redhat.com:389 (91))
slapd error log:
...
[26/Nov/2014:01:26:54 -0500] - ldbm: Bringing ca offline...
[26/Nov/2014:01:26:54 -0500] - ldbm: removing 'ca'.
[26/Nov/2014:01:26:54 -0500] - Destructor for instance ca called
[26/Nov/2014:01:26:55 -0500] NSMMReplicationPlugin - multimaster_be_state_change: replica dc=ca,dc=example,dc=com is going offline; disabling replication
[26/Nov/2014:01:26:55 -0500] NSMMReplicationPlugin - agmt="cn=cloneAgreement1-vm-064.idm.lab.bos.redhat.com-pki-tomcat" (vm-084:389): The remote replica has a different database generation ID than the local database. You may have to reinitialize the remote replica, or the local replica.
[26/Nov/2014:01:26:55 -0500] - WARNING: Import is running with nsslapd-db-private-import-mem on; No other process is allowed to access the database
[26/Nov/2014:01:26:58 -0500] - import ca: Workers finished; cleaning up...
[26/Nov/2014:01:26:58 -0500] - import ca: Workers cleaned up.
[26/Nov/2014:01:26:58 -0500] - import ca: Indexing complete. Post-processing...
[26/Nov/2014:01:26:58 -0500] - import ca: Generating numSubordinates complete.
[26/Nov/2014:01:26:58 -0500] - import ca: Flushing caches...
[26/Nov/2014:01:26:58 -0500] - import ca: Closing files...
[26/Nov/2014:01:26:58 -0500] - import ca: Import complete. Processed 82 entries in 3 seconds. (27.33 entries/sec)
[26/Nov/2014:01:26:58 -0500] NSMMReplicationPlugin - multimaster_be_state_change: replica dc=ca,dc=example,dc=com is coming online; enabling replication
-----------------------------------------------------------------
Steps:
1. Set up 2-way MMR -- Master0 and Master1.
2. On each master, create a test backend and configure a VLV index on the backend.
3. On Master1, delete the backend and recreate the same named backend.
3. On Master0, run consumer initialization (bulk import).
If Master1 does not crash, the bug is verified.
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-2015-2351.html