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

Re: DB log message (in replica server)

I forgot to tell you that the openldap server which is giving the problems is a replica server. And the way I initialized this was copying the databases from the master to the réplica. Is this the right way to perform the sincronization or should I use slapcat/slapadd commands on each server to do this?

Thanks for help

Jorge



Jorge Izquierdo escribió:
I have another OpenLDAP with the same versions running in other machine and it works fine. I think it could be a problem of the way and libraries used in building my OpenLDAP. I may try to recompile it, but it would be greatfull if somebody could tell me what this line on the logs mean: DB_ENV->log_flush: LSN past current end-of-log

What is the openldap trying to do when this message appears? Why this could be a problem with my openldap installation?

Thanks for your help

Jorge




Dustin Doris escribió:

Jorge,

I was getting the same errors previously running 2.1.22 with berkeley db
4 backend.  For us, our berkeley db started becoming corrupt every few
days.  We have about 200K users and have about 1k changes come through
every day.  We were having to run db_recover to fix.

I switched back to 2.0 w/ berkeley 3 and we are not having any problems.
If you find out what was causing it, please reply and let us know.  I'd
prefer to get back to the most up to date versions.  We are still in
testing stages right now, so it would be easy to go back.

Thanks
Dustin Doris

On Fri, 11 Jul 2003, Jorge Izquierdo wrote:


Hi everybody, I´m getting sometimes a message on the log of my openldap
server:

DB_ENV->log_flush: LSN past current end-of-log

It seems everything works fine but I don´t know what does it mean and if
it could lead to any problem in the future.

Thanks for help

Jorge