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.
On Fri, 11 Jul 2003, Jorge Izquierdo wrote:
Hi everybody, I´m getting sometimes a message on the log of my openldap
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