Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 790491 - 389 DS Segfaults during replica install in FreeIPA
389 DS Segfaults during replica install in FreeIPA
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: 389-ds-base (Show other bugs)
6.3
Unspecified Unspecified
unspecified Severity unspecified
: rc
: ---
Assigned To: Rich Megginson
IDM QE LIST
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2012-02-14 11:31 EST by Rich Megginson
Modified: 2012-06-20 03:14 EDT (History)
5 users (show)

See Also:
Fixed In Version: 389-ds-base-1.2.10.1-1.el6
Doc Type: Bug Fix
Doc Text:
Cause: Doing a replica initialization. Consequence: Server crashes. Fix: A NULL pointer dereference was found and fixed that would occur under certain conditions during replica initialization. Result: Server does not crash during replica initialization.
Story Points: ---
Clone Of:
Environment:
Last Closed: 2012-06-20 03:14:46 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2012:0813 normal SHIPPED_LIVE Low: 389-ds-base security, bug fix, and enhancement update 2012-06-19 15:29:15 EDT

  None (edit)
Description Rich Megginson 2012-02-14 11:31:53 EST
This bug is created as a clone of upstream ticket:
https://fedorahosted.org/389/ticket/294

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.
Comment 3 Rich Megginson 2012-04-16 17:00:14 EDT
steps to verify - verify no regressions/crashes during mmr acceptance, stress, long duration, etc.
Comment 4 Amita Sharma 2012-05-24 07:32:45 EDT
no regression noticed, marking as VERIFIED.
Comment 5 Rich Megginson 2012-05-24 19:43:02 EDT
    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
Cause: Doing a replica initialization.
Consequence: Server crashes.
Fix: A NULL pointer dereference was found and fixed that would occur under certain conditions during replica initialization.
Result: Server does not crash during replica initialization.
Comment 6 errata-xmlrpc 2012-06-20 03:14:46 EDT
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.

http://rhn.redhat.com/errata/RHSA-2012-0813.html

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