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 1335423 - heap corruption at schema replication.
Summary: heap corruption at schema replication.
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: 389-ds-base
Version: 7.2
Hardware: All
OS: Linux
urgent
urgent
Target Milestone: rc
: ---
Assignee: Noriko Hosoi
QA Contact: Viktor Ashirov
URL:
Whiteboard:
Depends On: 1303641
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-05-12 08:35 UTC by Marcel Kolaja
Modified: 2019-11-14 08:00 UTC (History)
10 users (show)

Fixed In Version: 389-ds-base-1.3.4.0-31.el7_2
Doc Type: Bug Fix
Doc Text:
389-ds-base version 1.3.2 and later is compliant with the schema definition described in RFC 4512, which may not allow the schema to be used by the older versions. To ease migration from earlier versions, the "nsslapd-enquote-sup-oc" was introduced. However, this parameter contained a bug which prevented handling old schema styles such as 'SYNTAX oid' in single quotes. This update fixes that bug, and you can now use single quotes with older schema styles. Additionally, this update introduces the "LDAP_SCHEMA_ALLOW_QUOTES" environment variable which adds support for older style schema in the schema directory. To enable this functionality, set LDAP_SCHEMA_ALLOW_QUOTED="on" in the /etc/sysconfig/dirsrv-INSTANCE configuration file.
Clone Of: 1303641
Environment:
Last Closed: 2016-06-23 16:23:10 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:1298 0 normal SHIPPED_LIVE 389-ds-base bug fix update 2016-06-23 20:14:06 UTC

Description Marcel Kolaja 2016-05-12 08:35:44 UTC 
This bug has been copied from bug #1303641 and has been proposed
to be backported to 7.2 z-stream (EUS).
Comment 8 Amita Sharma 2016-06-01 07:19:47 UTC 
Thanks Noriko for the steps.


[root@ibm-x3650m4-01-vm-11 schema]# rpm -qa | grep 389-ds-base
389-ds-base-libs-1.3.4.0-31.el7_2.x86_64
389-ds-base-1.3.4.0-31.el7_2.x86_64

[root@ibm-x3650m4-01-vm-11 schema]# vim 01core389.ldif
[root@ibm-x3650m4-01-vm-11 schema]# systemctl start dirsrv@ibm-x3650m4-01-vm-11

My standalone instance is working fine and starting up after the mentioned changes with the syntax value in quotes for attribute.
Hence, Marking bug as verified.

 I will also work on the another scenario mentioned and report issue in case of any.
Comment 13 errata-xmlrpc 2016-06-23 16:23:10 UTC 
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://access.redhat.com/errata/RHBA-2016:1298
Note You need to log in before you can comment on or make changes to this bug.