Problems with imap

Jochen May admin at jmay.org
Sun Jan 17 00:37:02 CET 2010


Hi,

after a while i get problems with my imap server.

This are the sieve.log:
Jan 16 23:13:15 kolab <warning> sieve[6553]: DBERROR db4: file 
/kolab/var/imapd/tls_sessions.db has LSN 1/6318827, past end of log at 
1/3707608
Jan 16 23:13:15 kolab <warning> sieve[6553]: DBERROR db4: Commonly caused by 
moving a database from one transactional database
Jan 16 23:13:15 kolab <warning> sieve[6553]: DBERROR db4: environment to 
another without clearing the database LSNs, or removing
Jan 16 23:13:15 kolab <warning> sieve[6553]: DBERROR db4: all of the log files 
from a database environment
Jan 16 23:13:15 kolab <warning> sieve[6553]: DBERROR db4: 
/kolab/var/imapd/tls_sessions.db: unexpected file type or format

Simulary error, but a different file -> imapd.log:
Jan 16 23:44:08 kolab <debug> imap[11099]: mystore: starting txn 2147483689
Jan 16 23:44:08 kolab <warning> imap[11099]: DBERROR db4: file 
/kolab/var/imapd/annotations.db has LSN 1/6387392, past end of log
 at 1/3723252
Jan 16 23:44:08 kolab <warning> imap[11099]: DBERROR db4: Commonly caused by 
moving a database from one transactional database
Jan 16 23:44:08 kolab <warning> imap[11099]: DBERROR db4: environment to 
another without clearing the database LSNs, or removing
Jan 16 23:44:08 kolab <warning> imap[11099]: DBERROR db4: all of the log files 
from a database environment
Jan 16 23:44:08 kolab <debug> imap[11099]: abort_txn: aborting txn 2147483689

And again, quite the same - ctl_cyrusdb.log:
Jan 17 00:00:26 kolab <notice> ctl_cyrusdb[16070]: done checkpointing cyrus 
databases
Jan 17 00:30:24 kolab <notice> ctl_cyrusdb[18266]: checkpointing cyrus 
databases
Jan 17 00:30:24 kolab <warning> ctl_cyrusdb[18266]: DBERROR db4: DB_ENV-
>log_flush: LSN of 1/6387392 past current end-of-log of 1/3728860
Jan 17 00:30:24 kolab <warning> ctl_cyrusdb[18266]: DBERROR db4: Database 
environment corrupt; the wrong log files may have been removed or incompatible 
database files imported from another environment
Jan 17 00:30:24 kolab <warning> ctl_cyrusdb[18266]: DBERROR db4: PANIC: 
DB_RUNRECOVERY: Fatal error, run database recovery
Jan 17 00:30:24 kolab <critical> ctl_cyrusdb[18266]: DBERROR: critical 
database situation
Jan 17 00:31:38 kolab <notice> ctl_cyrusdb[23357]: recovering cyrus databases

When i run ctl_mboxlist -r everything looks ok for a while. But the error come 
back.

I try to recover my mailbox.db with /kolab/bin/ctl_mboxlist -d > 
mailboxlist.txt and delete the db directory without effect. Also i delete the 
tls_session.db - without effect. 
Anybody a idea how i can fix this?

Kolab is running in version 2.2.2 on debian 5.0 in a xen domU

Regards,
Jochen May




More information about the users mailing list