[csw-maintainers] Cyrus imapd update

[Rafael Ostertag]

On Sat, Jan 21, 2012 at 03:10:34PM +0100, Yann Rouillard wrote:
> Le 21/01/2012 14:59, Rafael Ostertag a ?crit :
> >On Sat, Jan 21, 2012 at 02:37:29PM +0100, Yann Rouillard wrote:
> >>The configuration file you used explicitly configured berkeleydb as
> >>the backend.
> >>
> >>The bug is triggered if the administrator kept the default settings
> >>(and I suppose some admins do not change this setting).
> >>The default backend for most cyrus database was berkeleydb before
> >>2.4 and is now skiplist since 2.4.
> >Yes, I saw that, but I was referring to `what if somebody has explicitely set berkeleydb'.
> >
> In this casen it should not be a problem if berkeleydb handles
> gracefully the upgrade from 4.2 to 4.8.

I will test again, with bigger databases this time (few thousand mails
delievered)

> 
> >>Cyrus tries to automagically upgrade from berkeleydb to skiplist and
> >>this is what didn't work as expected in my tests.
> >>
> >>Have a look at the bug I opened upstream
> >>https://bugzilla.cyrusimap.org/show_bug.cgi?id=3496, I explained the
> >>bug and attached files which should allow you to reproduce the bug.
> >>You will notice the bug happens the second time you launch cyrus.
> >>
> >>(Although I am surprised you didn't run into some berkeleydb problem
> >>if you upgraded to berkeleydb 4.8).
> >Me too, taking into account what I heard so far about bdb. Did bdb 4.8 improve
> >that, perhaps?
> That's possible. We should check if the bug still happens with
> berkeleydb 4.8.
Yes, I can do that.

> 
> Because of the berkeleydb reputation, I think we should do more
> extensive test with berkeleydb.
> 
> >It appears from your bug report, that only deliver.db is affected, and since it
> >is used `only' for duplicate delivery supression, why not taking a radical
> >approach and just kill it on upgrade?
> The problem isn't exactly deliver.db. deliver.db is correctly
> converted but somehow, a reference to deliver.db is kept in the db
> files and when the berkeleydb backend is initialized, it reads the
> db files and is not happy with that.
> Removing the db/ directory before launching cyrus solves the
> problem, but it's not a solution if there is some database which
> should stay in berkeleydb format.

Well, there goes my radical approach. :)
> 
> About deliver.db, it is also used to keep track of vacation message
> already sent. Not very important also but we should warn the users.
> But the problem may also happen with annotations.db (I never used
> this one but some setup could).
I see.

> 
> Yann
> 
> >--rafi
> >>Yann
> >>
> >>
> >>Le 21/01/2012 13:40, Rafael Ostertag a ?crit :
> >>>Hi Yann
> >>>
> >>>On Sat, Jan 21, 2012 at 12:55:39PM +0100, Rafael Ostertag wrote:
> >>>>>It will probably break the setup of people who explicitely
> >>>>>configured berkeleydb for cyrus database and the upgrade path should
> >>>>>be documented.
> >>>>Hmm, let me check this.
> >>>I used the this imapd.conf: http://paste.pocoo.org/show/538215/
> >>>
> >>>Same procedure:
> >>>
> >>>  1. installed 2.3.16
> >>>  2. created 2 users
> >>>  3. sent some mails
> >>>  4. upgraded to 2.4
> >>>
> >>>No errors so far. Would you say that is sufficient, or do we have to make a
> >>>more sophisticated test setup?
> >>>
> >>>cheers
> >>>rafi
> >>>
> >>>_______________________________________________
> >>>maintainers mailing list
> >>>maintainers at lists.opencsw.org
> >>>https://lists.opencsw.org/mailman/listinfo/maintainers
> >>>.:: This mailing list's archive is public. ::.
> >>_______________________________________________
> >>maintainers mailing list
> >>maintainers at lists.opencsw.org
> >>https://lists.opencsw.org/mailman/listinfo/maintainers
> >>.:: This mailing list's archive is public. ::.
> >>
> >_______________________________________________
> >maintainers mailing list
> >maintainers at lists.opencsw.org
> >https://lists.opencsw.org/mailman/listinfo/maintainers
> >.:: This mailing list's archive is public. ::.
> 
> _______________________________________________
> maintainers mailing list
> maintainers at lists.opencsw.org
> https://lists.opencsw.org/mailman/listinfo/maintainers
> .:: This mailing list's archive is public. ::.
>