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

Re: Log sequence error on db_recover

Hi Tony,
    Thanks for you reply.

Try mv'ing the log to an invalid name and running 'db_recover -c' again. 

db_recover runs without errors. But bdb files don't get generated.

[openldap-data]# db_recover -c -v
db_recover: Finding last valid log LSN: file: 4 offset 159583
db_recover: Recovery starting from [2][28]
db_recover: Recovery complete at Sat Jan 24 07:55:07 2004
db_recover: Maximum transaction ID 8000016e Recovery checkpoint [4][159583]
db_recover: Recovery complete at Sat Jan 24 07:55:07 2004
db_recover: Maximum transaction id 80000000 Recovery checkpoint [4][159583]
[openldap-data]# echo $?
0
[openldap-data]# ls
log.0000000002  log.0000000003  log.0000000004

What seems to be the problem? Are there any fixes in 4.1.25 towards the problem that I see?

thanks
manoj


fre, 06.02.2004 kl. 04.24 skrev Manoj Lal:

>      I am having trouble recovering the slapd database after an abrupt
> system crash (system power loss). Running db_recover in catastrophic
> mode results in errors of the following form although db_recover
> returns 0:
> db_recover: Log sequence error: page LSN 1 343516; previous LSN 1 448705
>
>
> Another db_verify after this fails again. Understandably, I am able to
> start slapd but unable to access it. I am wondering if there is a way
> to recover from this scenario. Is this log file corrupted?
> Transcript attached. I am using Berkeley DB ver 4.1.24. On red-hat

Try mv'ing the log to an invalid name and running 'db_recover -c' again.
Try to update your BDB version to 4.1.25. RH should have an updated
version; this machine (RH RHEL3) runs 4.1.25 as standard.


_________________________________________________________________
Check out the great features of the new MSN 9 Dial-up, with the MSN Dial-up Accelerator. http://click.atdmt.com/AVE/go/onm00200361ave/direct/01/