https://bugzilla.redhat.com/show_bug.cgi?id=479931
Description of problem: On my production machine FDS is running in multimaster replication mode. But sometimes my service get stuck and in the logs i get the following error: [14/Jan/2009:10:55:27 +051800] - libdb: DB_ENV->log_flush: LSN of 5436/8995196 past current end-of-log of 5436/625098 [14/Jan/2009:10:55:27 +051800] - libdb: Database environment corrupt; the wrong log files may have been removed or incompatible database files imported from another environment [14/Jan/2009:10:55:27 +051800] - libdb: PANIC: DB_RUNRECOVERY: Fatal error, run database recovery [14/Jan/2009:10:55:27 +051800] - libdb: mihRoot/guid.db4: unable to flush page: 212875 [14/Jan/2009:10:55:27 +051800] - Serious Error---Failed to trickle, err=-30977 (DB_RUNRECOVERY: Fatal error, run database recovery) [14/Jan/2009:10:55:27 +051800] - libdb: PANIC: fatal region error detected; run recovery [14/Jan/2009:10:55:27 +051800] - Serious Error---Failed in deadlock detect (aborted at 0x0), err=-30977 (DB_RUNRECOVERY: Fatal error, run database recovery) [14/Jan/2009:10:55:27 +051800] - libdb: PANIC: fatal region error detected; run recovery [14/Jan/2009:10:55:27 +051800] - FATAL ERROR at idl_new.c (1); server stopping as database recovery needed. [14/Jan/2009:10:55:27 +051800] - libdb: PANIC: fatal region error detected; run recovery [14/Jan/2009:10:55:27 +051800] - FATAL ERROR at idl_new.c (1); server stopping as database recovery needed. [14/Jan/2009:10:55:27 +051800] - libdb: PANIC: fatal region error detected; run recovery [14/Jan/2009:10:55:27 +051800] - Serious Error---Failed in deadlock detect (aborted at 0x0), err=-30977 (DB_RUNRECOVERY: Fatal error, run database recovery) Fedora-Directory/1.1.3 B2008.269.157 NMLUDB01.edc.mihi.com:8888 (/etc/dirsrv/slapd-NMLUDB01) [14/Jan/2009:11:01:44 +051800] - Fedora-Directory/1.1.3 B2008.269.157 starting up Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1.N/A 2. 3. Actual results: Expected results: Additional info:
batch update to FUTURE milestone
Added initial screened field value.
Metadata Update from @nkinder: - Issue set to the milestone: N/A
389-ds-base is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in 389-ds-base's github repository.
This issue has been cloned to Github and is available here: - https://github.com/389ds/389-ds-base/issues/106
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Metadata Update from @spichugi: - Issue close_status updated to: wontfix (was: Invalid)
Login to comment on this ticket.