I have been holding back updating to cyrus 2.2.13 but this afternoon I went ahead and made the major update and really tried to follow ALL the points and rules in updating but I really think I messed up the whole system now. I really hope I have not hosed all the email today and have to go back to an older backup :(.
<br><br>I really do need some help for I am so lost and I think everything I have been trying has made it to worse and back again. <br><br>Here is the output from syslog.<br><br>Jul 26 22:37:27 jurassic cyrus/master[10684]: process started
<br>Jul 26 22:37:31 jurassic cyrus/master[10708]: about to exec /usr/sbin/ctl_cyrusdb<br>Jul 26 22:37:32 jurassic cyrus/ctl_cyrusdb[10708]: DBERROR db4: Skipping log file /var/lib/cyrus/db/log.00000000<br>55: historic log version 3
<br>Jul 26 22:37:33 jurassic cyrus/ctl_cyrusdb[10708]: recovering cyrus databases<br>Jul 26 22:37:33 jurassic cyrus/ctl_cyrusdb[10708]: skiplist: recovered /var/lib/cyrus/mailboxes.db (563 records,<br> 84908 bytes) in 0 seconds
<br>Jul 26 22:37:33 jurassic cyrus/ctl_cyrusdb[10708]: skiplist: recovered /var/lib/cyrus/annotations.db (0 records,<br> 144 bytes) in 0 seconds<br>Jul 26 22:37:33 jurassic cyrus/ctl_cyrusdb[10708]: DBERROR db4: /var/lib/cyrus/db/log.0000000056: log file open
<br>failed: No such file or directory<br>Jul 26 22:37:33 jurassic cyrus/ctl_cyrusdb[10708]: DBERROR db4: PANIC: No such file or directory<br>Jul 26 22:37:33 jurassic cyrus/ctl_cyrusdb[10708]: DBERROR: critical database situation
<br>Jul 26 22:37:34 jurassic cyrus/master[10684]: process 10708 exited, status 75 <br>Jul 26 22:37:34 jurassic cyrus/master[10754]: about to exec /usr/sbin/cyr_expire<br>Jul 26 22:37:34 jurassic cyrus/cyr_expire[10754]: DBERROR db4: PANIC: fatal region error detected; run recovery
<br>Jul 26 22:37:34 jurassic cyrus/cyr_expire[10754]: DBERROR: critical database situation<br>Jul 26 22:37:34 jurassic cyrus/master[10684]: process 10754 exited, status 75 <br>Jul 26 22:37:34 jurassic cyrus/master[10755]: about to exec /usr/sbin/tls_prune
<br>Jul 26 22:37:34 jurassic cyrus/tls_prune[10755]: DBERROR db4: PANIC: fatal region error detected; run recovery<br>Jul 26 22:37:34 jurassic cyrus/tls_prune[10755]: DBERROR: critical database situation<br>Jul 26 22:37:34 jurassic cyrus/master[10684]: process 10755 exited, status 75
<br>Jul 26 22:37:34 jurassic cyrus/master[10684]: ready for work<br>Jul 26 22:37:34 jurassic cyrus/master[10766]: about to exec /usr/sbin/ctl_cyrusdb<br>Jul 26 22:37:34 jurassic cyrus/master[10767]: about to exec /usr/lib/cyrus/bin/notifyd
<br>Jul 26 22:37:34 jurassic cyrus/ctl_cyrusdb[10766]: DBERROR db4: PANIC: fatal region error detected; run recovery<br>Jul 26 22:37:34 jurassic cyrus/ctl_cyrusdb[10766]: DBERROR: critical database situation<br>Jul 26 22:37:34 jurassic cyrus/master[10684]: process 10766 exited, status 75
<br><br><br><br>No mater what I do I just can not get passed this error. I have tried...reconstructing, db4.3_recover, bringing in a backup db and each one just does not clear the air. Every time I try the error still persists. Is this recoverable? Everything I have read on how to fix it does not work. I am wondering if i really missed something here. I really do hope to get some feed back ASAP because I want to get this fixed within the next 7 hrs.
<br><br>-Adam<br>