I am having a very strange issue where the imap server stops accepting
messages via LMTP, does not allow logins via imap, and the load
reaches anywhere from 800 - 2000. This happens nearly daily. Also, I
notice there are generally many defunct processes and the below pasted
excerpt from the
On Nov 27, 2007 4:42 PM, Gerard [EMAIL PROTECTED] wrote:
I am having a very strange issue where the imap server stops accepting
messages via LMTP, does not allow logins via imap, and the load
reaches anywhere from 800 - 2000. This happens nearly daily.
Daily ? On a regular basis ? At backup
On Nov 27, 2007 11:53 AM, Alain Spineux [EMAIL PROTECTED] wrote:
On Nov 27, 2007 4:42 PM, Gerard [EMAIL PROTECTED] wrote:
I am having a very strange issue where the imap server stops accepting
messages via LMTP, does not allow logins via imap, and the load
reaches anywhere from 800 - 2000.
When I try to run the following command line from
/usr/share/doc/cyrus-common-2.2/README.Debian.database.gz
/usr/sbin/cvt_cyrusdb /var/lib/cyrus/deliver.db db3 /var/lib/cyrus/temp.db flat
I get the following error message:
fatal error: unknown old backend
What's unknown here? The db3
-- Gerard [EMAIL PROTECTED] is rumored to have mumbled on 27.
November 2007 12:22:42 -0500 regarding Re: lmtp timed out while sending
MAIL FROM:
Some DBERROR in the logs somewhere ?
There were, but not anymore. In troubleshooting the issues we
converted deliver.db to skiplist rather then BDB
On Nov 27, 2007 6:22 PM, Gerard [EMAIL PROTECTED] wrote:
On Nov 27, 2007 11:53 AM, Alain Spineux [EMAIL PROTECTED] wrote:
Daily ?
Yes, over the last 7 days it didn't happen on one day, Thanksgiving. I
would probably attribute that to very low load.
On a regular basis ?
Yes. I generally
On Nov 27, 2007 6:59 PM, Steinar Bang [EMAIL PROTECTED] wrote:
When I try to run the following command line from
/usr/share/doc/cyrus-common-2.2/README.Debian.database.gz
/usr/sbin/cvt_cyrusdb /var/lib/cyrus/deliver.db db3 /var/lib/cyrus/temp.db
flat
I get the following error message:
This of course sounds familiar to some experiences we had
recently with Cyrus 2.3.8 on Solaris 10 backends pretty
heavily loaded with number of users. If you search the
mailing list archives you'll find several threads about our
problems here at UC Davis.
However, the others in the thread have
Steinar Bang [EMAIL PROTECTED]:
When I try to run the following command line from
/usr/share/doc/cyrus-common-2.2/README.Debian.database.gz
/usr/sbin/cvt_cyrusdb /var/lib/cyrus/deliver.db db3 /var/lib/cyrus/temp.db
flat
I get the following error message:
fatal error: unknown old
Alain Spineux [EMAIL PROTECTED]:
On Nov 27, 2007 6:59 PM, Steinar Bang [EMAIL PROTECTED] wrote:
When I try to run the following command line from
/usr/share/doc/cyrus-common-2.2/README.Debian.database.gz
/usr/sbin/cvt_cyrusdb /var/lib/cyrus/deliver.db db3 /var/lib/cyrus/temp.db
flat
I
On Nov 27, 2007 7:53 PM, Steinar Bang [EMAIL PROTECTED] wrote:
Alain Spineux [EMAIL PROTECTED]:
On Nov 27, 2007 6:59 PM, Steinar Bang [EMAIL PROTECTED] wrote:
When I try to run the following command line from
/usr/share/doc/cyrus-common-2.2/README.Debian.database.gz
Steinar Bang [EMAIL PROTECTED]:
That fails with a different error message:
$ /usr/sbin/cvt_cyrusdb /var/lib/cyrus/deliver.db berkeley
/var/lib/cyrus/temp.db flat
Converting from /var/lib/cyrus/deliver.db (berkeley) to
/var/lib/cyrus/temp.db (flat)
fatal error: can't open old database
Alain Spineux [EMAIL PROTECTED]:
#file filename
# file /var/lib/cyrus/deliver.db
/var/lib/cyrus/deliver.db: Berkeley DB (Btree, version 8, native byte-order)
The 2.1 tools, you mean? Too late. They went out when I apt-get
installed 2.2.
Yes, the old one, including the corresponding
Steinar Bang [EMAIL PROTECTED]:
Where does the read marks on the messages live? Can't be in the
mailbox.db file. It's way too small, and so is its text counterpart.
They're as \*.seen under /var/lib/cyrus/user/...
And they are already skiplists according to file:
# file
Steinar Bang [EMAIL PROTECTED]:
Does this mean they don't require rebuilding when moving from cyrus 2.1
to 2.2?
If that is true, and if the text version of the mailboxes file is what I
need, then I should be able to survive this...:-)
(but I don't dare start cyrus22 until I hear some sort
Steinar Bang [EMAIL PROTECTED]:
Does this mean they don't require rebuilding when moving from cyrus 2.1
to 2.2?
If that is true, and if the text version of the mailboxes file is what I
need, then I should be able to survive this...:-)
(but I don't dare start cyrus22 until I hear some sort
Steinar Bang [EMAIL PROTECTED]:
Steinar Bang [EMAIL PROTECTED]:
Does this mean they don't require rebuilding when moving from cyrus 2.1
to 2.2?
If that is true, and if the text version of the mailboxes file is what I
need, then I should be able to survive this...:-)
(but I don't dare
I found the following in /var/log/syslog:
Nov 27 21:55:39 doohan cyrus/cvt_cyrusdb[7682]: DBERROR db4: Program version
4.2 doesn't match environment version
Nov 27 21:55:39 doohan cyrus/cvt_cyrusdb[7682]: DBERROR: dbenv-open
'/var/lib/cyrus/db' failed: Invalid argument
Nov 27 21:55:39 doohan
Well, for those following this thread. The problems with starting
cyrus2.2 after upgrading the mailboxes.db to skiplist, was because I
hadn't done the final step of the file
/usr/share/doc/cyrus-common-2.2/README.Debian.database.gz :
3. Reset the database backend change system
rm
Steinar,
You would use ctl_mboxlist to restore the mboxlist.txt file if you used
ctl_mboxlist to dump it.
for example, my weekly crontab backs up my mailboxes.db in a textfile,
such as
su -c /usr/lib/cyrus/ctl_mboxlist -d cyrus
/imap.backup/mailboxes.$DATE.txt
You would use
Steinar Bang [EMAIL PROTECTED]:
So now it's seemingly up and running, but so far not with imaps,
appearently. I need to restore my old SSL and whatever, config settings
(whatever they were. When I do this only every two or three years or
so, things tend to go dim...).
Now I've got imaps
Hello All,
I've moved my old mail server to a new hardware and everything is working
fine. Although I found some redundant mail accounts and deleted some of
them.
The problem is that I'm not able to delete cyrus mailbox this way:
# cyradm --user cyrus --server localhost --auth plain
Password:
22 matches
Mail list logo
