Hi,
I am running a slapd 2.2.23 (debian package) with a bdb Backend on a Debian Sarge system. I want to use slapcat for backing up my database, but it does never dump the complete data. After running a while it just stops and is doing nothing anymore. I am a bit nervous right now, is there another way to get a ldif dump, or some way of debugging to find the error ? I did try slapcat -d 256, but that did not show anything unnormal, it just stopped.
Thank you,
Marcella
On Wed, Feb 14, 2007 at 09:04:29AM +0100, Voigtlaender@hansenet.com wrote:
I am running a slapd 2.2.23 (debian package) with a bdb Backend on a Debian Sarge system. I want to use slapcat for backing up my database, but it does never dump the complete data. After running a while it just stops and is doing nothing anymore. I am a bit nervous right now, is there another way to get a ldif dump, or some way of debugging to find the error ? I did try slapcat -d 256, but that did not show anything unnormal, it just stopped.
Sounds like a corrupted database. You should try to recover it (db-recover, or db_recover, or db4.2_recover, etc).
There's a chance your bdb might be corrupt. Stop slapd, run db_recover, and try the slapcat again (with slapd still stopped). Assuming you can get a decent slapcat out of that, the next step would be use it to upgrade to 2.3.33. I believe that 2.2.23 isn't safe to slapcat hot, so you won't be able to accomplish your backup goal without the upgrade.
On Wed, 14 Feb 2007, Voigtlaender@hansenet.com wrote:
Hi,
I am running a slapd 2.2.23 (debian package) with a bdb Backend on a Debian Sarge system. I want to use slapcat for backing up my database, but it does never dump the complete data. After running a while it just stops and is doing nothing anymore. I am a bit nervous right now, is there another way to get a ldif dump, or some way of debugging to find the error ? I did try slapcat -d 256, but that did not show anything unnormal, it just stopped.
Thank you,
Marcella
It seems you are right. I did try db_recover, after that slapcat runs, but the data is not complete. Furthermore my slapd doesn't start anymore after the recover. Is there anything else I could try to get my data ?
Marcella
-----Ursprüngliche Nachricht----- Von: Aaron Richton [mailto:richton@nbcs.rutgers.edu] Gesendet: Mittwoch, 14. Februar 2007 14:34 An: Voigtländer, Marcella HTK Cc: openldap-software@openldap.org Betreff: Re: slapcat hangs without error message
There's a chance your bdb might be corrupt. Stop slapd, run db_recover, and try the slapcat again (with slapd still stopped). Assuming you can get a decent slapcat out of that, the next step would be use it to upgrade to 2.3.33. I believe that 2.2.23 isn't safe to slapcat hot, so you won't be able to accomplish your backup goal without the upgrade.
On Wed, 14 Feb 2007, Voigtlaender@hansenet.com wrote:
Hi,
I am running a slapd 2.2.23 (debian package) with a bdb Backend on a Debian Sarge system. I want to use slapcat for backing up
my database,
but it does never dump the complete data. After running a
while it just
stops and is doing nothing anymore. I am a bit nervous
right now, is
there another way to get a ldif dump, or some way of
debugging to find
the error ? I did try slapcat -d 256, but that did not show
anything
unnormal, it just stopped.
Thank you,
Marcella
If you have enough log files lying around, you could try the catastrophic recovery mode of db_recover. But that's a long shot, to put it nicely.
On Wed, 14 Feb 2007, Voigtlaender@hansenet.com wrote:
It seems you are right. I did try db_recover, after that slapcat runs, but the data is not complete. Furthermore my slapd doesn't start anymore after the recover. Is there anything else I could try to get my data ?
Marcella
On Wed, 14 Feb 2007, Voigtlaender@hansenet.com wrote:
It seems you are right. I did try db_recover, after that slapcat runs, but the data is not complete. Furthermore my slapd doesn't start anymore after the recover. Is there anything else I could try to get my data ?
What error messages do you get when starting slapd with debugging enabled?
Marcella
.
It seems you are right. I did try db_recover, after that slapcat runs, but the data is not complete. Furthermore my slapd doesn't start anymore after the recover. Is there anything else I could
try to get
my data ?
What error messages do you get when starting slapd with debugging enabled?
This ist the error message I get:
Feb 14 09:36:31 ldap slapd[732]: bdb_db_init: Initializing BDB database Feb 14 09:36:31 ldap slapd[733]: bdb(): PANIC: fatal region error detected; run recovery Feb 14 09:36:31 ldap slapd[733]: bdb_db_open: dbenv_open failed: DB_RUNRECOVERY: Fatal error, run database recovery (-3 0978) Feb 14 09:36:31 ldap slapd[733]: backend_startup: bi_db_open failed! (-30978) Feb 14 09:36:31 ldap slapd[733]: bdb(): DB_ENV->lock_id_free interface requires an environment configured for the locki ng subsystem Feb 14 09:36:31 ldap slapd[733]: bdb(): txn_checkpoint interface requires an environment configured for the transaction subsystem Feb 14 09:36:31 ldap slapd[733]: bdb_db_destroy: txn_checkpoint failed: Invalid argument (22) Feb 14 09:36:31 ldap slapd[733]: slapd stopped. Feb 14 09:36:31 ldap slapd[733]: connections_destroy: nothing to destroy
openldap-software@openldap.org
-
Aaron Richton -
Andreas Hasenack -
Howard Chu -
Voigtlaender＠hansenet.com