Kolab 2.0.4 upgrade to 2.1 fails due to DBERROR

[Bernhard Reiter]

On Monday 13 August 2007 09:16, Divan Santana wrote:
> 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
>
> root at tmgmen-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)

Maybe there is another point in the configuration for the recovery
which runs from time to time. Hmm.

-- 
Managing Director - Owner: www.intevation.net       (Free Software Company)
Germany Coordinator: fsfeurope.org. Coordinator: www.Kolab-Konsortium.com.
Intevation GmbH, Osnabrück, DE; Amtsgericht Osnabrück, HRB 18998
Geschäftsführer Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://lists.kolab.org/pipermail/users/attachments/20070815/3d38cb96/attachment.sig>