Re: Apparent database corruption causing bus errors

[matthew sporleder <msporleder@gmail.com>]

db_recover is a tool that usually comes with a bdb install, try a find
/path/to/fink/install/root -name "db_recover*" and, obviously, replace
/path/to/.. with the correct into.  (/fink/?)

On 2/2/06, Chuck Meyer <chuck@popes.com> wrote:
>
> Sorry, like I said I'm very new to this so I'm not certain what info is
> pertinent.
>
> From slapd.conf:
>
> $OpenLDAP: pkg/ldap/servers/slapd/slapd.conf,v 1.23.2.8
> ...
> database        bdb
>
> This is my first installation, so everything is more or less set to
> defaults.
>
> Also, doing a quick "locate" I don't seem to have recover_db installed. Is
> it something I can install after the fact or is this related to my
> database type/OpenLDAP version?
>
> Thanks for your help!
>
> Chuck
>
>
> On Thu, 2 Feb 2006, matthew sporleder wrote:
>
> > You left out a lot of key information like the version of openldap,
> > and the backend you're using.  Assuming you're using back-bdb, you
> > might want to try the fink-installed db_recover.
> >
> > On 2/2/06, Chuck Meyer <chuck@popes.com> wrote:
> >> Hey folks,
> >>
> >> I've been using openLDAP casually on my Mac OS 10.3 system for about 6
> >> months now (via fink installation).
> >>
> >> I had a power outage recently and now my LDAP crashes on search
> >> consistently with a bus error.
> >>
> >> I attempted to do a slapcat to extract the data and (after exporting
> >> several entries)  I see the following:
> >>
> >> entry_decode: "8Z"
> >> <= entry_decode(8Z)
> >> # id=0000007f
> >> Bus error
> >>
> >> Since there's no way "8Z" is a valid record, I'm assuming my database has
> >> been corrupted.  Is there any way to recover the data beyond this record
> >> or to repair the database?
> >>
> >> So far my searches are making me believe I'm going to have to export the
> >> data I can, recreate the database and re-add all missing records.  I'm
> >> hoping there may be an easier solution?
> >>
> >> Thanks for your time!
> >>
> >> Chuck Meyer
> >> chuck@popes.com
> >>
> >
>