[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
Re: OpenLDAP v2.2.24 Berkley fatal region error detected
Ok, maybe this was a stupid user error.
I shut ldap down, did a db_verify -o and found no problems and started
it back up and it worked again.
When I initially set this up I meant to set the Berkeley DB up with a 1G
256M cache area, unfortunately I set it up with 1G 256K cache, would
that possibly be the cause of this and the slapcat hang I saw the other day?
I now have it set up with a 1G 256M cache but it would put my mind at
ease if this would explain those anomalies.
Curt Blank wrote:
I just got the errors below out of the blue. Tried to do a ldapsearch
and got a Unknown error/Internal error so I looked in the log file. I
loaded the LDIF data in two days ago from scratch, fresh load, no
activity on this server i.e. not in production, nothing accessing it,
nothing updating it, it was staged to go into production tonight but
probably not now.
Mirrorset where the db resides is optimal and does not/did not have
any problems/events.
Nothing in the log file other then what is below. Need to be pointed
in a direction please. This does not give me a good feeling...
Apr 22 10:14:34 xxxxxx slapd[5547]: bdb(o=uwm.edu): PANIC: fatal
region error detected; run recovery
Apr 22 10:14:34 xxxxxx last message repeated 3 times
Apr 22 10:15:48 xxxxxx slapd[5547]: bdb(o=uwm.edu): PANIC: fatal
region error detected; run recovery
Apr 22 10:15:48 xxxxxx last message repeated 3 times
Apr 22 10:16:28 xxxxxx slapd[5547]: conn=2 op=0 ENTRY dn=""
Apr 22 10:17:20 xxxxxx slapd[5547]: bdb(o=uwm.edu): PANIC: fatal
region error detected; run recovery
Apr 22 10:17:20 xxxxxx last message repeated 3 times
Apr 22 12:19:14 xxxxxx slapd[5547]: bdb(o=uwm.edu): PANIC: fatal
region error detected; run recovery
Apr 22 12:19:23 xxxxxx last message repeated 19 times
Apr 22 12:19:37 xxxxxx slapd[5547]: bdb(o=uwm.edu): PANIC: fatal
region error detected; run recovery
Apr 22 12:19:37 xxxxxx last message repeated 3 times