List Info

Thread: Re: Kolab 2.0.4 upgrade to 2.1 fails due to DBERROR




Re: Kolab 2.0.4 upgrade to 2.1 fails due to DBERROR
country flaguser name
Germany
2007-08-16 03:22:12
Divan Santana <divan.santanagmail.com> writes:

> On Thursday 16 August 2007 09:19:33 Gunnar Wrobel
wrote:
>> Just read this again and wondered if you meant that
you converted the
>> files to berkeley db but did not switch from
skiplist to berkeley db
>> in the imapd.conf.template. Probably not.
>>
>> Could you check the format of the
mailbox/annotation.db again. Does it
>> have "skiplist" on the first few bytes or
is is berkeley?
>
> Didn't mean the above. I tried to keep it as skiplist
and commented out the 
> things in imapd.conf.template as per upgrade notes.
>
> Is this what you wanted me to do?
>
> #:/home/kolab2fail/kolab/var/imapd# file
annotations.db
> annotations.db: Cyrus skiplist DB

Yes 
But that would mean that your problem does not result from
either the annotations.db or mailbox.db file. Question is
which file
berkeley db does complain about.

The tls_sessions.db is by default in berkeley format.

file /kolab/var/imapd/tls_sessions.db 
/kolab/var/imapd/tls_sessions.db: Berkeley DB (Btree,
version 9, native byte-order)

I think this is just a session cache so you should be able
to move it
away and restard cyrus imapd:

cd /kolab/var/imapd
mv tls_sessions.db tls_sessions.db.old
/kolab/bin/openpkg rc imapd restart

Just a wild guess. Does it help?

Cheers,

Gunnar


-- 
______ http://kdab.com
_______________ http://kolab-konsortium.c
om _

prdus Kolab work is funded in part by KDAB and the
Kolab Konsortium

____ http://www.pardus.de
_________________ http://gunnarwrobel.de _
E-mail : prdus.de                                 Dr. Gunnar
Wrobel
Tel.   : +49 40 432 72335                          
Bundesstrasse 29
Fax    : +49 40 432 70855                            D-20146
Hamburg
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~
   >> Mail at ease - Rent a kolab groupware server at
prdus <<                 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~

_______________________________________________
Kolab-users mailing list
Kolab-userskolab.org
https:
//kolab.org/mailman/listinfo/kolab-users

Re: Kolab 2.0.4 upgrade to 2.1 fails due to DBERROR
country flaguser name
South Africa
2007-08-16 04:24:08
On Thursday 16 August 2007 10:22:12 Gunnar Wrobel wrote:
> Yes  But that
would mean that your problem does not result from
> either the annotations.db or mailbox.db file. Question
is which file
> berkeley db does complain about.
>
> The tls_sessions.db is by default in berkeley format.
>
> file /kolab/var/imapd/tls_sessions.db
> /kolab/var/imapd/tls_sessions.db: Berkeley DB (Btree,
version 9, native
> byte-order)
>
> I think this is just a session cache so you should be
able to move it
> away and restard cyrus imapd:
>
> cd /kolab/var/imapd
> mv tls_sessions.db tls_sessions.db.old
> /kolab/bin/openpkg rc imapd restart
>
> Just a wild guess. Does it help?

I'll have to try after hours to put the broken system back
in place and try 
that because I reverted to my backup when it failed so I am
still on the old 
version.

Note that both tls_sessions.db and deliver.db: Berkeley DB
(Btree, version 9, 
native byte-order) and Berkeley DB.

Could it not be the deliver.db file?

I've got two things I'm going to try to fix this.
1) Your suggestion
2) Try upgrade again but this time convert my imap files to
Berkeley DB and 
not keep it on skiplist as per upgrade notes.

Will let you know the outcome, will try this weekend again.


Thanks!!

-- 
Divan Santana

Skype:                  DivanSantana
Gtalk/MSN:              Divan.SantanaGMail.com


Love God, Love People, Love Life!

_______________________________________________
Kolab-users mailing list
Kolab-userskolab.org
https:
//kolab.org/mailman/listinfo/kolab-users

[1-2]

about | contact  Other archives ( Real Estate discussion Medical topics )