Re: Kolab 2.0.4 upgrade to 2.1 fails due to DBERROR

On Thursday 09 August 2007 12:25:23 Bernhard Reiter wrote:
> Which database in particular is the error message
about?

I'm not sure.
All I know is I get this error repetitively in
/kolab/var/imapd/log/pop3d.log
Aug 06 08:00:32 tmgmen-bbb <warning> pop3s[17873]:
DBERROR db4: PANIC: fatal 
region error detected; run recovery
Aug 06 08:00:32 tmgmen-bbb <critical> pop3s[17873]:
DBERROR: critical database 
situation
Aug 06 08:00:32 tmgmen-bbb <warning> pop3[17882]:
DBERROR db4: PANIC: fatal 
region error detected; run recovery
Aug 06 08:00:32 tmgmen-bbb <critical> pop3[17882]:
DBERROR: critical database 
situation
Aug 06 08:00:32 tmgmen-bbb <warning> pop3s[17902]:
DBERROR db4: PANIC: fatal 
region error detected; run recovery
Aug 06 08:00:32 tmgmen-bbb <critical> pop3s[17902]:
DBERROR: critical database 
situation
Aug 06 08:00:32 tmgmen-bbb <warning> pop3s[17907]:
DBERROR db4: PANIC: fatal 
region error detected; run recovery
Aug 06 08:00:32 tmgmen-bbb <critical> pop3s[17907]:
DBERROR: critical database 
situation
Aug 06 08:00:32 tmgmen-bbb <warning> pop3s[17913]:
DBERROR db4: PANIC: fatal 
region error detected; run recovery
Aug 06 08:00:32 tmgmen-bbb <critical> pop3s[17913]:
DBERROR: critical database 
situation
Aug 06 08:00:32 tmgmen-bbb <warning> pop3[17906]:
DBERROR db4: PANIC: fatal 
region error detected; run recovery
Aug 06 08:00:32 tmgmen-bbb <critical> pop3[17906]:
DBERROR: critical database 
situation

roottmgmen-bbb:/home/kolab2fail/kolab/var/imapd# file
*.db
annotations.db:  Cyrus skiplist DB
deliver.db:      Berkeley DB (Btree, version 9, native
byte-order)
mailboxes.db:    Cyrus skiplist DB
tls_sessions.db: Berkeley DB (Btree, version 9, native
byte-order)

-- 
Divan Santana

Skype:                  DivanSantana
Gtalk/MSN:              Divan.SantanaGMail.com


Love God, Love People, Love Life!

_______________________________________________
Kolab-users mailing list
Kolab-userskolab.org
https:
//kolab.org/mailman/listinfo/kolab-users