Multiple instaces of kolabquotawarn - kolabquotawarn not terminating

[Christian Rößler]

Mark Berndt schrieb:

>> after setting up a new Kolab in an equally new openSuse 10.3 for testing
>> I have noticed that kolabquotawarn will not terminate. So every 10
>> minutes a new kolabquotawarninstance pops up:
>> Any hints, please? Kolab version is 2.2.0, yesterday from
>> <http://ftp.gwdg.de/pub/linux/kolab/server/release/kolab-server-2.2.0/>.
> I have seen this due to a crashed openldap.
> I was running openpkg on debian and I got ldap error messages 
> in /var/log/messages.
> [...] Restarting the openpkg system resumed normal operation.

Thanks for the hints! Anyway, I have started everything multiple times, 
without change. Then I noticed in the imap logs:

Jan 16 10:28:36 kolab-test <warning> imap[21482]: DBERROR db4: 
/kolab/var/imapd/mailboxes.db: unexpected file type or format
Jan 16 10:28:36 kolab-test <error> imap[21482]: DBERROR: opening 
/kolab/var/imapd/mailboxes.db: Invalid argument
Jan 16 10:28:36 kolab-test <error> imap[21482]: DBERROR: opening 
/kolab/var/imapd/mailboxes.db: cyrusdb error
Jan 16 10:28:36 kolab-test <error> imap[21482]: Fatal error: can't read 
mailboxes file
Jan 16 10:28:36 kolab-test <debug> imap[21488]: executed

Jan 16 10:30:12 kolab-test <debug> imap[29974]: executed
Jan 16 10:30:12 kolab-test <warning> imap[29974]: DBERROR db4: 
/kolab/var/imapd/annotations.db: unexpected file type or format
Jan 16 10:30:12 kolab-test <error> imap[29974]: DBERROR: opening 
/kolab/var/imapd/annotations.db: Invalid argument
Jan 16 10:30:12 kolab-test <error> imap[29974]: DBERROR: opening 
/kolab/var/imapd/annotations.db: cyrusdb error
Jan 16 10:30:12 kolab-test <error> imap[29974]: Fatal error: can't read 
annotations file

...got a bit agitated, and deleted /kolab/var/imapd/mailboxes.db and 
/kolab/var/imapd/mailboxes.db - as it was a very fresh install; surely 
not good for a working one.

Then I killed the kolabquotawarn instances manually, and (as it seems) 
the problem's gone.

But in any case I wonder why these two files got corrupted - as it was a 
very fresh install.

Best regards, Christian