Upgrade from 2.0 to 2.2.2 with new server

[greenpenguin at free.fr]

Hi,

This is almost Ok.
I have followed the instructions to upgrade from 2.0 to 2.1 and then the 2.1 to
2.2.
I will write a documentation.

The server is in production but I have a problem.

The imapd crashes when there is load.
In the imapd.log, we can find :
Jul 27 10:00:14 srvmail <warning> imap[25452]: DBERROR db4: Logging region out
of memory; you may need to increase its size
Jul 27 10:00:14 srvmail <error> imap[25452]: DBERROR: opening
/kolab/var/imapd/annotations.db: Cannot allocate memory
Jul 27 10:00:14 srvmail <error> imap[25452]: DBERROR: opening
/kolab/var/imapd/annotations.db: cyrusdb error
Jul 27 10:00:14 srvmail <error> imap[25452]: Fatal error: can't read annotations
file
J

The only solution I have found is to to remove the annotations.db and restart
the imapd service.

I have searched on Internet and the solution would be to configure DB4 with
DB_CONFIG.
How to do this ? Where is the file ?
The only file I found is in the LDAP configuration ?

I need your help because the server is in production.

Thanks by advance

Green Penguin


Selon greenpenguin at free.fr:

> Ok I will try to use the 2.0->2.1 instructions and then the 2.1->2.2
> instructions.
>
> I am interesting for the instructions to import existing data into a fresh
> installation. I think, it's very important for the future.
>
>
>
>
>
> Selon "Arendsen Hein, Thomas" <thomas at intevation.de>:
> > The default structure in 2.1.x and 2.2.x has changed compared to
> > 2.0.x, but you can just comment the "hashimapspool: yes" line in
> > /kolab/etc/kolab/templates/imapd.conf.template (as described in the
> > 2.0->2.1 upgrading docs).
> >
> > Alternatively you can use
> >
>
http://kolab.org/cgi-bin/viewcvs-kolab.cgi/*checkout*/utils/admin/hash-imap-spool
> > to convert it from the old format to the current.
> >
> > I think your best bet for now is to follow the 2.0->2.1
> > instructions and then the 2.1->2.2 instructions. I think this should
> > even work without installing the 2.1 packages first, but directly
> > install the 2.2 ones.
> >
> > > @thomas: The 1st.README states "Instructions for upgrading from Kolab
> > > server 2.0 will be added in a future version of this document." Is
> > > this still on the list of things to do?
> >
> > Somehow, but with lower priority, as there is above workaround.
> >
> > More interesting would be instructions to import existing data into
> > a fresh installations. We already have a draft for that and it was
> > already used in production once, but it needs some more work before
> > this can be published.
> >
> > Thomas
> >
> > --
> > thomas at intevation.de - http://intevation.de/~thomas/ - OpenPGP key:
> > 0x5816791A
> > Intevation GmbH, Neuer Graben 17, 49074 Osnabrueck - AG Osnabrueck, HR B
> > 18998
> > Geschaeftsfuehrer: Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner
> >
> > _______________________________________________
> > Kolab-users mailing list
> > Kolab-users at kolab.org
> > https://kolab.org/mailman/listinfo/kolab-users
> >
>
>
> _______________________________________________
> Kolab-users mailing list
> Kolab-users at kolab.org
> https://kolab.org/mailman/listinfo/kolab-users
>