ctl_cyrusdb - DBERROR db4
Torsten Bunde
tb at sim.uni-hannover.de
Thu Jan 17 10:20:44 EST 2008
Hi @all,
I've got a question about Cyrus where I didn't even find a solution with
google, etc. until now.
We are using a Cyrus server here that causes some problems sometimes and
we don't know why. We are able to repair this but we would like to know
why this happens.
We are using
- SUSE Linux Enterprise Server 9
- Cyrus 2.2.3
The first problem is, that there are sometimes database errors because
of wrong user rights. After a rotation the user cyrus is not allowed to
write in same files because they are owned by root. But this is not the
main problem.
Today in the morning the server logfiles had the following messages
Jan 17 06:00:01 zeus ctl_cyrusdb[5101]: DBERROR db4: Log sequence error:
page LSN 7 1172797; previous LSN 17 2099307
Jan 17 06:00:01 zeus ctl_cyrusdb[5101]: DBERROR db4: Recovery function
for LSN 7 1148884 failed on forward pass
Jan 17 06:00:01 zeus ctl_cyrusdb[5101]: DBERROR db4: PANIC: Invalid argument
Jan 17 06:00:01 zeus ctl_cyrusdb[5101]: DBERROR: critical database situation
Jan 17 06:00:01 zeus idled[5102]: DBERROR db4: PANIC: fatal region error
detected; run recovery
Jan 17 06:00:01 zeus idled[5102]: DBERROR: critical database situation
Jan 17 06:00:02 zeus ctl_cyrusdb[5104]: DBERROR db4: PANIC: fatal region
error detected; run recovery
Jan 17 06:00:02 zeus ctl_cyrusdb[5104]: DBERROR: critical database situation
Jan 17 06:00:04 zeus lmtpunix[5119]: DBERROR db4: PANIC: fatal region
error detected; run recovery
Jan 17 06:00:04 zeus lmtpunix[5119]: DBERROR: critical database situation
[...]
Does anyone has any idea what happened here?
Thanks
- Torsten Bunde
More information about the Info-cyrus
mailing list