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.
Cause: There was a bug in calculating the size of the string format entry which was shorter than the real size when there are lots of deleted attributes.
Consequence: It overflows the allocated memory with the longer size of entry and crashes the server.
Fix: Fixed the calculation.
Result: No more overflow and the server crash.
{{{
Description of problem:
Our multimaster environment with four nodes is attached to the Novel IDM.
When large dataset is migrated to the 389-ds it just dies.
Version-Release number of selected component (if applicable):
Name : 389-ds-base
Arch : x86_64
Version : 1.3.5.10
Release : 15.el7_3
How reproducible:
I just enable driver from the Novel to start synching data to the multimaster cluster.
Actual results:
* [4373826.739387] ns-slapd[2666]: segfault at 7f68b4000000 ip 00007f68b29513ac
sp 00007f68807eef98 error 4 in libc-2.17.so[7f68b28d1000+1b6000]
* [4720607.858694] traps: ns-slapd[21687] general protection ip:7f3545b5cdab
sp:7f35107e6240 error:0 in libc-2.17.so[7f3545ade000+1b6000]
Expected results:
Data should be synched
}}}
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-2017-0667.html
{{{ Description of problem: Our multimaster environment with four nodes is attached to the Novel IDM. When large dataset is migrated to the 389-ds it just dies. Version-Release number of selected component (if applicable): Name : 389-ds-base Arch : x86_64 Version : 1.3.5.10 Release : 15.el7_3 How reproducible: I just enable driver from the Novel to start synching data to the multimaster cluster. Actual results: * [4373826.739387] ns-slapd[2666]: segfault at 7f68b4000000 ip 00007f68b29513ac sp 00007f68807eef98 error 4 in libc-2.17.so[7f68b28d1000+1b6000] * [4720607.858694] traps: ns-slapd[21687] general protection ip:7f3545b5cdab sp:7f35107e6240 error:0 in libc-2.17.so[7f3545ade000+1b6000] Expected results: Data should be synched }}}