version 5 requires a version upgrade
Hello, I'am a new member at this mailing list. I've installed the cyrus-sasl 1.5.24 and the cyrus-imapd 2.0.16, tcl, makedepend and all the other things which mentioned in the documentation. When i start the cyradm it doesn't works and always threw me out after the password prompt. the /var/log/messages shows the following messages: SION: Database requires a version upgrade Sep 5 01:13:58 imap ctl_deliver[32664]: DBERROR dup: /var/imap/deliverdb/deliver-r.db: hash version 5 requires a version upgrade A client doesn't can connect to the server. It would be great if anyone have an solution for this problem... best regards, Pascal Reinheimer
version 5 requires a version upgrade
Hello, Now i've updated the Berkley Database and the /var/log/messages file shows the following message on each connect from a client to the server. The Client got a message that the server connection was early broken. Sep 9 03:48:01 imap imap: could not getenv(CYRUS_SERVICE); exiting Nette Gruesse, Pascal
imtest on localhost failed (prot layer failure)
Hello, I've installed the cyrus-sasl 1.5.24 and the cyrus-imapd 2.0.16, tcl, makedepend and all the other things which mentioned in the documentation. When i start the imtest program, the following message arrives on the screen: imtest -p imap localhost C: C01 CAPABILITY failure: prot layer failure What could i do to solve these Problem ? If i start the cyradm tool on the localhost i only get an password prompt and after this nothing because the tool exits and bring me back to the system prompt. In the /var/log/messages file the following messages arrives: Sep 15 02:58:54 imap imap: could not getenv(CYRUS_SERVICE); exiting Sep 15 02:58:57 imap imap: could not getenv(CYRUS_SERVICE); exiting Sep 15 02:59:43 imap sshd[1762]: log: Could not reverse map address 192.168.0.101. Sep 15 02:59:45 imap sshd[1762]: fatal: Read from socket failed: Connection reset by peer Sep 15 03:01:59 imap imap: could not getenv(CYRUS_SERVICE); exiting in the /var/adm/imap.log no new messages... best regards ... in hope to find anyone who can tell me how to solve these difficult problem. Nette Gruesse, Pascal Reinheimer
AW: imtest on localhost failed (prot layer failure)
Hello,
Now i've done this 4 points which you gave to me.
The master process are running, but in the /var/log/messages file the
following lines comes in:
rdb/deliver-u.db: DB_OLDVERSION: Database requires a version upgrade
Sep 16 16:15:03 imap ctl_deliver[487]: DBERROR dup:
/var/imap/deliverdb/deliver-
v.db: hash version 5 requires a version upgrade
Sep 16 16:15:03 imap ctl_deliver[487]: duplicate_prune: opening
/var/imap/delive
Sep 16 16:15:04 imap ctl_deliver[487]: DBERROR dup:
/var/imap/deliverdb/deliver-
y.db: hash version 5 requires a version upgrade
Sep 16 16:15:04 imap ctl_deliver[487]: duplicate_prune: opening
/var/imap/delive
rdb/deliver-y.db: DB_OLDVERSION: Database requires a version upgrade
Sep 16 16:15:04 imap ctl_deliver[487]: DBERROR dup:
/var/imap/deliverdb/deliver-
z.db: hash version 5 requires a version upgrade
Sep 16 16:15:04 imap ctl_deliver[487]: duplicate_prune: opening
/var/imap/delive
rdb/deliver-z.db: DB_OLDVERSION: Database requires a version upgrade
Sep 16 16:15:04 imap master[474]: process 487 exited, status 0
Sep 16 16:15:04 imap master[501]: about to exec /usr/cyrus/bin/imapd
Sep 16 16:15:05 imap service-imap[501]: executed
Sep 16 16:15:06 imap imapd[501]: DBERROR db3: region error detected; run
recovery.
Sep 16 16:15:06 imap imapd[501]: DBERROR: dbenv->open '/var/imap/db' failed:
DB_
RUNRECOVERY: Fatal error, run database recovery
if i run "imtest -p imap localhost" i got this:
C: C01 CAPABILITY
"telnet localhost 143" shows this:
Trying ::1...
telnet: connect to address ::1: Connection refused
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
I hope you have an solution for these things, the Berkley Database are:
/usr/local/BerkeleyDB.3.0/
best regards...
Nette Gruesse,
Pascal
-Ursprungliche Nachricht-
Von: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]Im Auftrag von Tarjei Huse
Gesendet: Sonntag, 16. September 2001 12:44
An: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Betreff: Re: imtest on localhost failed (prot layer failure)
Hi, have you:
a) remove all references to cyrus from ined.conf.
b) started cyrus as a independant daemon ('/usr/cyrus/bin/master &' I think)
c) What is your setup in regard of os and authentication info.
d) Have you read through the cyrus faq? (cyrus-utils.sf.net/faq)
tarjei
Pascal Reinheimer wrote:
> Hello,
>
> I've installed the cyrus-sasl 1.5.24 and the cyrus-imapd 2.0.16, tcl,
> makedepend and all the other things which mentioned in the documentation.
> When i start the imtest program, the following message arrives on the
> screen:
>
>
> imtest -p imap localhost
> C: C01 CAPABILITY
> failure: prot layer failure
>
> What could i do to solve these Problem ?
>
> If i start the cyradm tool on the localhost i only get an password prompt
> and after this nothing because the tool exits and bring me back to the
> system prompt.
>
> In the /var/log/messages file the following messages arrives:
>
> Sep 15 02:58:54 imap imap: could not getenv(CYRUS_SERVICE); exiting
> Sep 15 02:58:57 imap imap: could not getenv(CYRUS_SERVICE); exiting
> Sep 15 02:59:43 imap sshd[1762]: log: Could not reverse map address
> 192.168.0.101.
> Sep 15 02:59:45 imap sshd[1762]: fatal: Read from socket failed:
Connection
> reset by peer
> Sep 15 03:01:59 imap imap: could not getenv(CYRUS_SERVICE); exiting
>
>
> in the /var/adm/imap.log no new messages...
>
>
> best regards ... in hope to find anyone who can tell me how to solve these
> difficult problem.
>
>
>
> Nette Gruesse,
> Pascal Reinheimer
>
>
>
>
>
AW: imtest on localhost failed (prot layer failure)
hello, i've installed the newest berkley database, but if i start the /usr/cyrus/bin/master & process, the following messages arrives at the message file: Sep 18 21:31:14 imap ctl_deliver[1019]: duplicate_prune: opening /var/imap/deliverdb/deliver-x.db: DB_OLDVERSION: Database requires a version upgrade Sep 18 21:31:14 imap ctl_deliver[1019]: DBERROR dup: /var/imap/deliverdb/deliver-y.db: hash version 5 requires a version upgrade Sep 18 21:31:14 imap ctl_deliver[1019]: duplicate_prune: opening /var/imap/deliverdb/deliver-y.db: DB_OLDVERSION: Database requires a version upgrade Sep 18 21:31:14 imap ctl_deliver[1019]: DBERROR dup: /var/imap/deliverdb/deliver-z.db: hash version 5 requires a version upgrade Sep 18 21:31:14 imap ctl_deliver[1019]: duplicate_prune: opening /var/imap/deliverdb/deliver-z.db: DB_OLDVERSION: Database requires a version upgrade Sep 18 21:31:14 imap master[1015]: process 1019 exited, status best regards ... Nette Gruesse, Pascal Reinheimer -Ursprüngliche Nachricht- Von: Jeremy Howard [mailto:[EMAIL PROTECTED]] Gesendet: Montag, 17. September 2001 02:28 An: [EMAIL PROTECTED]; [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Betreff: Re: imtest on localhost failed (prot layer failure) > Now i've done this 4 points which you gave to me. > The master process are running, but in the /var/log/messages file the > following lines comes in: > > rdb/deliver-u.db: DB_OLDVERSION: Database requires a version upgrade <...> Read docs/install_upgrade.html in the source distribution to learn how to upgrade to BDB3.
No Subject
imap:/var/imap # /usr/cyrus/bin/ctl_mboxlist -u < mailboxes fatal error: can't initialize mboxlist environment imap:/var/imap # /usr/cyrus/bin/ctl_mboxlist -c fatal error: can't initialize mboxlist environment imap:/var/imap # this errors i got ... mboxlist environment, this looks like that the imap file structure are damaged or ? thank you for your patience ;-) best regards Nette Gruesse, Pascal Reinheimer
No Subject
I got the following messages if i want start the /usr/cyrus/bin/master & process entries Sep 22 18:33:48 imap ctl_deliver[3664]: duplicate_prune: /var/imap/deliverdb/deliver-x.db: purged 0 out of 0 entries Sep 22 18:33:48 imap ctl_deliver[3664]: duplicate_prune: /var/imap/deliverdb/deliver-y.db: purged 0 out of 0 entries Sep 22 18:33:48 imap ctl_deliver[3664]: duplicate_prune: /var/imap/deliverdb/deliver-z.db: purged 0 out of 0 entries Sep 22 18:33:48 imap master[3660]: process 3664 exited, status 0 Sep 22 18:33:49 imap master[3665]: about to exec /usr/cyrus/bin/imapd Sep 22 18:33:49 imap service-imap[3665]: executed 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 Sep 22 18:33:49 imap master[3660]: process 3665 exited, signaled to death by 11 Sep 22 18:34:36 imap su: (to cyrus) root on /dev/pts/0 Sep 22 18:34:40 imap reconstruct[3671]: DBERROR db3: region error detected; run recovery. Sep 22 18:34:41 imap reconstruct[3671]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery Sep 22 18:35:19 imap ctl_mboxlist[3675]: checkpointing mboxlist Sep 22 18:35:19 imap ctl_mboxlist[3675]: DBERROR db3: region error detected; run recovery. Sep 22 18:35:19 imap ctl_mboxlist[3675]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery what could i do to solve this problem ? best regards ... Nette Gruesse, Pascal Reinheimer
AW: your DB3/Cyrus problems
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.01: 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. --
AW: AW: your DB3/Cyrus problems
Hello Pascal, After i've used "db_recover -c -h /var/imap/db" the master process starts, but then a client connect to the imap server the following messages arrives: Sep 22 20:47:25 imap ctl_mboxlist[4030]: done running mboxlist recovery Sep 22 20:47:27 imap master[4032]: about to exec /usr/cyrus/bin/ctl_deliver Sep 22 20:47:28 imap master[4029]: ready for work Sep 22 20:47:28 imap master[4033]: about to exec /usr/cyrus/bin/ctl_mboxlist Sep 22 20:47:29 imap master[4034]: about to exec /usr/cyrus/bin/ctl_deliver Sep 22 20:47:29 imap ctl_deliver[4034]: duplicate_prune: pruning back 3 days Sep 22 20:47:29 imap ctl_mboxlist[4033]: checkpointing mboxlist Sep 22 20:47:29 imap master[4029]: process 4033 exited, status 0 Sep 22 20:47:29 imap ctl_deliver[4034]: duplicate_prune: /var/imap/deliverdb/deliver-a.db: purged 0 out of 0 entries Sep 22 20:47:29 imap ctl_deliver[4034]: duplicate_prune: /var/imap/deliverdb/deliver-b.db: purged 0 out of 0 entries Sep 22 20:47:29 imap ctl_deliver[4034]: duplicate_prune: /var/imap/deliverdb/deliver-c.db: purged 0 out of 0 entries Sep 22 20:47:31 imap ctl_deliver[4034]: duplicate_prune: /var/imap/deliverdb/deliver-z.db: purged 0 out of 0 entries Sep 22 20:47:31 imap master[4029]: process 4034 exited, status 0 Sep 22 20:47:45 imap master[4035]: about to exec /usr/cyrus/bin/imapd Sep 22 20:47:45 imap service-imap[4035]: executed Sep 22 20:47:46 imap imapd[4035]: accepted connection Sep 22 20:47:46 imap master[4029]: process 4035 exited, signaled to death by 11 Nette Gruesse, Pascal Reinheimer -Ursprungliche Nachricht- Von: Pascal Gienger [mailto:[EMAIL PROTECTED]] Gesendet: Samstag, 22. September 2001 18:46 An: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Betreff: Re: AW: your DB3/Cyrus problems >hello pascal, > >thank you for your fast answer! >i've done this but at this time i got this message: [...] >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.01: No such file or direc >tory It complains about not finding the transaction log of your DB3 database. What did you do with your database? You may still try the hard way via a "catastrophic recovery": db_recover -c -h /var/imap/db If you are new to DB3, I suggest reading the manual pages for these db_-utilities, available here: http://www.sleepycat.com/docs/utility/ Pascal Gienger --
AW: your DB3/Cyrus problems
In my opinion the "tools/mkimap" will create the directorys under /var/imap/ ... or ??? But if i start this tool, i get the following message: reading configure file... done Use of uninitialized value at (eval 1) line 85. creating ... Use of uninitialized value at (eval 1) line 87. Use of uninitialized value at (eval 1) line 91. Use of uninitialized value at (eval 1) line 91. couldn't change to at (eval 1) line 91. Nette Gruesse, Pascal Reinheimer -Ursprungliche Nachricht- Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]Im Auftrag von Pascal Reinheimer Gesendet: Samstag, 22. September 2001 18:39 An: 'Pascal Gienger' Cc: [EMAIL PROTECTED] Betreff: AW: your DB3/Cyrus problems 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.01: 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. --
[no subject]
remove
