[Date Prev][Date Next] [Chronological] [Thread] [Top]

RE: cannot restore db

To: "openldap-technical@openldap.org" <openldap-technical@openldap.org>
Subject: RE: cannot restore db
From: "Bidwell, Matt" <Matt.Bidwell@nrel.gov>
Date: Wed, 8 Jun 2011 17:07:55 -0600
Accept-language: en-US
Acceptlanguage: en-US
Content-language: en-US
In-reply-to: <F3F815C07462A840B98DAB83D0FE583533B7D3AA2A@MAILBOX1.nrel.gov>
References: <F3F815C07462A840B98DAB83D0FE583533B7D3AA2A@MAILBOX1.nrel.gov>
Thread-index: AcwlcPSivbf/LKWARSqE+yXPvo9YaQAv+Apg
Thread-topic: cannot restore db

Ignore, the issue seems to be something completely different. 

-----Original Message-----
From: openldap-technical-bounces@OpenLDAP.org [mailto:openldap-technical-bounces@OpenLDAP.org] On Behalf Of Bidwell, Matt
Sent: Tuesday, June 07, 2011 6:14 PM
To: openldap-technical@openldap.org
Subject: cannot restore db

I'm using both openldap-2.4.24 and db-5.1.25 from source.  I was experiencing
corrupted entries from the running database. I tried moving the openldap-data
folder, created a new one, and tried running  slapadd with the -f and -l 
flags with my conf file and backup ldif.  I get back an error that tells
me id2entry.bdb can't be opened because it is missing.  Isn't slapadd supposed 
to create id2entry.bdb?  The flags I used to configure BDB are --enable-cxx -C,
did I miss something?

Matt

References:
- cannot restore db
  - From: "Bidwell, Matt" <Matt.Bidwell@nrel.gov>

Prev by Date: Re: retrieving dn via proxy ldap
Next by Date: Scaling Syncrepl
Index(es):
- Chronological
- Thread