[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 12:43:48 -0600
Accept-language: en-US
Acceptlanguage: en-US
Content-language: en-US
In-reply-to: <20110608083321.184ec147@magenta.l4b.de>
References: <F3F815C07462A840B98DAB83D0FE583533B7D3AA2A@MAILBOX1.nrel.gov> <20110608083321.184ec147@magenta.l4b.de>
Thread-index: AcwlqI3TYtvJF3r7Tz6aK40sq21FBQAY2hsQ
Thread-topic: cannot restore db

I recompiled but that didn't seem to change things.

Matt

-----Original Message-----
From: openldap-technical-bounces@OpenLDAP.org [mailto:openldap-technical-bounces@OpenLDAP.org] On Behalf Of Dieter Kluenter
Sent: Wednesday, June 08, 2011 12:33 AM
To: openldap-technical@openldap.org
Subject: Re: cannot restore db

Am Tue, 7 Jun 2011 18:13:55 -0600
schrieb "Bidwell, Matt" <Matt.Bidwell@nrel.gov>:

> 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?

probably something like
--with-mutex=POSIX/pthreads/library

-Dieter

-- 
Dieter KlÃnter | Systemberatung
sip: 7770535@sipgate.de 
http://www.dpunkt.de/buecher/2104.html
GPG Key ID:8EF7B6C6

References:
- cannot restore db
  - From: "Bidwell, Matt" <Matt.Bidwell@nrel.gov>
- Re: cannot restore db
  - From: Dieter Kluenter <dieter@dkluenter.de>

Prev by Date: Migrating from RHDS to openldap
Next by Date: retrieving dn via proxy ldap
Index(es):
- Chronological
- Thread