ipa-replica-install /var/lib/ipa/replica-info-auth1.qai.expertcity.com.gpg Directory Manager (existing master) password:
Run connection check to master Check connection from replica to remote master 'authmgr1.ops.expertcity.com': Directory Service: Unsecure port (389): OK Directory Service: Secure port (636): OK Kerberos KDC: TCP (88): OK Kerberos KDC: UDP (88): OK Kerberos Kpasswd: TCP (464): OK Kerberos Kpasswd: UDP (464): OK HTTP Server: Unsecure port (80): OK HTTP Server: Secure port (443): OK
Connection from replica to master is OK. Start listening on required ports for remote master check Get credentials to log in to remote master admin@EXPERTCITY.COM password:
Execute check on remote master Check connection from master to remote replica 'auth1.qai.expertcity.com': Directory Service: Unsecure port (389): OK Directory Service: Secure port (636): OK Kerberos KDC: TCP (88): OK Kerberos KDC: UDP (88): OK Kerberos Kpasswd: TCP (464): OK Kerberos Kpasswd: UDP (464): OK HTTP Server: Unsecure port (80): OK HTTP Server: Secure port (443): OK
Connection from master to replica is OK.
Connection check OK Configuring ntpd [1/4]: stopping ntpd [2/4]: writing configuration [3/4]: configuring ntpd to start on boot [4/4]: starting ntpd done configuring ntpd. Configuring directory server: Estimated time 1 minute [1/29]: creating directory server user [2/29]: creating directory server instance [3/29]: adding default schema [4/29]: enabling memberof plugin [5/29]: enabling referential integrity plugin [6/29]: enabling winsync plugin [7/29]: configuring replication version plugin [8/29]: enabling IPA enrollment plugin [9/29]: enabling ldapi [10/29]: configuring uniqueness plugin [11/29]: configuring uuid plugin [12/29]: configuring modrdn plugin [13/29]: enabling entryUSN plugin [14/29]: configuring lockout plugin [15/29]: creating indices [16/29]: configuring ssl for ds instance [17/29]: configuring certmap.conf [18/29]: configure autobind for root [19/29]: configure new location for managed entries [20/29]: restarting directory server [21/29]: setting up initial replication Starting replication, please wait until this has completed. Update in progress Update in progress Update in progress Update in progress Update in progress Update in progress [authmgr1.ops.expertcity.com] reports: Update failed! Status: [-2 Total update abortedSystem error] creation of replica failed: Failed to start replication
Your system may be partly configured. Run /usr/sbin/ipa-server-install --uninstall to clean up.
Stacktrace 389stacktrace.txt
0001-Ticket-294-389-DS-Segfaults-during-replica-install-i.patch 0001-Ticket-294-389-DS-Segfaults-during-replica-install-i.patch
ack
To ssh://git.fedorahosted.org/git/389/ds.git f98310c..9e65c7a master -> master commit changeset:9e65c7a/389-ds-base Author: Rich Megginson rmeggins@redhat.com Date: Mon Feb 13 20:14:12 2012 -0700 Reviewed by: mreynolds (Thanks!) Branch: master Fix Description: Have to check for NULL childnrdn return from slapi_rdn_get_prev_ext(). Platforms tested: RHEL6 x86_64 Flag Day: no Doc impact: no
To ssh://git.fedorahosted.org/git/389/ds.git dc731e2..7373fbf 389-ds-base-1.2.10 -> 389-ds-base-1.2.10 commit changeset:7373fbf/389-ds-base Author: Rich Megginson rmeggins@redhat.com Date: Mon Feb 13 20:14:12 2012 -0700 Branch: 389-ds-base-1.2.10 (cherry picked from commit changeset:9e65c7a/389-ds-base)
Ticket has been cloned to Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=790491
Added initial screened field value.
Metadata Update from @rmeggins: - Issue assigned to rmeggins - Issue set to the milestone: 1.2.10.1
389-ds-base is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in 389-ds-base's github repository.
This issue has been cloned to Github and is available here: - https://github.com/389ds/389-ds-base/issues/294
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. We apologize for all inconvenience.
Metadata Update from @spichugi: - Issue close_status updated to: wontfix (was: Fixed)
Login to comment on this ticket.