Your message dated Thu, 25 Jun 2015 17:11:10 +0200
with message-id <[email protected]>
and subject line closing bugs reported against ancient dbX.Y versions
has caused the Debian Bug report #272674,
regarding db4.2-util: db4.2_recover only worked when -v specified
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
272674: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=272674
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: db4.2-util
Version: 4.2.52-17
Severity: normal
Hi.
Not sure this is what actually happened, but I cannot find another
explanation...
We've had a mangled LDAP database somehow after a power failure, leading
to messed-up db4.2 database.
I've used db4.2_recover without success :
/var/lib/ldap $ db4.2_recover
db_recover: DB_LOGC->get: log record LSN 1/188459: checksum mismatch
db_recover: DB_LOGC->get: catastrophic recovery may be required
db_recover: PANIC: DB_RUNRECOVERY: Fatal error, run database recovery
db_recover: PANIC: DB_RUNRECOVERY: Fatal error, run database recovery
db_recover: PANIC: fatal region error detected; run recovery
db_recover: PANIC: fatal region error detected; run recovery
db_recover: PANIC: fatal region error detected; run recovery
db_recover: PANIC: fatal region error detected; run recovery
db_recover: PANIC: fatal region error detected; run recovery
db_recover: PANIC: fatal region error detected; run recovery
db_recover: PANIC: fatal region error detected; run recovery
db_recover: PANIC: fatal region error detected; run recovery
db_recover: PANIC: fatal region error detected; run recovery
db_recover: PANIC: fatal region error detected; run recovery
db_recover: PANIC: fatal region error detected; run recovery
db_recover: PANIC: fatal region error detected; run recovery
db_recover: PANIC: fatal region error detected; run recovery
db_recover: PANIC: fatal region error detected; run recovery
db_recover: PANIC: fatal region error detected; run recovery
db_recover: PANIC: fatal region error detected; run recovery
db_recover: DB_ENV->open: DB_RUNRECOVERY: Fatal error, run database recovery
Nor did it work with the -c (catastrophic recovery) option :
still :
/var/lib/ldap$ db4.2_recover -c
db_recover: DB_LOGC->get: log record LSN 1/188459: checksum mismatch
db_recover: DB_LOGC->get: catastrophic recovery may be required
db_recover: PANIC: DB_RUNRECOVERY: Fatal error, run database recovery
db_recover: PANIC: DB_RUNRECOVERY: Fatal error, run database recovery
db_recover: PANIC: fatal region error detected; run recovery
db_recover: PANIC: fatal region error detected; run recovery
db_recover: PANIC: fatal region error detected; run recovery
db_recover: PANIC: fatal region error detected; run recovery
db_recover: PANIC: fatal region error detected; run recovery
db_recover: PANIC: fatal region error detected; run recovery
db_recover: PANIC: fatal region error detected; run recovery
db_recover: PANIC: fatal region error detected; run recovery
db_recover: PANIC: fatal region error detected; run recovery
db_recover: PANIC: fatal region error detected; run recovery
db_recover: PANIC: fatal region error detected; run recovery
db_recover: PANIC: fatal region error detected; run recovery
db_recover: PANIC: fatal region error detected; run recovery
db_recover: PANIC: fatal region error detected; run recovery
db_recover: PANIC: fatal region error detected; run recovery
db_recover: PANIC: fatal region error detected; run recovery
db_recover: DB_ENV->open: DB_RUNRECOVERY: Fatal error, run database recovery
Then as I was really pissed, I tried with a -v (verbose) option :
/var/lib/ldap$ db4.2_recover -v
db_recover: Finding last valid log LSN: file: 5 offset 826758
db_recover: Recovery starting from [5][826617]
db_recover: Recovery complete at Tue Sep 21 14:36:08 2004
db_recover: Maximum transaction ID 80000002 Recovery checkpoint
[5][826758]
And that actually repaired it !
Surprising, isn't it ?
Hope I didn't dream...
Regards,
-- System Information:
Debian Release: 3.1
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.4.27-200409151
Locale: LANG=C, LC_CTYPE=C
Versions of packages db4.2-util depends on:
ii libc6 2.3.2.ds1-16 GNU C Library: Shared libraries an
ii libdb4.2 4.2.52-17 Berkeley v4.2 Database Libraries [
-- no debconf information
--- End Message ---
--- Begin Message ---
This bug has been reported against an ancient version of dbX.Y (4.x,
5.0), that was removed from Debian so long ago that it is no longer part
of any supported release (including oldoldstable-lts).
It is assumed to be fixed (or no longer relevant) in newer releases and
therefore I'm closing this report now. If the problem is still
reproducible in the current version (db5.3), feel free to provide more
information, reopen and reassign this bug report.
Andreas
--- End Message ---
