Bug 57981 - Large LDAP transactions fail using ldbm backend
Large LDAP transactions fail using ldbm backend
Status: CLOSED NOTABUG
Product: Red Hat Linux
Classification: Retired
Component: openldap (Show other bugs)
7.1
i686 Linux
medium Severity medium
: ---
: ---
Assigned To: Nalin Dahyabhai
Aaron Brown
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2002-01-04 07:28 EST by John Dalbec
Modified: 2007-04-18 12:38 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2002-01-06 08:29:47 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description John Dalbec 2002-01-04 07:28:52 EST
From Bugzilla Helper:
User-Agent: Mozilla/4.79 [en] (Windows NT 5.0; U)

Description of problem:
Using the OpenLDAP ldbm backend (which appears to use gdbm), adding more than about 3400 members to an LDAP groupOfNames 
in 
a single transaction fails with an I/O error.

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. Install RH 7.1
2. (Optional) Rebuild/install RawHide OpenLDAP-2.0.19-1 package in 7.1
3. Define an LDAP groupOfNames object
4. Add 3500 members to the groupOfNames object in one ldapmodify transaction
	

Actual Results:  modifying entry <insert DN here>
ldap_modify: Can't contact LDAP server

ldif_record() = 81

Expected Results:  no error messages

Additional info:

Supposedly Berkeley DB 3.3.11 doesn't have this problem.
Comment 1 Trond Eivind Glomsrxd 2002-01-06 08:29:42 EST
Refiling against openldap.
Comment 2 John Dalbec 2002-01-17 15:35:01 EST
self->rtfm(sockbuf_max_incoming, sockbuf_max_incoming_auth);
self->slap(self.forehead);

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