Dear,
When i am trying to recover the cyrus database as given by
troubleshoot kolab we found following errors
"fatal error: can't open old database"
[root indo ~]# head -c 17 /kolab/var/imapd/mailboxes.db |
tail -c 13
��b1 [rootindo ~]#
[rootindo ~]#
[rootindo ~]#
[rootindo ~]# /kolab/bin/openpkg rc all start
OpenPKG: start: openpkg, openldap, sasl, spamassassin,
amavisd, apache, clamav
OpenPKG: start: imapd, postfix, proftpd, kolabd.
[rootindo ~]# head -c 17 /kolab/var/imapd/mailboxes.db |
tail -c 13
��b1 [rootindo ~]#
[rootindo ~]#
[rootindo ~]#
[rootindo ~]# /kolab/bin/openpkg rc imapd stop
OpenPKG: stop: imapd.
[rootindo ~]# su - kolab-r
kolab-rindo$ cd /kolab/var/imapd/
kolab-rindo$ mv annotations.db annotations.db-skiplist
kolab-rindo$ cvt_cyrusdb
/kolab/var/imapd/annotations.db-skiplist
skiplist /kolab/var/imapd/annotations.db berkeley
Converting from /kolab/var/imapd/annotations.db-skiplist
(skiplist) to
/kolab/var/imapd/annotations.db (berkeley)
fatal error: can't open old database
with rgds
rajnish
On Jan 9, 2008 1:09 PM, Gunnar Wrobel <wrobelpardus.de> wrote:
>
> "rajnish krishna" <krishnarajnishguptagmail.com> writes:
>
> > Dear friends
> > Now a days i find some cyrus
DB error in my
> > Kolab2.1 servers. Have any one has opinion about
this imap.log file
> > is like this
> >
> >
> >
> > Jan 09 11:36:49 indo <error> imap[3800]:
DBERROR: opening
> > /kolab/var/imapd/mailboxes.db: cyrusdb error
> > Jan 09 11:36:49 indo <error> imap[3800]:
Fatal error: can't read mailboxes file
> > Jan 09 11:36:49 indo <debug> imap[3802]:
executed
> > Jan 09 11:36:49 indo <warning> imap[3802]:
DBERROR db4: Logging region
> > out of memory; you may need to increase its size
> > Jan 09 11:36:49 indo <error> imap[3802]:
DBERROR: opening
> > /kolab/var/imapd/mailboxes.db: Cannot allocate
memory
> > Jan 09 11:36:49 indo <error> imap[3802]:
DBERROR: opening
> > /kolab/var/imapd/mailboxes.db: cyrusdb error
> > Jan 09 11:36:49 indo <error> imap[3802]:
Fatal error: can't read mailboxes file
> > Jan 09 11:36:49 indo <debug> imap[3804]:
executed
>
> I have sseen this on a Gentoo server once and we
discussed it on the
> Kolab2/Gentoo forum: htt
p://forum.pardus.de/index.php?topic=156.msg525
>
> I'm afraid that we didn't find a solution for it yet.
I'd suggest you
> open a bug report in the Kolab bug tracker.
>
> You should try to repair the berkley database with the
standard
> berkeley db tools. If this does not help you might also
wish to revert
> back to skiplist format for the mailboxes.db.
>
> Cheers,
>
> Gunnar
>
> >
> >
> > with regds
> > rajnish
> >
> > _______________________________________________
> > Kolab-users mailing list
> > Kolab-userskolab.org
> > https:
//kolab.org/mailman/listinfo/kolab-users
>
> --
> ______ 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 700 6245 0000
Bundesstrasse 29
> Fax : +49 721 1513 52322
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
|
