Open i-ivantsov opened 1 year ago
I'm experiencing exactly the same problem you described. I'm running 389ds 2.2 (docker) and it takes about 4 hours of continuous create/read queries (in testing purpose) to cause 389ds to crash. Here are some logs:
[03/May/2023:08:33:21.903178731 +0000] - NOTICE - bdb_start - Detected Disorderly Shutdown last time Directory Server was running, recovering database.
...
[03/May/2023:08:34:11.636988497 +0000] - ERR - libdb - Log sequence error: page LSN 162 8344656; previous LSN 162 8363470
[03/May/2023:08:34:11.638781278 +0000] - ERR - libdb - Recovery function for LSN 162 8363574 failed on forward pass
[03/May/2023:08:34:11.642935003 +0000] - ERR - libdb - PANIC: Invalid argument
[03/May/2023:08:34:11.746976604 +0000] - ERR - libdb - unable to join the environment
[03/May/2023:08:34:12.055180981 +0000] - CRIT - bdb_start - Database Recovery Process FAILED. The database is not recoverable. err=-30974: Unexpected dbimpl error code
[03/May/2023:08:34:12.060264341 +0000] - CRIT - bdb_start - Please make sure there is enough disk space for dbcache (1610612736 bytes) and db region files
[03/May/2023:08:34:12.063577179 +0000] - ERR - ldbm_back_start - Failed to init database, err=-30974 Unexpected dbimpl error code
Issue Description The ds389 service database is corrupted after a crash.
Package Version and Platform:
Steps to Reproduce Steps to reproduce the behavior:
CRIT - bdb_start - Database Recovery Process FAILED. The database is not recoverable. err=-30974: Unexpected dbimpl error code
Expected results Database recovered after service crush.
Additional context There is ds389 log: