occasional libdb: DB_ENV->log_flush and Database environment corrupt and PANIC: DB_RUNRECOVERY

[389-ds-bot]

Cloned from Pagure issue: https://pagure.io/389-ds-base/issue/106

• Created at 2012-01-04 19:42:45 by mkosek
• Closed as Invalid
• Assigned to nobody
• Associated bugzillas
  • https://bugzilla.redhat.com/show_bug.cgi?id=479931

---

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:

[389-ds-bot]

Comment from rmeggins (@richm) at 2012-01-10 06:05:48

batch update to FUTURE milestone

[389-ds-bot]

Comment from nkinder (@nkinder) at 2012-08-28 04:14:29

Added initial screened field value.

[389-ds-bot]

Comment from nkinder (@nkinder) at 2017-02-11 23:04:42

Metadata Update from @nkinder:

• Issue set to the milestone: N/A