hello pascal,
thank you for your fast answer!
i've done this but at this time i got this message:
Sep 22 20:15:24 imap master: unable to change limit of file descriptors
available
Sep 22 20:15:24 imap master[3892]: process started
Sep 22 20:15:24 imap master[3893]: about to exec /usr/cyrus/bin/ctl_mboxlist
Sep 22 20:15:25 imap ctl_mboxlist[3893]: running mboxlist recovery
Sep 22 20:15:25 imap ctl_mboxlist[3893]: DBERROR db3: Invalid log file:
log.0000000001: No such file or direc
tory
Sep 22 20:15:25 imap ctl_mboxlist[3893]: DBERROR db3: PANIC: No such file or
directory
Sep 22 20:15:25 imap ctl_mboxlist[3893]: DBERROR: critical database
situation
Sep 22 20:15:25 imap master[3892]: process 3893 exited, status 75
Sep 22 20:15:25 imap master[3894]: about to exec /usr/cyrus/bin/ctl_deliver
Sep 22 20:15:25 imap master[3892]: unable to bind imap socket: Address
already in use
Sep 22 20:15:25 imap master[3892]: unable to bind imaps socket: Address
already in use
Sep 22 20:15:25 imap master[3892]: unable to bind pop3 socket: Address
already in use
Sep 22 20:15:25 imap master[3892]: unable to bind pop3s socket: Address
already in use
Sep 22 20:15:25 imap master[3892]: unable to bind sieve socket: Address
already in use
Sep 22 20:15:25 imap master[3892]: ready for work
Sep 22 20:15:25 imap master[3895]: about to exec /usr/cyrus/bin/ctl_mboxlist
Sep 22 20:15:25 imap ctl_mboxlist[3895]: checkpointing mboxlist
Sep 22 20:15:25 imap ctl_mboxlist[3895]: DBERROR db3: region error detected;
run recovery.
Sep 22 20:15:25 imap ctl_mboxlist[3895]: DBERROR: dbenv->open '/var/imap/db'
failed: DB_RUNRECOVERY: Fatal er
ror, run database recovery
Sep 22 20:15:25 imap master[3896]: about to exec /usr/cyrus/bin/ctl_deliver
Sep 22 20:15:25 imap ctl_deliver[3896]: duplicate_prune: pruning back 3 days
Sep 22 20:12:05 imap ctl_deliver[3849]: duplicate_prune:
/var/imap/deliverdb/del
iver-u.db: purged 0 out of 0 entries
Sep 22 20:12:05 imap ctl_deliver[3849]: duplicate_prune:
/var/imap/deliverdb/del
iver-v.db: purged 0 out of 0 entries
best regards...
Nette Gruesse,
Pascal Reinheimer
-----Ursprungliche Nachricht-----
Von: Pascal Gienger [mailto:[EMAIL PROTECTED]]
Gesendet: Samstag, 22. September 2001 18:17
An: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Betreff: Re: your DB3/Cyrus problems
>I got the following messages if i want start the /usr/cyrus/bin/master &
>process
[...]
>Sep 22 18:33:49 imap imapd[3665]: DBERROR db3: region error detected; run
>recovery.
>Sep 22 18:33:49 imap imapd[3665]: DBERROR: dbenv->open '/var/imap/db'
>failed: DB_RUNRECOVERY: Fatal error, run database recovery
That is clear, isn't it? ,-)
The underlying DB3 library is complaining about a corrupted .db-File (.db
is not in sync with the db/* journal and log files (*) ).
In your DB3 distribution there should be a program called "db_recover".
Backup /var/imap/db (the directory) and /var/imap/mailboxes.db.
Run:
db_recover -h /var/imap/db
That's it.
Start the master then and it will work.
Pascal
(*) DB3 does not only use the .db file but also a "db" subdirectory in your
database path. So Cyrus with DB3 compiled in will use:
/var/imap/mailboxes.db
/var/imap/db/db...-files and
/var/imap/db/log..-files.
--
