Bug 131550 - Update 3 OpenLDAP packages can't access data
Update 3 OpenLDAP packages can't access data
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: openldap (Show other bugs)
3.0
i386 Linux
medium Severity high
: ---
: ---
Assigned To: Nalin Dahyabhai
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2004-09-02 03:38 EDT by Dana Canfield
Modified: 2007-11-30 17:07 EST (History)
3 users (show)

See Also:
Fixed In Version: 2.0.27-17
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2004-09-02 19:31:30 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)

  None (edit)
Description Dana Canfield 2004-09-02 03:38:16 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7)
Gecko/20040808 Firefox/0.9.3

Description of problem:
Installed the openldap packages from QU3 tonight (it happened to be
our maintenance windows and I'd been waiting for the kernel updates,
so I jumped right in).

After installing those packages and restarting LDAP, none of the
existing data is available.  Slapadd and slapcat can't access the
databases, either.  The only clue I have is from my attempt at
rebuilding the database, which gave me this at debug level 1:
slapadd init: initiated tool.
slapadd startup: initiated.
backend_startup: starting database
=> ldbm_cache_open( "/var/lib/ldap/id2entry.gdbm", 18, 600 )
<= ldbm_cache_open (opened 0)
=> str2entry
<= str2entry(uindykey=B17Y5NXCA,ou=devices,dc=uindy,dc=edu) -> -1
(0x80f10c8)
oc_check_required entry
(uindykey=B17Y5NXCA,ou=devices,dc=uindy,dc=edu), objectClass "top"
oc_check_required entry
(uindykey=B17Y5NXCA,ou=devices,dc=uindy,dc=edu), objectClass "device"
oc_check_required entry
(uindykey=B17Y5NXCA,ou=devices,dc=uindy,dc=edu), objectClass
"ieee802Device"
oc_check_required entry
(uindykey=B17Y5NXCA,ou=devices,dc=uindy,dc=edu), objectClass
"printerDevice"
oc_check_allowed type "cn"
oc_check_allowed type "macAddress"
oc_check_allowed type "uIndyKey"
oc_check_allowed type "objectClass"
oc_check_allowed type "creatorsName"
oc_check_allowed type "createTimestamp"
oc_check_allowed type "modifiersName"
oc_check_allowed type "modifyTimestamp"
=> ldbm_cache_open( "/var/lib/ldap/nextid.gdbm", 18, 600 )
<= ldbm_cache_open (opened 1)
=> ldbm_tool_entry_put( 3,
"uindykey=B17Y5NXCA,ou=devices,dc=uindy,dc=edu" )
=> dn2id( "UINDYKEY=B17Y5NXCA,OU=DEVICES,DC=UINDY,DC=EDU" )
=> ldbm_cache_open( "/var/lib/ldap/dn2id.gdbm", 18, 600 )
<= ldbm_cache_open NULL "/var/lib/ldap/dn2id.gdbm" errno=11
reason="Resource temporarily unavailable")
<= dn2id could not open dn2id.gdbm
slapadd: could not add entry
dn="uindykey=B17Y5NXCA,ou=devices,dc=uindy,dc=edu" (line=13)
=> ldbm_cache_open( "/var/lib/ldap/nextid.gdbm", 34, 600 )
<= ldbm_cache_open (opened 1)
slapadd shutdown: initiated
ldbm backend syncing
ldbm flushing db (/var/lib/ldap/id2entry.gdbm)
ldbm closing db (/var/lib/ldap/id2entry.gdbm)
ldbm flushing db (/var/lib/ldap/nextid.gdbm)
ldbm closing db (/var/lib/ldap/nextid.gdbm)
ldbm backend done syncing
====> cache_release_all
slapadd shutdown: freeing system resources.

Rolling back to the version -11 restored my access to the data with no
further intervention.  This was reproduced on two separate boxes.

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

How reproducible:
Always

Steps to Reproduce:
1. Install 2.0.27-15 rpms
2. Attempt anything having to do with LDAP.

    

Actual Results:  Not search results, unable to access database for
adding or dumping data.

Expected Results:  Continued operation as in QU2.

Additional info:
Comment 1 Edward Muller 2004-09-02 15:05:27 EDT
Adding a me too.

I am using ldbm as my database type.
Comment 3 Jay Turner 2004-09-02 19:35:31 EDT
An errata has been issued which should help the problem 
described in this bug report. This report is therefore being 
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files, 
please follow the link below. You may reopen this bug report 
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2004-224.html

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