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.

Bug 1044193

Summary: default nsslapd-sasl-max-buffer-size should be 2MB
Product: Red Hat Enterprise Linux 7 Reporter: Nathan Kinder <nkinder>
Component: 389-ds-baseAssignee: Rich Megginson <rmeggins>
Status: CLOSED ERRATA QA Contact: Viktor Ashirov <vashirov>
Severity: unspecified Docs Contact:
Priority: low    
Version: 7.0CC: mreynolds, nhosoi, pasteur, sauchter, spoore
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: 389-ds-base-1.3.3.1-1.el7 Doc Type: Bug Fix
Doc Text:
Cause: Heavy sasl based ldap traffic Consequence: The sasl buffer could exceed its limit Fix: Increase the sasl max buffer size to be the same as the default max BER size. Result: The server is much less likely to exceed the buffer.
Story Points: ---
Clone Of:
: 1136882 (view as bug list) Environment:
Last Closed: 2015-03-05 09:32:47 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1136882    

Description Nathan Kinder 2013-12-17 21:50:24 UTC
This bug is created as a clone of upstream ticket:
https://fedorahosted.org/389/ticket/47457

IPA migrate easily runs into the default 64KB limit - we should increase the limit to 2MB to match the sasl and ber size limit.

Comment 1 mreynolds 2014-04-22 20:38:15 UTC
There are no simple verification steps for this bug, as it involves setting up IPA and run it under a lot of load.

Comment 3 Scott Poore 2015-01-16 23:31:15 UTC
Verified.

Version ::

389-ds-base-1.3.3.1-11.el7.x86_64
ipa-server-4.1.0-15.el7.x86_64

Results ::

Quick check:

[root@rhel7-1 ~]# ldapsearch -x -D "cn=Directory Manager" -w Secret123 -b cn=config |grep nsslapd-sasl-max-buffer-size
nsslapd-sasl-max-buffer-size: 2097152

Since there is no easy test for this, I think we can check above from IPA install and also results from tests where I saw the errors before.

::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
:: [   LOG    ] :: irm_list_pos_0001: list, no name
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::

:: [  BEGIN   ] :: Running 'ipa-replica-manage -p Secret123 list > /tmp/test_irm_list_pos_0001.out 2>&1'
:: [   PASS   ] :: Command 'ipa-replica-manage -p Secret123 list > /tmp/test_irm_list_pos_0001.out 2>&1' (Expected 0, got 0)
:: [  BEGIN   ] :: Running 'cat /tmp/test_irm_list_pos_0001.out'
cloud-qe-1-vm-2.testrelm.test: master
beast.testrelm.test: master
spider.testrelm.test: master
ipaqavme.testrelm.test: master
cloud-qe-4.testrelm.test: master
:: [   PASS   ] :: Command 'cat /tmp/test_irm_list_pos_0001.out' (Expected 0, got 0)
:: [   PASS   ] :: File '/tmp/test_irm_list_pos_0001.out' should contain 'cloud-qe-4.testrelm.test' 
:: [   PASS   ] :: File '/tmp/test_irm_list_pos_0001.out' should contain 'cloud-qe-1-vm-2.testrelm.test' 
:: [   PASS   ] :: File '/tmp/test_irm_list_pos_0001.out' should contain 'spider.testrelm.test' 
:: [   PASS   ] :: File '/tmp/test_irm_list_pos_0001.out' should contain 'beast.testrelm.test' 
:: [   PASS   ] :: File '/tmp/test_irm_list_pos_0001.out' should contain 'ipaqavme.testrelm.test' 
:: [  BEGIN   ] :: Running 'remotehost-sync-set -s '1.irm_list_pos_0001.0' -m cloud-qe-4.idmqe.lab.eng.bos.redhat.com'
remotehost-sync-set -s 1.irm_list_pos_0001.0 -m cloud-qe-4.idmqe.lab.eng.bos.redhat.com

Comment 6 errata-xmlrpc 2015-03-05 09:32:47 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://rhn.redhat.com/errata/RHSA-2015-0416.html