Re: Problems upgrading from cyrus 2.1.18 to 2.2.13 on debian etch

2007-11-28 Thread Steinar Bang
> Steinar Bang <[EMAIL PROTECTED]>: > Now I've got imaps up and running, and according to the log some new > messages have been delivered. But my imap clients reports no messages > in the folders. > Are there problems with the .seen files, I wonder...? > Do skiplist files have to be convert

Re: Problems upgrading from cyrus 2.1.18 to 2.2.13 on debian etch

2007-11-27 Thread Steinar Bang
> 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 g

Re: Problems upgrading from cyrus 2.1.18 to 2.2.13 on debian etch

2007-11-27 Thread Scott M. Likens
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 ctl_mboxl

Re: Problems upgrading from cyrus 2.1.18 to 2.2.13 on debian etch

2007-11-27 Thread Steinar Bang
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 /usr/lib/cyru

Re: Problems upgrading from cyrus 2.1.18 to 2.2.13 on debian etch

2007-11-27 Thread Steinar Bang
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 cyr

Re: Problems upgrading from cyrus 2.1.18 to 2.2.13 on debian etch

2007-11-27 Thread Steinar Bang
> 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...:-

Re: Problems upgrading from cyrus 2.1.18 to 2.2.13 on debian etch

2007-11-27 Thread Steinar Bang
> 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

Re: Problems upgrading from cyrus 2.1.18 to 2.2.13 on debian etch

2007-11-27 Thread Steinar Bang
> 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

Re: Problems upgrading from cyrus 2.1.18 to 2.2.13 on debian etch

2007-11-27 Thread Steinar Bang
> 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 /var/lib/c

Re: Problems upgrading from cyrus 2.1.18 to 2.2.13 on debian etch

2007-11-27 Thread Steinar Bang
> "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 corr

Re: Problems upgrading from cyrus 2.1.18 to 2.2.13 on debian etch

2007-11-27 Thread Steinar Bang
> 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

Re: Problems upgrading from cyrus 2.1.18 to 2.2.13 on debian etch

2007-11-27 Thread Alain Spineux
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

Re: Problems upgrading from cyrus 2.1.18 to 2.2.13 on debian etch

2007-11-27 Thread Steinar Bang
> "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/

Re: Problems upgrading from cyrus 2.1.18 to 2.2.13 on debian etch

2007-11-27 Thread Steinar Bang
> 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: unkno

Re: Problems upgrading from cyrus 2.1.18 to 2.2.13 on debian etch

2007-11-27 Thread Alain Spineux
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 messa

Problems upgrading from cyrus 2.1.18 to 2.2.13 on debian etch

2007-11-27 Thread Steinar Bang
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" argume