Re: cyrus 2.4 and DBERROR

[Anthony Prades via Info-cyrus]

Hi,

Try db_recover tool in /var/lib/cyrus, somithing like (depends of your 
install):

-- stop cyrus --
cd /var/lib/cyrus && db_recover -v -h /var/lib/cyrus/db
-- start cyrus --

or herder version:
-- stop cyrus --
cd /var/lib/cyrus && db_recover -c -v -h /var/lib/cyrus/db
-- start cyrus --

If problem persists, you may convert your db file to flat, then flat to 
db using cvt_cyrusdb tool - something like:

-- stop cyrus --
cvt_cyrusdb /var/lib/cyrus/mailboxes.db skiplist /tmp/mailboxes flat
mv /var/lib/cyrus/mailboxes.db /var/lib/cyrus/mailboxes.db.orig
cvt_cyrusdb /tmp/mailboxes flat /var/lib/cyrus/mailboxes.db skiplist
chown cyrus:mail /var/lib/cyrus/mailboxes.db
-- start cyrus --

Note: do backup before...

Anthony

On 12/1/18 8:20 AM, chose wrote:

 Good morning,
 what caused this and how to recover. All files in db/ directory were 
deleted and cyrus restarted, still no progress.


Dec  1 07:57:44 email11 imap[4498]: DBERROR db4: PANIC: fatal region 
error detected; run recovery

Dec  1 07:57:44 email11 imap[4498]: DBERROR: critical database situation
Dec  1 07:57:44 email11 idled[4422]: DBERROR db4: PANIC: fatal region 
error detected; run recovery

Dec  1 07:57:44 email11 idled[4422]: DBERROR: critical database situation
Dec  1 07:57:44 email11 imap[4428]: DBERROR db4: PANIC: fatal region 
error detected; run recovery

Dec  1 07:57:44 email11 imap[4428]: DBERROR: critical database situation
Dec  1 07:57:44 email11 imap[4482]: DBERROR db4: PANIC: fatal region 
error detected; run recovery


  Cyrus imap is working, but it si slow.
  Thanks and best regards
  J.Karliak



Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
To Unsubscribe:
https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus

cyrus 2.4 and DBERROR

[chose]

 Good morning,
 what caused this and how to recover. All files in db/ directory were 
deleted and cyrus restarted, still no progress.


Dec  1 07:57:44 email11 imap[4498]: DBERROR db4: PANIC: fatal region 
error detected; run recovery

Dec  1 07:57:44 email11 imap[4498]: DBERROR: critical database situation
Dec  1 07:57:44 email11 idled[4422]: DBERROR db4: PANIC: fatal region 
error detected; run recovery
Dec  1 07:57:44 email11 idled[4422]: DBERROR: critical database 
situation
Dec  1 07:57:44 email11 imap[4428]: DBERROR db4: PANIC: fatal region 
error detected; run recovery

Dec  1 07:57:44 email11 imap[4428]: DBERROR: critical database situation
Dec  1 07:57:44 email11 imap[4482]: DBERROR db4: PANIC: fatal region 
error detected; run recovery


  Cyrus imap is working, but it si slow.
  Thanks and best regards
  J.Karliak

--
Ma domena pouziva zabezpeceni a kontrolu SPF (www.openspf.org) a
DomainKeys/DKIM (s ADSP) a implementaci DMARC. Pokud mate problemy s
dorucenim emailu, zacnete pouzivat metody overeni puvody emailu
zminene vyse. Dekuji.
My domain use SPF (www.openspf.org) and DomainKeys/DKIM (with ADSP)
policy and implementation of the DMARC. If you've problem with sending
emails to me, start using email origin methods mentioned above. Thank
you.

Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
To Unsubscribe:
https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus

tls_prune DBERROR

[Janos Dohanics]

Hello,

I have cyrus-imapd24-2.4.18_4 running on FreeBSD 11.0-STABLE.

I got these error messages in the log file:

Dec 29 04:00:00 cortina tls_prune[29126]: DBERROR db5: pthread suspend failed: 
Invalid argument
Dec 29 04:00:00 cortina tls_prune[29126]: DBERROR db5: BDB0061 PANIC: Invalid 
argument
Dec 29 04:00:00 cortina tls_prune[29126]: DBERROR: critical database situation
Dec 29 04:00:03 cortina ctl_cyrusdb[29128]: DBERROR db5: BDB0060 PANIC: fatal 
region error detected; run recovery
Dec 29 04:00:03 cortina ctl_cyrusdb[29128]: DBERROR: critical database situation
Dec 29 04:00:05 cortina cyr_expire[29127]: DBERROR db5: BDB1581 File handles 
still open at environment close
Dec 29 04:00:05 cortina cyr_expire[29127]: DBERROR db5: BDB1582 Open file 
handle: /usr/local/imap/db/__db.001
Dec 29 04:00:05 cortina cyr_expire[29127]: DBERROR db5: BDB1582 Open file 
handle: /usr/local/imap/db/__db.002
Dec 29 04:00:05 cortina cyr_expire[29127]: DBERROR db5: BDB1582 Open file 
handle: /usr/local/imap/db/__db.003

Cyrus is configured to use skiplist:

# file /usr/local/imap/*.db
/usr/local/imap/annotations.db:  Cyrus skiplist DB
/usr/local/imap/deliver.db:  Cyrus skiplist DB
/usr/local/imap/mailboxes.db:Cyrus skiplist DB
/usr/local/imap/statuscache.db:  Cyrus skiplist DB
/usr/local/imap/tls_sessions.db: Cyrus skiplist DB

I suppose I shut down cyrus and do "ctl_cyrusdb -r", correct?

Anything I could do to prevent this error from occurring again?

-- 
Janos Dohanics

Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
To Unsubscribe:
https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus

R: Re: R: Re: R: Re: DBERROR: critical database situation

[absolutely_free--- via Info-cyrus]

I followed those steps:

1) shutdown imap daemon
2) rm /var/imap/db/* 
3) rm /var/imap/tls_session.db and /var/imap/deliver.db
4) reconstruct -f (as cyrus user)
5) changed /usr/local/etc/imapd.conf in this manner:

#tlscache_db: berkeley-nosync
tlscache_db: skiplist

#ptscache_db: berkeley
ptscache_db: skiplist

#duplicate_db: berkeley
duplicate_db: skiplist

6) start imap daemon

it seems quite stable.
I hope it is solved.
Thank you all for support!



Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
To Unsubscribe:
https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus

Re: R: Re: R: Re: DBERROR: critical database situation

[Bron Gondwana via Info-cyrus]

Just removing the config options that say berkeley for those two databases in 
imapd.conf should do the trick (followed by nuking them again, and while Cyrus 
is shut down)

Bron.

On Wed, 4 Jan 2017, at 22:08, absolutely_free--- via Info-cyrus wrote:
> After deleting /var/imap/db/*, /var/imap/mailboxes.db and 
> /var/imap/deliver.db, 
> it rans fine for about 20 minutes, and after:
> 
> Jan  4 11:58:41 mail lmtpunix[60214]: DBERROR db5: pthread suspend failed: 
> Invalid argument
> Jan  4 11:58:41 mail lmtpunix[60214]: DBERROR db5: BDB0061 PANIC: Invalid 
> argument
> Jan  4 11:58:41 mail lmtpunix[60214]: DBERROR: critical database situation
> Jan  4 11:58:41 mail lmtpunix[60215]: DBERROR db5: BDB0060 PANIC: fatal 
> region 
> error detected; run recovery
> Jan  4 11:58:41 mail lmtpunix[60215]: DBERROR: critical database situation
> Jan  4 11:58:41 mail master[60046]: service lmtpunix pid 60215 in READY 
> state: 
> terminated abnormally
> Jan  4 11:58:41 mail lmtpunix[60217]: DBERROR db5: BDB0060 PANIC: fatal 
> region 
> error detected; run recovery
> Jan  4 11:58:41 mail lmtpunix[60217]: DBERROR: critical database situation
> Jan  4 11:58:41 mail master[60046]: service lmtpunix pid 60217 in READY 
> state: 
> terminated abnormally
> Jan  4 11:58:41 mail lmtpunix[60218]: DBERROR db5: BDB0060 PANIC: fatal 
> region 
> error detected; run recovery
> Jan  4 11:58:41 mail lmtpunix[60218]: DBERROR: critical database situation
> Jan  4 11:58:41 mail master[60046]: service lmtpunix pid 60218 in READY 
> state: 
> terminated abnormally
> Jan  4 11:58:41 mail lmtpunix[60219]: DBERROR db5: BDB0060 PANIC: fatal 
> region 
> error detected; run recovery
> Jan  4 11:58:41 mail lmtpunix[60219]: DBERROR: critical database situation
> Jan  4 11:58:41 mail master[60046]: service lmtpunix pid 60219 in READY 
> state: 
> terminated abnormally
> Jan  4 11:58:41 mail lmtpunix[60220]: DBERROR db5: BDB0060 PANIC: fatal 
> region 
> error detected; run recovery
> Jan  4 11:58:41 mail lmtpunix[60220]: DBERROR: critical database situation
> Jan  4 11:58:41 mail master[60046]: service lmtpunix pid 60220 in READY 
> state: 
> terminated abnormally
> Jan  4 11:58:41 mail lmtpunix[60221]: DBERROR db5: BDB0060 PANIC: fatal 
> region 
> error detected; run recovery
> Jan  4 11:58:41 mail lmtpunix[60221]: DBERROR: critical database situation
> Jan  4 11:58:41 mail master[60046]: service lmtpunix pid 60221 in READY 
> state: 
> terminated abnormally
> 
> 
> I am wondering what is my best option?
> Upgrade to 2.4 (at least)?
> 
> Thank you
> 
> 
> >Messaggio originale
> >Da: "Niels Dettenbach" 
> >Data: 04/01/2017 11.28
> >A: , "absolutely_f...@libero.it"
> 
> >Ogg: Re: R: Re: DBERROR: critical database situation
> >
> >Am Mittwoch, 4. Januar 2017, 11:18:42 CET schrieb absolutely_free--- via 
> Info-
> >cyrus:
> >> ./tls_sessions.db: Berkeley DB (Btree, version 9, little-endian)
> >> ./deliver.db: Berkeley DB (Btree, version 9, little-endian)
> >> 
> >> So, I can convert tls_sessions and deliver db to skiplist format, right?
> >> How can I determine which database is giving me "DBERROR: critical database
> >> situation"?
> >
> >As far as i remember, it is uncritical to just delete both files, without 
> >loosing "practical" data. tls_sessions just held details to ("running") TLS 
> >Sessions and deliver.db avoids duplicates if i remember correctly.
> >
> >Stop cyrus - do a backup of delliver.db and tls_sessions.db (or just "Move 
> it 
> >out of the way) for security (but i'm pretty shure that you can delete it) 
> or 
> >try to just delete it and restart. 
> >
> >After that try to run reconstruct -f to re-generate any indize files etc. 
> >within the mailboxes itself.
> >
> >If that not helps, come back again. ß)
> >
> >hth a bit,
> >best regards and good luck,
> >
> >Niels.
> >
> >
> >-- 
> > ---
> > Niels Dettenbach
> > Syndicat IT & Internet
> > http://www.syndicat.com
> > PGP: https://syndicat.com/pub_key.asc
> > ---
> > 
> >
> >
> >
> >
> 
> 
> 
> Cyrus Home Page: http://www.cyrusimap.org/
> List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
> To Unsubscribe:
> https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus


-- 
  Bron Gondwana
  br...@fastmail.fm

Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
To Unsubscribe:
https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus

Re: R: Re: DBERROR: critical database situation

[Bron Gondwana via Info-cyrus]

Oh good, you can just delete those two BDB files with Cyrus shut down (and 
change them to skiplist while you're at it!)

Once you've done that you can delete everything in the $confdir/db folder too.

(delete might mean take a copy somewhere else until you're happy everything is 
working of course)

They're both things that don't matter across restarts.

Bron.

On Wed, 4 Jan 2017, at 21:18, absolutely_free--- via Info-cyrus wrote:
> Hi Niels,
> 
> thank you for your reply.
> I am using cyrus from sources (ports).
> 
> root@mail:/var/imap# find . -name "*.db" -exec file '{}' \;
> ./mailboxes.db: Cyrus skiplist DB
> ./annotations.db: Cyrus skiplist DB
> ./db.backup1/annotations.db: Cyrus skiplist DB
> ./db.backup1/mailboxes.db: Cyrus skiplist DB
> ./tls_sessions.db: Berkeley DB (Btree, version 9, little-endian)
> ./db.backup2/annotations.db: Cyrus skiplist DB
> ./db.backup2/mailboxes.db: Cyrus skiplist DB
> ./deliver.db: Berkeley DB (Btree, version 9, little-endian)
> 
> So, I can convert tls_sessions and deliver db to skiplist format, right?
> How can I determine which database is giving me "DBERROR: critical database 
> situation"?
> 
> Thank you
> 
> 
> Cyrus Home Page: http://www.cyrusimap.org/
> List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
> To Unsubscribe:
> https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus


-- 
  Bron Gondwana
  br...@fastmail.fm

Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
To Unsubscribe:
https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus

Re: R: Re: R: Re: DBERROR: critical database situation

[Niels Dettenbach via Info-cyrus]

Am Mittwoch, 4. Januar 2017, 12:08:55 CET schrieb absolutely_free--- via Info-
cyrus:
> After deleting /var/imap/db/*, /var/imap/mailboxes.db and
> /var/imap/deliver.db, it rans fine for about 20 minutes, and after:
tls_sessions and deliver.db are not important (afaik) .

Files within ./db ARE important data files (which are only to delete when going 
the migration procedure to skiplist during that procedure). You other files 
still was skiplist (as your listing shows) - so they did not need that 
migration anymore.

Did deleting tls_sessions and deliver.db (alone and by my described procedure) 
not helped?

The error shows that there still are files within the "old" db format (i assume 
tls_sessions.db and deliver.db).

hth a bit,
good luck,


Niels.

-- 
 ---
 Niels Dettenbach
 Syndicat IT & Internet
 http://www.syndicat.com
 PGP: https://syndicat.com/pub_key.asc
 ---
 





signature.asc
Description: This is a digitally signed message part.

Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
To Unsubscribe:
https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus

Re: R: Re: DBERROR: critical database situation

[Bron Gondwana via Info-cyrus]

Indeed, with all the right libraries.  You can't upgrade libdb without
everything going to shit, which is why we have ditched BDB - the upgrade
path is bogus.


Bron.





On Wed, 4 Jan 2017, at 21:20, absolutely_free--- via Info-cyrus wrote:

> 

> Hi Bron,

> thank you for you reply.

> What do you mean with "get some version 10 binaries"?

> Do you mean "binaries from FreeBSD 10"?

> 
> Thank you

> 

> 

> Cyrus Home Page: http://www.cyrusimap.org/

> List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
> To Unsubscribe:

> https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus



--

  Bron Gondwana

  br...@fastmail.fm





Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
To Unsubscribe:
https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus

R: Re: R: Re: DBERROR: critical database situation

[absolutely_free--- via Info-cyrus]

After deleting /var/imap/db/*, /var/imap/mailboxes.db and /var/imap/deliver.db, 
it rans fine for about 20 minutes, and after:

Jan  4 11:58:41 mail lmtpunix[60214]: DBERROR db5: pthread suspend failed: 
Invalid argument
Jan  4 11:58:41 mail lmtpunix[60214]: DBERROR db5: BDB0061 PANIC: Invalid 
argument
Jan  4 11:58:41 mail lmtpunix[60214]: DBERROR: critical database situation
Jan  4 11:58:41 mail lmtpunix[60215]: DBERROR db5: BDB0060 PANIC: fatal region 
error detected; run recovery
Jan  4 11:58:41 mail lmtpunix[60215]: DBERROR: critical database situation
Jan  4 11:58:41 mail master[60046]: service lmtpunix pid 60215 in READY state: 
terminated abnormally
Jan  4 11:58:41 mail lmtpunix[60217]: DBERROR db5: BDB0060 PANIC: fatal region 
error detected; run recovery
Jan  4 11:58:41 mail lmtpunix[60217]: DBERROR: critical database situation
Jan  4 11:58:41 mail master[60046]: service lmtpunix pid 60217 in READY state: 
terminated abnormally
Jan  4 11:58:41 mail lmtpunix[60218]: DBERROR db5: BDB0060 PANIC: fatal region 
error detected; run recovery
Jan  4 11:58:41 mail lmtpunix[60218]: DBERROR: critical database situation
Jan  4 11:58:41 mail master[60046]: service lmtpunix pid 60218 in READY state: 
terminated abnormally
Jan  4 11:58:41 mail lmtpunix[60219]: DBERROR db5: BDB0060 PANIC: fatal region 
error detected; run recovery
Jan  4 11:58:41 mail lmtpunix[60219]: DBERROR: critical database situation
Jan  4 11:58:41 mail master[60046]: service lmtpunix pid 60219 in READY state: 
terminated abnormally
Jan  4 11:58:41 mail lmtpunix[60220]: DBERROR db5: BDB0060 PANIC: fatal region 
error detected; run recovery
Jan  4 11:58:41 mail lmtpunix[60220]: DBERROR: critical database situation
Jan  4 11:58:41 mail master[60046]: service lmtpunix pid 60220 in READY state: 
terminated abnormally
Jan  4 11:58:41 mail lmtpunix[60221]: DBERROR db5: BDB0060 PANIC: fatal region 
error detected; run recovery
Jan  4 11:58:41 mail lmtpunix[60221]: DBERROR: critical database situation
Jan  4 11:58:41 mail master[60046]: service lmtpunix pid 60221 in READY state: 
terminated abnormally


I am wondering what is my best option?
Upgrade to 2.4 (at least)?

Thank you


>Messaggio originale
>Da: "Niels Dettenbach" 
>Data: 04/01/2017 11.28
>A: , "absolutely_f...@libero.it"

>Ogg: Re: R: Re: DBERROR: critical database situation
>
>Am Mittwoch, 4. Januar 2017, 11:18:42 CET schrieb absolutely_free--- via 
Info-
>cyrus:
>> ./tls_sessions.db: Berkeley DB (Btree, version 9, little-endian)
>> ./deliver.db: Berkeley DB (Btree, version 9, little-endian)
>> 
>> So, I can convert tls_sessions and deliver db to skiplist format, right?
>> How can I determine which database is giving me "DBERROR: critical database
>> situation"?
>
>As far as i remember, it is uncritical to just delete both files, without 
>loosing "practical" data. tls_sessions just held details to ("running") TLS 
>Sessions and deliver.db avoids duplicates if i remember correctly.
>
>Stop cyrus - do a backup of delliver.db and tls_sessions.db (or just "Move 
it 
>out of the way) for security (but i'm pretty shure that you can delete it) 
or 
>try to just delete it and restart. 
>
>After that try to run reconstruct -f to re-generate any indize files etc. 
>within the mailboxes itself.
>
>If that not helps, come back again. ß)
>
>hth a bit,
>best regards and good luck,
>
>Niels.
>
>
>-- 
> ---
> Niels Dettenbach
> Syndicat IT & Internet
> http://www.syndicat.com
> PGP: https://syndicat.com/pub_key.asc
> ---
> 
>
>
>
>



Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
To Unsubscribe:
https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus

Re: R: Re: DBERROR: critical database situation

[Niels Dettenbach via Info-cyrus]

Am Mittwoch, 4. Januar 2017, 11:18:42 CET schrieb absolutely_free--- via Info-
cyrus:
> ./tls_sessions.db: Berkeley DB (Btree, version 9, little-endian)
> ./deliver.db: Berkeley DB (Btree, version 9, little-endian)
> 
> So, I can convert tls_sessions and deliver db to skiplist format, right?
> How can I determine which database is giving me "DBERROR: critical database
> situation"?

As far as i remember, it is uncritical to just delete both files, without 
loosing "practical" data. tls_sessions just held details to ("running") TLS 
Sessions and deliver.db avoids duplicates if i remember correctly.

Stop cyrus - do a backup of delliver.db and tls_sessions.db (or just "Move it 
out of the way) for security (but i'm pretty shure that you can delete it) or 
try to just delete it and restart. 

After that try to run reconstruct -f to re-generate any indize files etc. 
within the mailboxes itself.

If that not helps, come back again. ß)

hth a bit,
best regards and good luck,

Niels.


-- 
 ---
 Niels Dettenbach
 Syndicat IT & Internet
 http://www.syndicat.com
 PGP: https://syndicat.com/pub_key.asc
 ---
 





signature.asc
Description: This is a digitally signed message part.

Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
To Unsubscribe:
https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus

R: Re: DBERROR: critical database situation

[absolutely_free--- via Info-cyrus]

Hi Bron,thank you for you reply.What do you mean with "get some version 10 
binaries"?Do you mean "binaries from FreeBSD 10"?
Thank you


Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
To Unsubscribe:
https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus

R: Re: DBERROR: critical database situation

[absolutely_free--- via Info-cyrus]

Hi Niels,

thank you for your reply.
I am using cyrus from sources (ports).

root@mail:/var/imap# find . -name "*.db" -exec file '{}' \;
./mailboxes.db: Cyrus skiplist DB
./annotations.db: Cyrus skiplist DB
./db.backup1/annotations.db: Cyrus skiplist DB
./db.backup1/mailboxes.db: Cyrus skiplist DB
./tls_sessions.db: Berkeley DB (Btree, version 9, little-endian)
./db.backup2/annotations.db: Cyrus skiplist DB
./db.backup2/mailboxes.db: Cyrus skiplist DB
./deliver.db: Berkeley DB (Btree, version 9, little-endian)

So, I can convert tls_sessions and deliver db to skiplist format, right?
How can I determine which database is giving me "DBERROR: critical database 
situation"?

Thank you


Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
To Unsubscribe:
https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus

Re: DBERROR: critical database situation

[Bron Gondwana via Info-cyrus]

2.4 was releasted in 2010, it's 2017.  We advise not to run Berkeley DB
  (even on 2.3.19), because it doesn't upgrade very nicely.


I would advise that you get some version 10 binaries and use cvt_cyrusdb
to convert all your berkeley databases to skiplist. Skiplist in 2.3.19
is rock solid.  You'll need to update the config as well, but the
default for every database type in 2.3.19 is skiplist, so it's just a
matter of removing some lines from imapd.conf.


Regards,



Bron.



On Wed, 4 Jan 2017, at 19:45, absolutely_free--- via Info-cyrus wrote:

> 

> Hi,

> I am using cyrus-imapd23-2.3.19_2 on FreeBSD.

> After BSD upgrade (from 10 to 11) I get problems with cyrus.

> I get this kind of errors on:

> 

> Jan  4 09:27:31 mail imaps[65141]: DBERROR db5: pthread suspend
> failed: Invalid argument
> Jan  4 09:27:31 mail imaps[65141]: DBERROR db5: BDB0061 PANIC: Invalid
> argument
> Jan  4 09:27:31 mail imaps[65141]: DBERROR: critical database
> situation
> Jan  4 09:27:31 mail imaps[65140]: DBERROR db5: BDB0060 PANIC: fatal
> region error detected; run recovery
> Jan  4 09:27:31 mail imaps[65140]: DBERROR: critical database
> situation
> Jan  4 09:27:38 mail imaps[65142]: DBERROR db5: BDB0060 PANIC: fatal
> region error detected; run recovery
> Jan  4 09:27:38 mail imaps[65142]: DBERROR: critical database
> situation
> Jan  4 09:27:38 mail master[65081]: service imaps pid 65142 in READY
> state: terminated abnormally
> Jan  4 09:27:38 mail imaps[65143]: DBERROR db5: BDB0060 PANIC: fatal
> region error detected; run recovery
> Jan  4 09:27:38 mail imaps[65143]: DBERROR: critical database
> situation
> Jan  4 09:27:38 mail master[65081]: service imaps pid 65143 in READY
> state: terminated abnormally
> 

> So I stopped imapd service, and ran /usr/local/cyrus/bin/ctl_cyrusdb
> -r as cyrus user.
> 

> Rebuild went fine: 

> 

> Jan  4 09:36:17 mail ctl_cyrusdb[62332]: recovering cyrus databases

> Jan  4 09:36:17 mail ctl_cyrusdb[62332]: done recovering cyrus
> databases
> 

> and I also checked that just after ctl_cyrusdb command, I was able to
> dump mailboxes.db content with ctl_mboxlist -d
> 

> After few minutes, I get same errors, and ctl_mboxlist -d returns
> nothing:
> 

> cyrus@mail:/root$ /usr/local/cyrus/bin/ctl_cyrusdb -r

> cyrus@mail:/root$ 

> 

> Yesterday I tried to:

> 

> stop services

> remove and recreate /var/imap folder

> run reconstruct

> 

> but it seems I got no stable solution

> 

> Can you help me to solve this problem?

> Thank you very much

> 

> This is my imapd.conf:

> 

> root@mail:/usr/local/etc# grep -v ^# imapd.conf |grep -v ^$

> configdirectory: /var/imap

> partition-default: /var/spool/imap

> allowapop: 0

> unixhierarchysep: no

> altnamespace: no

> allowanonymouslogin: no

> allowplaintext: yes

> quotawarn: 90

> timeout: 30

> imapidlepoll: 60

> poptimeout: 10

> popminpoll: 0

> admins: root cyrus

> defaultacl: anyone lrs

> duplicatesuppression: no

> sievedir: /var/imap/sieve

> postmaster: postmaster

> sieve_maxscriptsize: 32

> sieve_maxscripts: 5

> duplicate_db: berkeley

> mboxlist_db: skiplist

> ptscache_db: berkeley

> seenstate_db: skiplist

> sasl_pwcheck_method: saslauthd

> sasl_mech_list: plain

> tls_cert_file: /etc/certs/ssl.crt/server.crt

> tls_key_file: /etc/certs/ssl.key/server.key

> tls_ca_file:  /etc/certs/ssl.crt/gd_bundle-g2-g1.crt

> tls_ca_path: /etc/certs/ssl.crt

> notifysocket: /var/imap/socket/notify

> 

> And cyrus.conf

> 

> root@mail:/usr/local/etc# grep -v ^# cyrus.conf |grep -v ^$
> START {

>   # do not delete this entry!

>   recover   cmd="ctl_cyrusdb -r"

>   # this is only necessary if using idled for IMAP IDLE

> }

> SERVICES {

>   # add or remove based on preferences

>   imap  cmd="imapd" listen="127.0.0.1:imap" prefork=1

>   imaps cmd="imapd -s" listen="imaps" prefork=0

>   #pop3 cmd="pop3d" listen="pop3" prefork=0

>   pop3s cmd="pop3d -s" listen="pop3s" prefork=0

>   sieve cmd="timsieved" listen="sieve" prefork=0

>   # these are only necessary if receiving/exporting usenet via NNTP

>   # at least one LMTP is required for delivery

>   lmtpunix  cmd="lmtpd" listen="/var/imap/socket/lmtp" prefork=0

>   # this is required if using notifications

> }

> EVENTS {

>   # this is required

>   checkpointcmd="ctl_cyrusdb -c" period=30

>   # this is only necessary if using duplicate delivery suppression,

>   # Sieve or NNTP

>   delprune  c

Re: DBERROR: critical database situation

[Niels Dettenbach via Info-cyrus]

Am Mittwoch, 4. Januar 2017, 09:45:47 CET schrieb absolutely_free--- via Info-
cyrus:
> Hi,
> I am using cyrus-imapd23-2.3.19_2 on FreeBSD.
> After BSD upgrade (from 10 to 11) I get problems with cyrus.
> I get this kind of errors on:
> 
> Jan  4 09:27:31 mail imaps[65141]: DBERROR db5: pthread suspend failed:
> Invalid argument Jan  4 09:27:31 mail imaps[65141]: DBERROR db5: BDB0061
> PANIC: Invalid argument Jan  4 09:27:31 mail imaps[65141]: DBERROR:
> critical database situation Jan  4 09:27:31 mail imaps[65140]: DBERROR db5:
> BDB0060 PANIC: fatal region error detected; run recovery Jan  4 09:27:31
> mail imaps[65140]: DBERROR: critical database situation Jan  4 09:27:38
> mail imaps[65142]: DBERROR db5: BDB0060 PANIC: fatal region error detected;
> run recovery Jan  4 09:27:38 mail imaps[65142]: DBERROR: critical database
> situation Jan  4 09:27:38 mail master[65081]: service imaps pid 65142 in
> READY state: terminated abnormally Jan  4 09:27:38 mail imaps[65143]:
> DBERROR db5: BDB0060 PANIC: fatal region error detected; run recovery Jan 
> 4 09:27:38 mail imaps[65143]: DBERROR: critical database situation Jan  4
> 09:27:38 mail master[65081]: service imaps pid 65143 in READY state:
> terminated abnormally

Just to clearify here: it is important to follow the upgrade procedure from 
cyrus:
https://www.cyrusimap.org/docs/cyrus-imapd/2.4.0/install-upgrade.php

and to export/reimport any data during db version changes / upgrades within 
the used cyrus builds (export before - delete db and and reimport after).

see i.e:
https://lists.andrew.cmu.edu/pipermail/info-cyrus/2015-August/038316.html
https://www.banquise.org/software/how-to-recover-from-cyrus-when-you-have-some-db-errors/
 (Linux, but same thing...)


Another thing often required in such a situation is to remove :

rm -f /var/lib/cyrus/deliver.db
rm -f /var/lib/cyrus/tls_sessions.db

to avoid the existence of incompatible database files.

If that doesn't help, a bug in your build may be a reason. Did you build the 
software from sources / ports or installed binaries?

hth a bit,

Niels.

-- 
 ---
 Niels Dettenbach
 Syndicat IT & Internet
 http://www.syndicat.com
 PGP: https://syndicat.com/pub_key.asc
 ---
 





signature.asc
Description: This is a digitally signed message part.

Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
To Unsubscribe:
https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus

DBERROR: critical database situation

[absolutely_free--- via Info-cyrus]

Hi,I am using cyrus-imapd23-2.3.19_2 on FreeBSD.After BSD upgrade (from 10 to 
11) I get problems with cyrus.I get this kind of errors on:
Jan  4 09:27:31 mail imaps[65141]: DBERROR db5: pthread suspend failed: Invalid 
argumentJan  4 09:27:31 mail imaps[65141]: DBERROR db5: BDB0061 PANIC: Invalid 
argumentJan  4 09:27:31 mail imaps[65141]: DBERROR: critical database 
situationJan  4 09:27:31 mail imaps[65140]: DBERROR db5: BDB0060 PANIC: fatal 
region error detected; run recoveryJan  4 09:27:31 mail imaps[65140]: DBERROR: 
critical database situationJan  4 09:27:38 mail imaps[65142]: DBERROR db5: 
BDB0060 PANIC: fatal region error detected; run recoveryJan  4 09:27:38 mail 
imaps[65142]: DBERROR: critical database situationJan  4 09:27:38 mail 
master[65081]: service imaps pid 65142 in READY state: terminated abnormallyJan 
 4 09:27:38 mail imaps[65143]: DBERROR db5: BDB0060 PANIC: fatal region error 
detected; run recoveryJan  4 09:27:38 mail imaps[65143]: DBERROR: critical 
database situationJan  4 09:27:38 mail master[65081]: service imaps pid 65143 
in READY state: terminated abnormally
So I stopped imapd service, and ran /usr/local/cyrus/bin/ctl_cyrusdb -r as 
cyrus user.
Rebuild went fine: 
Jan  4 09:36:17 mail ctl_cyrusdb[62332]: recovering cyrus databasesJan  4 
09:36:17 mail ctl_cyrusdb[62332]: done recovering cyrus databases
and I also checked that just after ctl_cyrusdb command, I was able to dump 
mailboxes.db content with ctl_mboxlist -d
After few minutes, I get same errors, and ctl_mboxlist -d returns nothing:
cyrus@mail:/root$ /usr/local/cyrus/bin/ctl_cyrusdb -rcyrus@mail:/root$ 
Yesterday I tried to:
stop servicesremove and recreate /var/imap folderrun reconstruct
but it seems I got no stable solution
Can you help me to solve this problem?Thank you very much
This is my imapd.conf:
root@mail:/usr/local/etc# grep -v ^# imapd.conf |grep -v ^$configdirectory: 
/var/imappartition-default: /var/spool/imapallowapop: 0unixhierarchysep: 
noaltnamespace: noallowanonymouslogin: noallowplaintext: yesquotawarn: 
90timeout: 30imapidlepoll: 60poptimeout: 10popminpoll: 0admins: root 
cyrusdefaultacl: anyone lrsduplicatesuppression: nosievedir: 
/var/imap/sievepostmaster: postmastersieve_maxscriptsize: 32sieve_maxscripts: 
5duplicate_db: berkeleymboxlist_db: skiplistptscache_db: berkeleyseenstate_db: 
skiplistsasl_pwcheck_method: saslauthdsasl_mech_list: plaintls_cert_file: 
/etc/certs/ssl.crt/server.crttls_key_file: 
/etc/certs/ssl.key/server.keytls_ca_file:  
/etc/certs/ssl.crt/gd_bundle-g2-g1.crttls_ca_path: 
/etc/certs/ssl.crtnotifysocket: /var/imap/socket/notify
And cyrus.conf
root@mail:/usr/local/etc# grep -v ^# cyrus.conf |grep -v ^$  START {  # 
do not delete this entry!  recover   cmd="ctl_cyrusdb -r"  # this is only 
necessary if using idled for IMAP IDLE}SERVICES {  # add or remove based on 
preferences  imap  cmd="imapd" listen="127.0.0.1:imap" prefork=1  imaps 
cmd="imapd -s" listen="imaps" prefork=0  #pop3 cmd="pop3d" 
listen="pop3" prefork=0  pop3s cmd="pop3d -s" listen="pop3s" prefork=0  
sieve cmd="timsieved" listen="sieve" prefork=0  # these are only 
necessary if receiving/exporting usenet via NNTP  # at least one LMTP is 
required for delivery  lmtpunix  cmd="lmtpd" listen="/var/imap/socket/lmtp" 
prefork=0  # this is required if using notifications}EVENTS {  # this is 
required  checkpointcmd="ctl_cyrusdb -c" period=30  # this is only 
necessary if using duplicate delivery suppression,  # Sieve or NNTP  delprune   
   cmd="cyr_expire -E 3" at=0400  # this is only necessary if caching TLS 
sessions  tlsprune  cmd="tls_prune" at=0400}





Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
To Unsubscribe:
https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus

RE: DBERROR db4: Lock table is out of available locker entries

[Dudi Finkel]

Hi,

Thank you for the reply.

Sometimes I see in maillog the following errors:
imap[31724]: SQUAT failed to open index file
imap[31724]: SQUAT failed
And also:
master[24699]: process 19488 exited, signaled to death by 11
master[24699]: service imap pid 19488 in BUSY state: terminated abnormally

Do you think that these errors are related to the lockers problem?

What will happen to the current mailboxes if I use skiplist instead of 
berkeley_db (for annotation_db and mboxlist_db)?

In case I continue to use berkelery_db, do you think that upgrade to db4 should 
help resolving the locker problem?

Thank you,
Dudi 

-Original Message-
From: Sebastian Hagedorn [mailto:haged...@uni-koeln.de] 
Sent: Thursday, July 30, 2015 11:56 AM
To: Dudi Finkel
Cc: info-cyrus@lists.andrew.cmu.edu
Subject: Re: DBERROR db4: Lock table is out of available locker entries

Hi,

--On 30. Juli 2015 01:17:29 +0300 Dudi Finkel 
wrote:

> db4-4.3.29
>
> The number of lockers was growing for more than a week
>
> Why this is happening?
>
> How can I fix it?
>
> How can I reproduce it?

general consensus is to just get rid of BerkeleyDB. You can use skiplist 
instead. Your version of Cyrus is also very outdated. You should seriously 
consider an upgrade.
-- 
.:.Sebastian Hagedorn - Weyertal 121 (Gebäude 133), Zimmer 2.02.:.
 .:.Regionales Rechenzentrum (RRZK).:.
   .:.Universität zu Köln / Cologne University - ✆ +49-221-470-89578.:.


Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
To Unsubscribe:
https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus

Re: DBERROR db4: Lock table is out of available locker entries

[Sebastian Hagedorn]

Hi,

--On 30. Juli 2015 01:17:29 +0300 Dudi Finkel  
wrote:



db4-4.3.29

The number of lockers was growing for more than a week

Why this is happening?

How can I fix it?

How can I reproduce it?


general consensus is to just get rid of BerkeleyDB. You can use skiplist 
instead. Your version of Cyrus is also very outdated. You should seriously 
consider an upgrade.

--
   .:.Sebastian Hagedorn - Weyertal 121 (Gebäude 133), Zimmer 2.02.:.
.:.Regionales Rechenzentrum (RRZK).:.
  .:.Universität zu Köln / Cologne University - ✆ +49-221-470-89578.:.

pgpeo8NVZ31xc.pgp
Description: PGP signature

Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
To Unsubscribe:
https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus

DBERROR db4: Lock table is out of available locker entries

[Dudi Finkel]

Hello,

 

I'm using:

cyrus-imapd-2.3.7

db4-4.3.29

The operating system is Linux RedHat 5.3

 

Sometimes, the number of lockers increases until no more lockers are left.

I searched for lock in the maillog file (grep lock mailog):

 

imap[12470]: DBMSG: 25913 lockers

imap[7497]: DBMSG: 26052 lockers

imap[5295]: DBMSG: 26528 lockers

imap[5305]: DBMSG: 26552 lockers

.

.

.

.

imap[13438]: DBMSG: 49823 lockers

imap[13357]: DBMSG: 49910 lockers

imap[25643]: DBMSG: 49955 lockers

imap[10874]: DBERROR db4: Lock table is out of available locker entries

imap[10875]: DBERROR db4: Lock table is out of available locker entries

imap[10876]: DBERROR db4: Lock table is out of available locker entries

 

Eventually I see the following errors:

 

imap[16719]: DBERROR db4: PANIC: fatal region error detected; run recovery

imap[16719]: DBERROR: critical database situation

master[22961]: process 16719 exited, status 75

master[22961]: service imap pid 16719 in READY state: terminated abnormally

master[16720]: about to exec /usr/lib/cyrus-imapd/imapd

 

 

The number of lockers was growing for more than a week

Why this is happening?

How can I fix it?

How can I reproduce it?

 

Thank you,

Dudi


Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
To Unsubscribe:
https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus

Re: Mystery cyrus/lmtp and cyrus/imap DBERROR log entries

[Andy Dorman]

On 03/16/2015 05:52 PM, Bron Gondwana wrote:
> On Tue, Mar 17, 2015, at 02:49 AM, Andy Dorman wrote:
>> It would be nice to not have to garbage up the logs with them though...I
>> will do some investigating in Debian to see if there is any traction for
>> a Debian package compiled without BDB.
>
> FYI, the branch which will become Cyrus 3.0 has had BDB support ripped out 
> entirely, so you won't have to worry when that comes out :)
>

+1 That works for us.  Thanks.

-- 
Andy Dorman


Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
To Unsubscribe:
https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus

Re: Mystery cyrus/lmtp and cyrus/imap DBERROR log entries

[Bron Gondwana]

On Tue, Mar 17, 2015, at 02:49 AM, Andy Dorman wrote:
> It would be nice to not have to garbage up the logs with them though...I 
> will do some investigating in Debian to see if there is any traction for 
> a Debian package compiled without BDB.

FYI, the branch which will become Cyrus 3.0 has had BDB support ripped out 
entirely, so you won't have to worry when that comes out :)


-- 
  Bron Gondwana
  br...@fastmail.fm

Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
To Unsubscribe:
https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus

Re: Mystery cyrus/lmtp and cyrus/imap DBERROR log entries

[Andy Dorman]

On 03/16/2015 10:08 AM, Patrick Boutilier wrote:
> On 03/16/2015 11:57 AM, Andy Dorman wrote:
>> Hi, I am relatively new to Cyrus...we have been using it for many years,
>> but I have only recently been given the job of administering it.
>>
>> We are using the Debian Cyrus package, 2.4.17.  Everything as far as
>> mail storage and delivery from the user perspective is working great.
>>
>> However, I have noticed DBERROR log entries have been happening for
>> months (possibly longer, our detailed syslogs only go back 6 months).
>>
>> I am concerned that there might be a problem, but if not then I would
>> like to clean up the log entries.
>>
>> 2015-03-16T08:28:18.024064-05:00 yorick cyrus/lmtp[2219]: DBERROR db5:
>> /var/lib/cyrus/db/__db.001: No such file or directory
>> 2015-03-16T08:28:18.024159-05:00 yorick cyrus/lmtp[2219]: DBERROR:
>> dbenv->open '/var/lib/cyrus/db' failed: No such file or directory
>> 2015-03-16T08:28:18.024182-05:00 yorick cyrus/lmtp[2219]: DBERROR:
>> init() on berkeley
>> 2015-03-16T08:28:18.024211-05:00 yorick cyrus/lmtp[2219]: DBERROR:
>> reading /var/lib/cyrus/db/skipstamp, assuming the worst: No such file or
>> directory
>> 2015-03-16T08:28:18.024234-05:00 yorick cyrus/lmtp[2219]: executed
>>
>> 2015-03-16T09:15:20.607017-05:00 yorick cyrus/imap[3716]: DBERROR db5:
>> /var/lib/cyrus/db/__db.001: No such file or directory
>> 2015-03-16T09:15:20.607183-05:00 yorick cyrus/imap[3716]: DBERROR:
>> dbenv->open '/var/lib/cyrus/db' failed: No such file or directory
>> 2015-03-16T09:15:20.607227-05:00 yorick cyrus/imap[3716]: DBERROR:
>> init() on berkeley
>> 2015-03-16T09:15:20.607281-05:00 yorick cyrus/imap[3716]: DBERROR:
>> reading /var/lib/cyrus/db/skipstamp, assuming the worst: No such file or
>> directory
>> 2015-03-16T09:15:20.607334-05:00 yorick cyrus/imap[3716]: executed
>>
>> Based on the 3rd line of each block of errors this looks like a BDB
>> (berkeley db) problem...but I checked our imapd.conf and the previous
>> admin switched everything to skiplist in July 2010 as shown by the
>> snippet below from our imapd.conf.  FWIW, it appears he left one BDB
>> setting in place accidentally, but I would think that would not make a
>> difference since we no longer use BDB.
>>
>> - snippets from imapd.conf -
>> # Use skiplist everywhere
>> annotation_db: skiplist
>> ...
>> berkeley_cachesize: 1024
>> ...
>> # Use skiplist everywhere
>> annotation_db: skiplist
>> ...
>> # Set our quota properly
>> quota_db: skiplist
>> ...
>> # Use skiplist everywhere
>> statuscache_db: skiplist
>>
>> # Use skiplist everywhere
>> tlscache_db: skiplist
>>
>> # Use skiplist everywhere
>> userdeny_db: skiplist
>> - end snippets from imapd.conf -
>>
>> As far as the /var/lib/cyrus/ directory, there is indeed no db
>> sub-directory, but everything else appears to be in order as far as I
>> can tell.
>>
>> drwxr-x--- 12 cyrus mail   4096 Mar 16 09:37 .
>> drwxr-xr-x 49 root  root   4096 Oct 20 14:54 ..
>> -rw---  1 cyrus mail144 Mar 16 09:37 annotations.db
>> drwx--  2 cyrus mail   4096 Mar 16 09:11 db.backup1
>> drwx--  2 cyrus mail   4096 Mar 16 08:41 db.backup2
>> -rw---  1 cyrus mail 114220 Mar 16 09:37 deliver.db
>> drwx--  9 cyrus mail   4096 Feb 15 01:56 domain
>> drwx-- 29 cyrus mail   4096 Apr 27  2011 lock
>> drwx--  2 cyrus mail   4096 Jul 12  2010 log
>> -rw---  1 cyrus mail   9280 Mar 16 09:37 mailboxes.db
>> drwx--  2 cyrus mail   4096 Nov 15  2007 msg
>> drwx--  2 cyrus mail   4096 Nov 11 10:59 proc
>> drwx-- 28 cyrus mail   4096 Nov 15  2007 quota
>> -rw---  1 cyrus mail608 Mar 16 09:37 quotas.db
>> drwxr-x---  2 cyrus mail   4096 Sep 12  2008 socket
>> -rw---  1 cyrus mail144 Mar 16 09:37 statuscache.db
>> -rw---  1 cyrus mail144 Mar 16 09:37 tls_sessions.db
>> drwx-- 29 cyrus mail   4096 Sep 22  2009 user
>> -rw---  1 cyrus mail144 Mar 16 09:37 user_deny.db
>>
>>
>> So, my questions are:
>>
>> 1. Do we actually have a problem here?  If so, then I can certainly
>> create a db sub-directory for BDB to work in, but then I wonder why do
>> we need to if we are no longer using BDB?
>>
>> 2. If we do not have a problem, then what can I change in our
>> configuration to let cyrus know it no longer needs to worry with a db
>> sub-directory for BDB (assuming this IS a BDB issue of course)?
>&g

Re: Mystery cyrus/lmtp and cyrus/imap DBERROR log entries

[Patrick Boutilier]

On 03/16/2015 11:57 AM, Andy Dorman wrote:

Hi, I am relatively new to Cyrus...we have been using it for many years,
but I have only recently been given the job of administering it.

We are using the Debian Cyrus package, 2.4.17.  Everything as far as
mail storage and delivery from the user perspective is working great.

However, I have noticed DBERROR log entries have been happening for
months (possibly longer, our detailed syslogs only go back 6 months).

I am concerned that there might be a problem, but if not then I would
like to clean up the log entries.

2015-03-16T08:28:18.024064-05:00 yorick cyrus/lmtp[2219]: DBERROR db5:
/var/lib/cyrus/db/__db.001: No such file or directory
2015-03-16T08:28:18.024159-05:00 yorick cyrus/lmtp[2219]: DBERROR:
dbenv->open '/var/lib/cyrus/db' failed: No such file or directory
2015-03-16T08:28:18.024182-05:00 yorick cyrus/lmtp[2219]: DBERROR:
init() on berkeley
2015-03-16T08:28:18.024211-05:00 yorick cyrus/lmtp[2219]: DBERROR:
reading /var/lib/cyrus/db/skipstamp, assuming the worst: No such file or
directory
2015-03-16T08:28:18.024234-05:00 yorick cyrus/lmtp[2219]: executed

2015-03-16T09:15:20.607017-05:00 yorick cyrus/imap[3716]: DBERROR db5:
/var/lib/cyrus/db/__db.001: No such file or directory
2015-03-16T09:15:20.607183-05:00 yorick cyrus/imap[3716]: DBERROR:
dbenv->open '/var/lib/cyrus/db' failed: No such file or directory
2015-03-16T09:15:20.607227-05:00 yorick cyrus/imap[3716]: DBERROR:
init() on berkeley
2015-03-16T09:15:20.607281-05:00 yorick cyrus/imap[3716]: DBERROR:
reading /var/lib/cyrus/db/skipstamp, assuming the worst: No such file or
directory
2015-03-16T09:15:20.607334-05:00 yorick cyrus/imap[3716]: executed

Based on the 3rd line of each block of errors this looks like a BDB
(berkeley db) problem...but I checked our imapd.conf and the previous
admin switched everything to skiplist in July 2010 as shown by the
snippet below from our imapd.conf.  FWIW, it appears he left one BDB
setting in place accidentally, but I would think that would not make a
difference since we no longer use BDB.

- snippets from imapd.conf -
# Use skiplist everywhere
annotation_db: skiplist
...
berkeley_cachesize: 1024
...
# Use skiplist everywhere
annotation_db: skiplist
...
# Set our quota properly
quota_db: skiplist
...
# Use skiplist everywhere
statuscache_db: skiplist

# Use skiplist everywhere
tlscache_db: skiplist

# Use skiplist everywhere
userdeny_db: skiplist
- end snippets from imapd.conf -

As far as the /var/lib/cyrus/ directory, there is indeed no db
sub-directory, but everything else appears to be in order as far as I
can tell.

drwxr-x--- 12 cyrus mail   4096 Mar 16 09:37 .
drwxr-xr-x 49 root  root   4096 Oct 20 14:54 ..
-rw---  1 cyrus mail144 Mar 16 09:37 annotations.db
drwx--  2 cyrus mail   4096 Mar 16 09:11 db.backup1
drwx--  2 cyrus mail   4096 Mar 16 08:41 db.backup2
-rw---  1 cyrus mail 114220 Mar 16 09:37 deliver.db
drwx--  9 cyrus mail   4096 Feb 15 01:56 domain
drwx-- 29 cyrus mail   4096 Apr 27  2011 lock
drwx--  2 cyrus mail   4096 Jul 12  2010 log
-rw---  1 cyrus mail   9280 Mar 16 09:37 mailboxes.db
drwx--  2 cyrus mail   4096 Nov 15  2007 msg
drwx--  2 cyrus mail   4096 Nov 11 10:59 proc
drwx-- 28 cyrus mail   4096 Nov 15  2007 quota
-rw---  1 cyrus mail608 Mar 16 09:37 quotas.db
drwxr-x---  2 cyrus mail   4096 Sep 12  2008 socket
-rw---  1 cyrus mail144 Mar 16 09:37 statuscache.db
-rw---  1 cyrus mail144 Mar 16 09:37 tls_sessions.db
drwx-- 29 cyrus mail   4096 Sep 22  2009 user
-rw---  1 cyrus mail144 Mar 16 09:37 user_deny.db


So, my questions are:

1. Do we actually have a problem here?  If so, then I can certainly
create a db sub-directory for BDB to work in, but then I wonder why do
we need to if we are no longer using BDB?

2. If we do not have a problem, then what can I change in our
configuration to let cyrus know it no longer needs to worry with a db
sub-directory for BDB (assuming this IS a BDB issue of course)?

I have searched the mailing list archives, Googled for info and studied
the imapd.conf man pages and have not found an answer.  It would be
appreciated if anyone in this list knows what is going on or can at
least point me in the right direction.

Thanks,




I think you have to compile with --without-bdb to completely get rid of 
BDB. I doubt the Debian packages would be compiled in such a way.



<>
Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
To Unsubscribe:
https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus

Mystery cyrus/lmtp and cyrus/imap DBERROR log entries

[Andy Dorman]

Hi, I am relatively new to Cyrus...we have been using it for many years, 
but I have only recently been given the job of administering it.

We are using the Debian Cyrus package, 2.4.17.  Everything as far as 
mail storage and delivery from the user perspective is working great.

However, I have noticed DBERROR log entries have been happening for 
months (possibly longer, our detailed syslogs only go back 6 months).

I am concerned that there might be a problem, but if not then I would 
like to clean up the log entries.

2015-03-16T08:28:18.024064-05:00 yorick cyrus/lmtp[2219]: DBERROR db5: 
/var/lib/cyrus/db/__db.001: No such file or directory
2015-03-16T08:28:18.024159-05:00 yorick cyrus/lmtp[2219]: DBERROR: 
dbenv->open '/var/lib/cyrus/db' failed: No such file or directory
2015-03-16T08:28:18.024182-05:00 yorick cyrus/lmtp[2219]: DBERROR: 
init() on berkeley
2015-03-16T08:28:18.024211-05:00 yorick cyrus/lmtp[2219]: DBERROR: 
reading /var/lib/cyrus/db/skipstamp, assuming the worst: No such file or 
directory
2015-03-16T08:28:18.024234-05:00 yorick cyrus/lmtp[2219]: executed

2015-03-16T09:15:20.607017-05:00 yorick cyrus/imap[3716]: DBERROR db5: 
/var/lib/cyrus/db/__db.001: No such file or directory
2015-03-16T09:15:20.607183-05:00 yorick cyrus/imap[3716]: DBERROR: 
dbenv->open '/var/lib/cyrus/db' failed: No such file or directory
2015-03-16T09:15:20.607227-05:00 yorick cyrus/imap[3716]: DBERROR: 
init() on berkeley
2015-03-16T09:15:20.607281-05:00 yorick cyrus/imap[3716]: DBERROR: 
reading /var/lib/cyrus/db/skipstamp, assuming the worst: No such file or 
directory
2015-03-16T09:15:20.607334-05:00 yorick cyrus/imap[3716]: executed

Based on the 3rd line of each block of errors this looks like a BDB 
(berkeley db) problem...but I checked our imapd.conf and the previous 
admin switched everything to skiplist in July 2010 as shown by the 
snippet below from our imapd.conf.  FWIW, it appears he left one BDB 
setting in place accidentally, but I would think that would not make a 
difference since we no longer use BDB.

- snippets from imapd.conf -
# Use skiplist everywhere
annotation_db: skiplist
...
berkeley_cachesize: 1024
...
# Use skiplist everywhere
annotation_db: skiplist
...
# Set our quota properly
quota_db: skiplist
...
# Use skiplist everywhere
statuscache_db: skiplist

# Use skiplist everywhere
tlscache_db: skiplist

# Use skiplist everywhere
userdeny_db: skiplist
- end snippets from imapd.conf -

As far as the /var/lib/cyrus/ directory, there is indeed no db 
sub-directory, but everything else appears to be in order as far as I 
can tell.

drwxr-x--- 12 cyrus mail   4096 Mar 16 09:37 .
drwxr-xr-x 49 root  root   4096 Oct 20 14:54 ..
-rw---  1 cyrus mail144 Mar 16 09:37 annotations.db
drwx--  2 cyrus mail   4096 Mar 16 09:11 db.backup1
drwx--  2 cyrus mail   4096 Mar 16 08:41 db.backup2
-rw---  1 cyrus mail 114220 Mar 16 09:37 deliver.db
drwx--  9 cyrus mail   4096 Feb 15 01:56 domain
drwx-- 29 cyrus mail   4096 Apr 27  2011 lock
drwx--  2 cyrus mail   4096 Jul 12  2010 log
-rw---  1 cyrus mail   9280 Mar 16 09:37 mailboxes.db
drwx--  2 cyrus mail   4096 Nov 15  2007 msg
drwx--  2 cyrus mail   4096 Nov 11 10:59 proc
drwx-- 28 cyrus mail   4096 Nov 15  2007 quota
-rw---  1 cyrus mail608 Mar 16 09:37 quotas.db
drwxr-x---  2 cyrus mail   4096 Sep 12  2008 socket
-rw---  1 cyrus mail144 Mar 16 09:37 statuscache.db
-rw---  1 cyrus mail144 Mar 16 09:37 tls_sessions.db
drwx-- 29 cyrus mail   4096 Sep 22  2009 user
-rw---  1 cyrus mail144 Mar 16 09:37 user_deny.db


So, my questions are:

1. Do we actually have a problem here?  If so, then I can certainly 
create a db sub-directory for BDB to work in, but then I wonder why do 
we need to if we are no longer using BDB?

2. If we do not have a problem, then what can I change in our 
configuration to let cyrus know it no longer needs to worry with a db 
sub-directory for BDB (assuming this IS a BDB issue of course)?

I have searched the mailing list archives, Googled for info and studied 
the imapd.conf man pages and have not found an answer.  It would be 
appreciated if anyone in this list knows what is going on or can at 
least point me in the right direction.

Thanks,

-- 
Andy Dorman


Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
To Unsubscribe:
https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus

Re: DBERROR error fetching user.toto cyrusdb error

[Sabine GOUDARD]

Hi
Finally
I found the reason of this " DBERROR error fetching user.toto cyrusdb error"

I don't know why but when I deleted the mailbox toto
user.toto file in /var/lib/cyrus/quota directory wasn't deleted

I deleted it manually
then I created mailbox toto with rights and quota and all is good

Thanks for your help


Le 26/03/2013 16:15, Sabine GOUDARD a écrit :


Hello,
  
Last Saturday, my database shutdown


I restart my server, a "checkdisk" was done and all was ok
but only one mailbox was corrupted

I could open the mailbox, but I couldn't delete mail etc etc ...

All message for this mailbox were suspended with I/O Error

I managed to save /var/spool/cyrus/t/user/toto

Cyrus restarted without any error
I created user.toto with cyradm
and "sam user.toto cyrus all"
When I try to set quota
I have "setquota : System I/O error"

If I try to acess to mailbox
I have "DBERROR error fetching user.toto cyrusdb error" in syslog

But all the other boxes work without any error
What can I do ?
have you got any idea about how to solve this problem ?
I never had these errors and i'm afraid to broken more ...
I'm confused about the state of my database and i have no idea about 
how to solve this problem


Cyrus 2.2



*
**Sabine Goudard*
Service Informatique et Multimédia
Tél : 04 77 42 37 20

*Ecole Nationale Supérieure d’Architecture de Saint-Étienne*
1, rue Buisson BP 94
42003 Saint-Étienne Cedex 1
Fax : 04 77 42 35 40
http://www.st-etienne.archi.fr




Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
To Unsubscribe:
https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus

Re: DBERROR error fetching user.toto cyrusdb error

[Anthony Prades]

On 03/26/2013 04:15 PM, Sabine GOUDARD wrote:
>
> Hello,
>   
> Last Saturday, my database shutdown
>
> I restart my server, a "checkdisk" was done and all was ok
> but only one mailbox was corrupted
>
> I could open the mailbox, but I couldn't delete mail etc etc ...
>
> All message for this mailbox were suspended with I/O Error
>
> I managed to save /var/spool/cyrus/t/user/toto
>
> Cyrus restarted without any error
> I created user.toto with cyradm
> and "sam user.toto cyrus all"
> When I try to set quota
> I have "setquota : System I/O error"
>
Hi,

check file system rights on:
- /var/lib/cyrus/quota/t/*toto*
- /var/lib/cyrus/user/t/toto*
- /var/spool/cyrus/t/user/toto/*

Anthony

> If I try to acess to mailbox
> I have "DBERROR error fetching user.toto cyrusdb error" in syslog
>
> But all the other boxes work without any error
> What can I do ?
> have you got any idea about how to solve this problem ?
> I never had these errors and i'm afraid to broken more ...
> I'm confused about the state of my database and i have no idea about 
> how to solve this problem
>
> Cyrus 2.2
>
> 
>
> *
> **Sabine Goudard*
> Service Informatique et Multimédia
> Tél : 04 77 42 37 20
>
> *Ecole Nationale Supérieure d’Architecture de Saint-Étienne*
> 1, rue Buisson BP 94
> 42003 Saint-Étienne Cedex 1
> Fax : 04 77 42 35 40
> http://www.st-etienne.archi.fr
>
>
>
> 
> Cyrus Home Page: http://www.cyrusimap.org/
> List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
> To Unsubscribe:
> https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus


Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
To Unsubscribe:
https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus

DBERROR: dbenv->open '/var/lib/cyrus/db' failed: Invalid argument

[David Touzeau]

Dear

 

I encounter these errors.

Did anyone have tips to resolve this issue ?

 
Aug 26 10:33:47 mail cyrus/ctl_cyrusdb[13465]: DBERROR db4:
DB_ENV->log_flush: LSN of 1/427823 past current end-of-log of 1/67803 
Aug 26 10:33:47 mail cyrus/ctl_cyrusdb[13465]: DBERROR db4: Database
environment corrupt; the wrong log files may have been removed or
incompatible database files imported from another environment 
Aug 26 10:33:47 mail cyrus/ctl_cyrusdb[13465]: DBERROR
db4: /var/lib/cyrus/tls_sessions.db: unable to flush page: 0 
Aug 26 10:33:47 mail cyrus/ctl_cyrusdb[13465]: DBERROR db4:
txn_checkpoint: failed to flush the buffer cache Invalid argument 
Aug 26 10:33:47 mail cyrus/ctl_cyrusdb[13465]: DBERROR: couldn't
checkpoint: Invalid argument 

Aug 26 10:00:54 mail cyrus/lmtpunix[1]: DBERROR: init() on berkeley 
Aug 26 10:00:54 mail cyrus/lmtpunix[1]: DBERROR db4: environment not
yet opened 
Aug 26 10:00:54 mail cyrus/lmtpunix[1]: DBERROR:
opening /var/lib/cyrus/deliver.db: Invalid argument 
Aug 26 10:00:54 mail cyrus/lmtpunix[1]: DBERROR:
opening /var/lib/cyrus/deliver.db: cyrusdb error 
Aug 26 10:00:54 mail cyrus/lmtpunix[13334]: DBERROR db4: log file size
must be >= log buffer size * 4 
Aug 26 10:00:54 mail cyrus/lmtpunix[13334]: DBERROR: dbenv->open
'/var/lib/cyrus/db' failed: Invalid argument 



Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/

DBERROR: dbenv->open '/var/lib/cyrus/db' failed: Invalid argument

[da...@touzeau.eu]

Dear
 
I encounter these errors.
Did anyone have tips to resolv this issue ?
 
Aug 26 10:33:47 mail cyrus/ctl_cyrusdb[13465]: DBERROR db4: DB_ENV->log_flush:
LSN of 1/427823 past current end-of-log of 1/67803
Aug 26 10:33:47 mail cyrus/ctl_cyrusdb[13465]: DBERROR db4: Database environment
corrupt; the wrong log files may have been removed or incompatible database
files imported from another environment
Aug 26 10:33:47 mail cyrus/ctl_cyrusdb[13465]: DBERROR db4:
/var/lib/cyrus/tls_sessions.db: unable to flush page: 0
Aug 26 10:33:47 mail cyrus/ctl_cyrusdb[13465]: DBERROR db4: txn_checkpoint:
failed to flush the buffer cache Invalid argument
Aug 26 10:33:47 mail cyrus/ctl_cyrusdb[13465]: DBERROR: couldn't checkpoint:
Invalid argument

Aug 26 10:00:54 mail cyrus/lmtpunix[1]: DBERROR: init() on berkeley
Aug 26 10:00:54 mail cyrus/lmtpunix[1]: DBERROR db4: environment not yet
opened
Aug 26 10:00:54 mail cyrus/lmtpunix[1]: DBERROR: opening
/var/lib/cyrus/deliver.db: Invalid argument
Aug 26 10:00:54 mail cyrus/lmtpunix[1]: DBERROR: opening
/var/lib/cyrus/deliver.db: cyrusdb error
Aug 26 10:00:54 mail cyrus/lmtpunix[13334]: DBERROR db4: log file size must be
>= log buffer size * 4
Aug 26 10:00:54 mail cyrus/lmtpunix[13334]: DBERROR: dbenv->open
'/var/lib/cyrus/db' failed: Invalid argument
viki [http://forum.artica.fr/memberlist.php?mode=viewprofileu=2003]
 Posts:13Joined:Mon Jan 31, 2011 6:03 pmUser Flagged:No [Flag
[http://forum.artica.fr/antispam/index.php?mode=user_flagu=2003p=20737] ]Artica
servers number:1Linux System:DebianTechnical skills:A Linux System Administrator
 [http://forum.artica.fr/ucp.php?i=pmmode=composeaction=quotepostp=20737]
Private message
[http://forum.artica.fr/ucp.php?i=pmmode=composeaction=quotepostp=20737]
 [http://forum.artica.fr/ucp.php?i=pmmode=composeaction=quotepostp=20737]
 [http://forum.artica.fr/memberlist.php?mode=emailu=2003] E-mail viki
[http://forum.artica.fr/memberlist.php?mode=emailu=2003]
 [http://forum.artica.fr/memberlist.php?mode=emailu=2003]
Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/

Re: what is causing DBERROR?

[IMAP List Administration]

On 12/06/2010 07:45 AM, Antoine Jacoutot wrote:
> On Mon, 06 Dec 2010 02:55:57 +0100, IMAP List Administration  
> wrote:
>> after upgrading my OpenBSD server from OBSD V4.7 --> V4.8, which meant going
>> from cyrus-imapd-2.3.16 to cyrus-imapd-2.3.16p0, we now get the
>> following errors
>> in syslog when cyrus is started:
> 
> Just cd under /var/imap or /var/spool/imap before starting the cyrus master.
> In 4.9 there will be an rc script that will take care of it.
> 
thanks. that sorted it out.

Rob Urban

Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/

Re: what is causing DBERROR?

[Antoine Jacoutot]

 On Mon, 06 Dec 2010 02:55:57 +0100, IMAP List Administration 
  wrote:
> Hi Folks,
>
> after upgrading my OpenBSD server from OBSD V4.7 --> V4.8, which 
> meant going
> from cyrus-imapd-2.3.16 to cyrus-imapd-2.3.16p0, we now get the
> following errors
> in syslog when cyrus is started:

 Just cd under /var/imap or /var/spool/imap before starting the cyrus 
 master.
 In 4.9 there will be an rc script that will take care of it.

> imapd/master[31550]: about to exec 
> /usr/local/libexec/cyrus-imapd/ctl_cyrusdb
> imapd/ctl_cyrusdb[31550]: checkpointing cyrus databases
> imapd/ctl_cyrusdb[31550]: archiving database file: 
> /var/imap/annotations.db
> imapd/ctl_cyrusdb[31550]: DBERROR db4: no absolute path for the 
> current
> directory: Permission denied
> imapd/ctl_cyrusdb[31550]: DBERROR: error listing log files: 
> Permission denied
> imapd/ctl_cyrusdb[31550]: DBERROR: archive /var/imap/db: cyrusdb 
> error
> imapd/ctl_cyrusdb[31550]: DBERROR db4: no absolute path for the 
> current
> directory: Permission denied
> imapd/ctl_cyrusdb[31550]: DBERROR: error listing log files: 
> Permission denied
> imapd/ctl_cyrusdb[31550]: DBERROR: archive /var/imap/db: cyrusdb 
> error
> imapd/ctl_cyrusdb[31550]: archiving database file: 
> /var/imap/mailboxes.db
> imapd/ctl_cyrusdb[31550]: DBERROR db4: no absolute path for the 
> current
> directory: Permission denied
> imapd/ctl_cyrusdb[31550]: DBERROR: error listing log files: 
> Permission denied
> imapd/ctl_cyrusdb[31550]: DBERROR: archive /var/imap/db: cyrusdb 
> error
> imapd/ctl_cyrusdb[31550]: DBERROR db4: no absolute path for the 
> current
> directory: Permission denied
> imapd/ctl_cyrusdb[31550]: DBERROR: error listing log files: 
> Permission denied
> imapd/ctl_cyrusdb[31550]: DBERROR: archive /var/imap/db: cyrusdb 
> error
> imapd/ctl_cyrusdb[31550]: done checkpointing cyrus databases
> imapd/master[14035]: process 31550 exited, status 1
>
> In spite of all these error messages, the server seems to work...
>
> Does anyone know what is causing this?
>
> thanks,
>
> Rob Urban
> 
> Cyrus Home Page: http://www.cyrusimap.org/
> List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/

-- 
 Antoine

Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/

what is causing DBERROR?

[IMAP List Administration]

Hi Folks,

after upgrading my OpenBSD server from OBSD V4.7 --> V4.8, which meant going
from cyrus-imapd-2.3.16 to cyrus-imapd-2.3.16p0, we now get the following errors
in syslog when cyrus is started:

imapd/master[31550]: about to exec /usr/local/libexec/cyrus-imapd/ctl_cyrusdb
imapd/ctl_cyrusdb[31550]: checkpointing cyrus databases
imapd/ctl_cyrusdb[31550]: archiving database file: /var/imap/annotations.db
imapd/ctl_cyrusdb[31550]: DBERROR db4: no absolute path for the current
directory: Permission denied
imapd/ctl_cyrusdb[31550]: DBERROR: error listing log files: Permission denied
imapd/ctl_cyrusdb[31550]: DBERROR: archive /var/imap/db: cyrusdb error
imapd/ctl_cyrusdb[31550]: DBERROR db4: no absolute path for the current
directory: Permission denied
imapd/ctl_cyrusdb[31550]: DBERROR: error listing log files: Permission denied
imapd/ctl_cyrusdb[31550]: DBERROR: archive /var/imap/db: cyrusdb error
imapd/ctl_cyrusdb[31550]: archiving database file: /var/imap/mailboxes.db
imapd/ctl_cyrusdb[31550]: DBERROR db4: no absolute path for the current
directory: Permission denied
imapd/ctl_cyrusdb[31550]: DBERROR: error listing log files: Permission denied
imapd/ctl_cyrusdb[31550]: DBERROR: archive /var/imap/db: cyrusdb error
imapd/ctl_cyrusdb[31550]: DBERROR db4: no absolute path for the current
directory: Permission denied
imapd/ctl_cyrusdb[31550]: DBERROR: error listing log files: Permission denied
imapd/ctl_cyrusdb[31550]: DBERROR: archive /var/imap/db: cyrusdb error
imapd/ctl_cyrusdb[31550]: done checkpointing cyrus databases
imapd/master[14035]: process 31550 exited, status 1

In spite of all these error messages, the server seems to work...

Does anyone know what is causing this?

thanks,

Rob Urban

Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/

Re: cyrus and DBERROR complains.

[Adam Tauno Williams]

On Sun, 2010-09-26 at 14:11 +0200, Josef Karliak wrote:
> Hi guys,
>on SLES 10 x64bit I see following complains in the syslog:
> Sep 26 12:44:36 email1 master[3805]: about to exec /usr/lib/cyrus/bin/lmtpd
> Sep 26 12:44:36 email1 lmtpunix[3805]: executed
> Sep 26 12:44:36 email1 lmtpunix[3805]: DBERROR db4: Logging region out  
> of memory; you may need to increase its size
> Sep 26 12:44:36 email1 lmtpunix[3805]: DBERROR: opening  
> /var/spool/imap/config/deliver.db: Cannot allocate memory
> Sep 26 12:44:36 email1 lmtpunix[3805]: DBERROR: opening  
> /var/spool/imap/config/deliver.db: cyrusdb error
> Sep 26 12:44:36 email1 lmtpunix[3805]: FATAL: lmtpd: unable to init  
> duplicate delivery database

Duplicate delivery database errors, I believe, are not fatal; the
message should still be delivered.

>"/var/lib/ldap/DB_CONFIG" contains:
> set_cachesize 0 1500 1
> set_lg_regionmax 262144
> set_lg_bsize 2097152
> set_flags DB_LOG_AUTOREMOVE
>But we do not use ldap, where is a right config for it ? Could you  
> kick me to the right way ? :)

??? That has nothing to do with the above.  The delivery database is
probably someplace like /var/lib/imap/deliverydb.  

The simplest solution is to not use BDB; set "duplicate_db" to
"skiplist" in /etc/imapd.conf

BDB is rarely, IMO, worth the headache.
-- 
Adam Tauno Williams  LPIC-1, Novell CLA
<http://www.whitemiceconsulting.com>
OpenGroupware, Cyrus IMAPd, Postfix, OpenLDAP, Samba


Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/

cyrus and DBERROR complains.

[Josef Karliak]

  Hi guys,
  on SLES 10 x64bit I see following complains in the syslog:

Sep 26 12:44:36 email1 master[3805]: about to exec /usr/lib/cyrus/bin/lmtpd
Sep 26 12:44:36 email1 lmtpunix[3805]: executed
Sep 26 12:44:36 email1 lmtpunix[3805]: DBERROR db4: Logging region out  
of memory; you may need to increase its size
Sep 26 12:44:36 email1 lmtpunix[3805]: DBERROR: opening  
/var/spool/imap/config/deliver.db: Cannot allocate memory
Sep 26 12:44:36 email1 lmtpunix[3805]: DBERROR: opening  
/var/spool/imap/config/deliver.db: cyrusdb error
Sep 26 12:44:36 email1 lmtpunix[3805]: FATAL: lmtpd: unable to init  
duplicate delivery database


  "/var/lib/ldap/DB_CONFIG" contains:
set_cachesize 0 1500 1
set_lg_regionmax 262144
set_lg_bsize 2097152
set_flags DB_LOG_AUTOREMOVE

  But we do not use ldap, where is a right config for it ? Could you  
kick me to the right way ? :)

  thanks a lot !
  J.Karliak



This message was sent using IMP, the Internet Messaging Program.



binKiaXZBXUmg.bin
Description: Veřejný PGP	klíč

Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/

Re: cvt_cyrusdb: DBERROR Я^F^H: db4

[Andrew Brink]

I was able to fix the problem by recompiling my cyrus binaries, doing
a make install and starting with a clean /var/imap directory.  I was
then able to move my mailboxes.db file back, with several other files
and it started working

2010/8/31 Björn Fahller :
> On Tuesday 31 August 2010 02.42.51 Andrew Brink wrote:
>
>> When I try to start cyrus I get many DBERROR: db4 errors.
>>
>> When I try to convert deliver.db and tls_session.db from berkeley to
>> skiplist using cvt_cyrusdb, I get the same error.  (All other
>> databases are already skiplist.)
>>
>> Any ideas would be great?  We are dead in the water at this point.  I
>> suspect the problem has to do with some DB4 mis matches?  Any
>> troubleshooting pointers?
>
> Hmm, I'm not sure if this was the exact same situation as mine, but a number
> of horrendous expletives were heard when I upgraded the Berkleley DB libs. It
> was easy enough to solve with "dbX.Y_upgrade file.db"
>   _
> /Bjorn
>

Cyrus Home Page: http://cyrusimap.web.cmu.edu/
Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html

Re: cvt_cyrusdb: DBERROR Я^F^H: db4

[Björn Fahller]

On Tuesday 31 August 2010 02.42.51 Andrew Brink wrote:

> When I try to start cyrus I get many DBERROR: db4 errors.
> 
> When I try to convert deliver.db and tls_session.db from berkeley to
> skiplist using cvt_cyrusdb, I get the same error.  (All other
> databases are already skiplist.)
> 
> Any ideas would be great?  We are dead in the water at this point.  I
> suspect the problem has to do with some DB4 mis matches?  Any
> troubleshooting pointers?

Hmm, I'm not sure if this was the exact same situation as mine, but a number 
of horrendous expletives were heard when I upgraded the Berkleley DB libs. It 
was easy enough to solve with "dbX.Y_upgrade file.db"
   _
/Bjorn

Cyrus Home Page: http://cyrusimap.web.cmu.edu/
Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html

Re: cvt_cyrusdb: DBERROR Я^ F^H: db4

[Dan White]

On 30/08/10 20:09 -0500, Andrew Brink wrote:
>It should be noted that this is 2.2.12 and if i delete deliver.db,
>cyrus does not recreate it upon startup
>
>On Mon, Aug 30, 2010 at 7:42 PM, Andrew Brink  wrote:
>> So another admin was messing around on our email server, and I have no
>> idea what happened.
>>
>> When I try to start cyrus I get many DBERROR: db4 errors.
>>
>> When I try to convert deliver.db and tls_session.db from berkeley to
>> skiplist using cvt_cyrusdb, I get the same error.  (All other
>> databases are already skiplist.)
>>
>> Any ideas would be great?  We are dead in the water at this point.  I
>> suspect the problem has to do with some DB4 mis matches?  Any
>> troubleshooting pointers?

What's your imapd.conf config?

Specifically, do you get any output from:

grep '_db\|suppress' /etc/imapd.conf

On a 2.2.13 system, with default debian configuration, when I stop cyrus,
remove both the deliver.db and tls_sessions.db files, then restart cyrus,
they both get recreated.

Any permissions problems on your ?

If you want to convert those databases to skiplist, you should modify your
imapd.conf and configure duplicate_db and tlscache_db.

-- 
Dan White

Cyrus Home Page: http://cyrusimap.web.cmu.edu/
Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html

Re: cvt_cyrusdb: DBERROR Я^F^H: db4

[Andrew Brink]

It should be noted that this is 2.2.12 and if i delete deliver.db,
cyrus does not recreate it upon startup

On Mon, Aug 30, 2010 at 7:42 PM, Andrew Brink  wrote:
> So another admin was messing around on our email server, and I have no
> idea what happened.
>
> When I try to start cyrus I get many DBERROR: db4 errors.
>
> When I try to convert deliver.db and tls_session.db from berkeley to
> skiplist using cvt_cyrusdb, I get the same error.  (All other
> databases are already skiplist.)
>
> Any ideas would be great?  We are dead in the water at this point.  I
> suspect the problem has to do with some DB4 mis matches?  Any
> troubleshooting pointers?
>
> Thanks
>

Cyrus Home Page: http://cyrusimap.web.cmu.edu/
Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html

cvt_cyrusdb: DBERROR Я^F^H: db4

[Andrew Brink]

So another admin was messing around on our email server, and I have no
idea what happened.

When I try to start cyrus I get many DBERROR: db4 errors.

When I try to convert deliver.db and tls_session.db from berkeley to
skiplist using cvt_cyrusdb, I get the same error.  (All other
databases are already skiplist.)

Any ideas would be great?  We are dead in the water at this point.  I
suspect the problem has to do with some DB4 mis matches?  Any
troubleshooting pointers?

Thanks

Cyrus Home Page: http://cyrusimap.web.cmu.edu/
Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html

DBERROR

[Oscar Nuñez]

Hi folks,

I have a problem with my backend server in a cyrus agreggator configuration.
In the logs appear the following error when cyrus check the database each 30
min.

ctl_cyrusdb[7634]: checkpointing cyrus databases
ctl_cyrusdb[7634]: DBERROR: error listing log files: DB_NOTFOUND: No
matching key/data pair found
ctl_cyrusdb[7634]: DBERROR: archive /var/imap/db: cyrusdb error
ctl_cyrusdb[7634]: done checkpointing cyrus databases

My cyrus.conf

START {
  recover cmd="ctl_cyrusdb -r"
  mupdatepush cmd="ctl_mboxlist -m"
}

SERVICES {
  imap cmd="imapd" listen="imap" prefork=10 maxchild=2000
  pop3 cmd="pop3d" listen="pop3" prefork=0
  sieve cmd="timsieved" listen="sieve" prefork=0
  lmtpunix cmd="lmtpd" listen="/var/imap/socket/lmtp" prefork=0
  fud cmd="fud" proto="udp" listen="4201" prefork=0 maxchilds=10
}

EVENTS {
  checkpoint cmd="ctl_cyrusdb -c" period=30
  delprune cmd="cyr_expire -E 3" at=0400
  tlsprune cmd="tls_prune" at=0400
}
#

any idea of what has happended
i hope yours anserws


-- 
ATTE
Oscar Nunez

Cyrus Home Page: http://cyrusimap.web.cmu.edu/
Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html

Re: DBERROR with Cyrus 2.2.12

[Andrew Morgan]

On Thu, 9 Jul 2009, Adam Tauno Williams wrote:

>> Would it be helpful to others, it is to me, to include the cited list 
>> message below on that same wiki page telling others how to convert from 
>> one backend to another?
>
> Page 120 - 121 of my 'book' has an example of cvt_cyrusdb
> 
>
> Except I just noticed the statement "the server must be online when"
> should be "there server must be offline when".  BUG!

Wow, that's some very nice documentation!

I suggest including Adam's detailed instructions in the wiki, rather 
than my rather vague instructions.  :)

Andy

Cyrus Home Page: http://cyrusimap.web.cmu.edu/
Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html

Re: DBERROR with Cyrus 2.2.12

[Adam Tauno Williams]

> Would it be helpful to others, it is to me, to include the cited list message 
> below on that same wiki page telling others how to convert from one backend 
> to another?

Page 120 - 121 of my 'book' has an example of cvt_cyrusdb


Except I just noticed the statement "the server must be online when"
should be "there server must be offline when".  BUG!

-- 
OpenGroupware developer: awill...@whitemice.org

OpenGroupare & Cyrus IMAPd documenation @



Cyrus Home Page: http://cyrusimap.web.cmu.edu/
Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html

Re: DBERROR with Cyrus 2.2.12

[Mike Eggleston]

On Thu, 09 Jul 2009, Harms Consulting IT support desk might have said:



> I'm also not an expert but I had these messages early on with my setup
> and the resolution was to switch from Berkeley DB to the native skiplist
> format. This was covered a couple of weeks ago on this list. Search the
> list archives for subject: Db4 problems.
> 
> I highly recommend reading this page from the Cyrus wiki:
> 
> http://cyrusimap.web.cmu.edu/twiki/bin/view/Cyrus/WhatDatabaseBackend
> 
> Good luck,
> 
> Josh

List:

Would it be helpful to others, it is to me, to include the cited list message 
below on that same wiki page telling others how to convert from one backend to 
another?

Mike


On Wed, 1 Jul 2009, Paul van der Vlis wrote:

> Hello!
>
> I have errors in my log, and sometimes Cyrus crashes and I have to
> reboot the server because restarting gives this error:
>
> mail:~# /etc/init.d/cyrus2.2 restart
> Stopping Cyrus IMAPd: cyrmaster.
> Waiting for complete shutdown
> fatal: incomplete shutdown detected, aborting.
>
> In the log I see all the time errors like:
> --
> Jul  1 10:35:27 mail cyrus/imap[16841]: DBERROR db4: Database handles
> open during environment close
> Jul  1 10:35:27 mail cyrus/imap[16841]: DBERROR: error exiting
> application: Invalid argument
> --
>
> When Cyrus stops working I see this in the logs:
> ---
> Jul  1 10:40:04 mail cyrus/imap[16920]: DBERROR db4: Logging region out
> of memory; you may need to increase its size
> Jul  1 10:40:04 mail cyrus/imap[16920]: DBERROR: opening
> /var/lib/cyrus/tls_sessions.db: Cannot allocate memory
> Jul  1 10:40:04 mail cyrus/imap[16920]: DBERROR: opening
> /var/lib/cyrus/tls_sessions.db: cyrusdb error
> -
>
> I am not sure what's the problem here.
>
> Do I need to increase the memory size of the Berkeley database?
> and where can I do that?
>
> Can I remove /var/lib/cyrus/tls_sessions.db?
> (I have the same problem with deliver.db.)
>
> What will be that "Databases handles open during environment close", can
> that give this problem?

Here's what I recommend - get rid of Berkeley DB in Cyrus and use skiplist 
instead.  :)

Change your backend database formats to skiplist in imapd.conf, something 
like:

# Backend database formats to use
annotation_db: skiplist
duplicate_db: skiplist
mboxlist_db: skiplist
quota_db: quotalegacy
seenstate_db: skiplist
statuscache_db: skiplist
subscription_db: flat
tlscache_db: skiplist


A lot of us got tired of messing around with Berkeley DB and switched to 
skiplist.

If you decide to change formats, make sure you stop Cyrus and remove the 
contents of the {configdirectory}/db/ directory.  You'll also want to 
delete the deliver.db and tls_sessions.db files, assuming those are the 
ones you change.  tls_sessions.db does not contain any information that 
needs to persist between Cyrus restarts.  deliver.db contains duplicate 
messsage suppression information and is also used for vacation reply 
tracking.  The worst that will happen if you delete deliver.db is that 
someone may get a second vacation reply message sent out.

Andy

Cyrus Home Page: http://cyrusimap.web.cmu.edu/
Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html


Cyrus Home Page: http://cyrusimap.web.cmu.edu/
Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html

Re: DBERROR with Cyrus 2.2.12

[Pascal Gienger]

Christophe Boyanique schrieb:
> In fact I managaged to solve the problem by removing the quota file in
> /var/lib/imap/quota/x// and using "quota -f" on the mailboxes.

So the quota file was corrupt. Ok. Do you really use DB4 quota files?

> But I still get repeating error messages like this:
> 
> Jul  7 14:58:51 mail7702 lmtpunix[8988]: DBERROR db4: 9 lockers
> Jul  7 15:04:24 mail7702 lmtpunix[9249]: DBERROR db4: 11 lockers
> 
> Should I be worried by these messages ?

No. In fact they are not errors but informational messages, so in newer 
versions of cyrus imapd you will see

Jul  8 15:39:28 atlanta lmtpunix[29159]: [ID 366844 local6.info] DBMSG: 
2279 lockers
Jul  8 15:51:34 atlanta lmtpunix[29077]: [ID 366844 local6.info] DBMSG: 
2249 lockers
Jul  8 18:12:14 atlanta lmtpunix[4289]: [ID 366844 local6.info] DBMSG: 
1583 lockers

lmtpunix wants to open delivery.db which normally is a DB4 backed 
database unless you have changed the default in imapd.conf.

Some old DB4 version had the problem of not releasing these locks so 
there was an overflow after some time. If the number of lockers keep 
growing without every becoming smaller from time to time you are running 
in this bug.


-- 
Pascal Gienger
University of Konstanz, IT Services Department ("Rechenzentrum")
Electronic Communications and Web Services
Building V, Room V404, Phone +49 7531 88 5048, Fax +49 7531 88 3739

Cyrus Home Page: http://cyrusimap.web.cmu.edu/
Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html

Re: DBERROR with Cyrus 2.2.12

[Harms Consulting IT support desk]

Toomas Aas wrote:
> Christophe Boyanique wrote:
>
>   
>> But I still get repeating error messages like this:
>>
>> Jul  7 14:58:51 mail7702 lmtpunix[8988]: DBERROR db4: 9 lockers
>> Jul  7 15:04:24 mail7702 lmtpunix[9249]: DBERROR db4: 11 lockers
>>
>> Should I be worried by these messages ?
>> 
>
> I am not the greatest Cyrus or Berkeley expert out there, but from long 
> time lurking on this list I remember that these messages can be ignored. I 
> have done so for years, and nothing bad seems to have happened.
>
> --
> Toomas
>
> ... I went to a general store, but they wouldn't let me buy anything specific.
> 
> Cyrus Home Page: http://cyrusimap.web.cmu.edu/
> Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki
> List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
>   
I'm also not an expert but I had these messages early on with my setup
and the resolution was to switch from Berkeley DB to the native skiplist
format. This was covered a couple of weeks ago on this list. Search the
list archives for subject: Db4 problems.

I highly recommend reading this page from the Cyrus wiki:

http://cyrusimap.web.cmu.edu/twiki/bin/view/Cyrus/WhatDatabaseBackend



Good luck,

Josh


Cyrus Home Page: http://cyrusimap.web.cmu.edu/
Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html

Re: DBERROR with Cyrus 2.2.12

[Toomas Aas]

Christophe Boyanique wrote:

> 
> But I still get repeating error messages like this:
> 
> Jul  7 14:58:51 mail7702 lmtpunix[8988]: DBERROR db4: 9 lockers
> Jul  7 15:04:24 mail7702 lmtpunix[9249]: DBERROR db4: 11 lockers
> 
> Should I be worried by these messages ?

I am not the greatest Cyrus or Berkeley expert out there, but from long 
time lurking on this list I remember that these messages can be ignored. I 
have done so for years, and nothing bad seems to have happened.

--
Toomas

... I went to a general store, but they wouldn't let me buy anything specific.

Cyrus Home Page: http://cyrusimap.web.cmu.edu/
Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html

Re: DBERROR with Cyrus 2.2.12

[Christophe Boyanique]

Hello Michael Menge, you wrote:

> Did you have a look at the mailboxes_dmp.txt file? Maybe it is corrupt?
> I would search for user.foobar

At first (quick) sight the file seemed to be correct. Here is an extract
of a box which had the problem (I added the blank lines and replaced
tabs by spaces):

--- cut ---
user.catherine^cudorge default catherine.cudorge lrswipcda

user.catherine^cudorge.&AMk-l&AOk-ments envoy&AOk-s default
catherine.cudorge lrswipcda cyrus lrswipcda catherine^cudorge lrswipcda


user.catherine^cudorge.Brouillons default catherine.cudorge lrswipcda
cyrus lrswipcda

user.catherine^cudorge.Courriers non d&AOk-sir&AOk-s default
catherine.cudorge lrs cyrus lrs

user.catherine^cudorge.Courriers non d&AOk-sir&AOk-s.A recevoir default
catherine.cudorge lrswipcd cyrus lrswipcd

user.catherine^cudorge.Courriers non d&AOk-sir&AOk-s.A rejeter default
catherine.cudorge lrswipcd cyrus lrswipcd

user.catherine^cudorge.Courriers non d&AOk-sir&AOk-s.D&AOk-tection
automatique default catherine.cudorge lrswipcd cyrus lrs

user.catherine^cudorge.El&AOk-ments envoy&AOk-s default
catherine.cudorge lrswipcda cyrus lrswipcda

user.catherine^cudorge.INBOX default catherine.cudorge lrswipcda cyrus
 lrswipcda

user.catherine^cudorge.Trash default catherine.cudorge lrswipcda cyrus
 lrswipcda

user.catherine^cudorge.archives default catherine.cudorge lrswipcda
cyrus lrswipcda catherine^cudorge lrswipcda
--- cut ---

Except a weird "catherine^cudorge lrswipcd" for two mailboxes in the
acl, entries seems to be normal.



In fact I managaged to solve the problem by removing the quota file in
/var/lib/imap/quota/x// and using "quota -f" on the mailboxes.


But I still get repeating error messages like this:

Jul  7 14:58:51 mail7702 lmtpunix[8988]: DBERROR db4: 9 lockers
Jul  7 15:04:24 mail7702 lmtpunix[9249]: DBERROR db4: 11 lockers

Should I be worried by these messages ?


Regards,

Christophe.

Cyrus Home Page: http://cyrusimap.web.cmu.edu/
Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html

Re: DBERROR with Cyrus 2.2.12

[David Mayo]

Christophe,

Christophe Boyanique wrote:

> I've got a problem with an old Cyrus installation: it is a 2.2.12
> version on RedHat AS3 server which used to work correctly. It seems that
> after a power failure, some mailboxes have been corrupted.
> 
> On 1000 mailboxes, 5 seem to be unreachable (for imap reads or lmtp
> deliveries) with this message in the log:
> 
> DBERROR: error fetching user.foobar: cyrusdb error

I may be way off the mark here, but have you run the Berkeley DB 
recovery program?

/etc/init.d/cyrus-imapd stop
cd /var/lib/imap
/path/to/berkeley/bin/db_recover

?

Regards,


Dave.

David Mayo
Networks/Systems Administrator
University of Bath Computing Services, UK


Cyrus Home Page: http://cyrusimap.web.cmu.edu/
Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html

Re: DBERROR with Cyrus 2.2.12

[Michael Menge]

Quoting Christophe Boyanique :



Hello,

I've got a problem with an old Cyrus installation: it is a 2.2.12
version on RedHat AS3 server which used to work correctly. It seems that
after a power failure, some mailboxes have been corrupted.

On 1000 mailboxes, 5 seem to be unreachable (for imap reads or lmtp
deliveries) with this message in the log:

DBERROR: error fetching user.foobar: cyrusdb error

I tried without success (with cyrus started or stopped) to reconstruct
the boxes with:

su - cyrus -c "/usr/lib/cyrus-imapd/reconstruct -fr user/foobar"

I also tried to stop the server, delete all the cyrus.* files in the
user mailbox, reconstruct it and start again cyrus. But i always get the
same errors...


I also tried to regenerate the mailbox file without success with:

/etc/init.d/cyrus-imapd stop
cp /var/lib/imap/mailboxes.db /var/lib/imap/mailboxes.db.orig
su -c '/usr/lib/cyrus-imapd/ctl_mboxlist -d > /tmp/mailboxes_dmp.txt' cyrus
su -c '/usr/lib/cyrus-imapd/cvt_cyrusdb /tmp/mailboxes_dmp.txt flat
/tmp/mailboxes.db skiplist' cyrus
cp /tmp/mailboxes.db /var/lib/imap/mailboxes.db
chown cyrus:mail /var/lib/imap/mailboxes.db
/etc/init.d/cyrus-imapd start

But Cyrus does not accept the new file so I add to revert back: for all
users I had these errors:



Did you have a look at the mailboxes_dmp.txt file? Maybe it is corrupt?
I would search for user.foobar


imap[27307]: user.foobar: can't find partition
master[27006]: service imap pid 27532 in BUSY state: terminated abnormally





M.MengeTel.: (49) 7071/29-70316
Universität Tübingen   Fax.: (49) 7071/29-5912
Zentrum für Datenverarbeitung  mail:  
michael.me...@zdv.uni-tuebingen.de

Wächterstraße 76
72074 Tübingen

smime.p7s
Description: S/MIME krytographische Unterschrift

Cyrus Home Page: http://cyrusimap.web.cmu.edu/
Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html

DBERROR with Cyrus 2.2.12

[Christophe Boyanique]

Hello,

I've got a problem with an old Cyrus installation: it is a 2.2.12
version on RedHat AS3 server which used to work correctly. It seems that
after a power failure, some mailboxes have been corrupted.

On 1000 mailboxes, 5 seem to be unreachable (for imap reads or lmtp
deliveries) with this message in the log:

DBERROR: error fetching user.foobar: cyrusdb error

I tried without success (with cyrus started or stopped) to reconstruct
the boxes with:

su - cyrus -c "/usr/lib/cyrus-imapd/reconstruct -fr user/foobar"

I also tried to stop the server, delete all the cyrus.* files in the
user mailbox, reconstruct it and start again cyrus. But i always get the
same errors...


I also tried to regenerate the mailbox file without success with:

/etc/init.d/cyrus-imapd stop
cp /var/lib/imap/mailboxes.db /var/lib/imap/mailboxes.db.orig
su -c '/usr/lib/cyrus-imapd/ctl_mboxlist -d > /tmp/mailboxes_dmp.txt' cyrus
su -c '/usr/lib/cyrus-imapd/cvt_cyrusdb /tmp/mailboxes_dmp.txt flat
/tmp/mailboxes.db skiplist' cyrus
cp /tmp/mailboxes.db /var/lib/imap/mailboxes.db
chown cyrus:mail /var/lib/imap/mailboxes.db
/etc/init.d/cyrus-imapd start

But Cyrus does not accept the new file so I add to revert back: for all
users I had these errors:

imap[27307]: user.foobar: can't find partition
master[27006]: service imap pid 27532 in BUSY state: terminated abnormally

Does anyone have an idea of what is the problem ? Is the mailboxes file
corrupted or ma I in a dead end ?
Is there a better way to generate a fresh mailboxes file ?


I also have these kinds of error messages:

lmtpunix[28440]: DBERROR db4: 23 lockers


Christophe.

Cyrus Home Page: http://cyrusimap.web.cmu.edu/
Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html

Re: Cyrus DB Errors "DBERROR: error fetching user.username" even after reconstructs

[Bron Gondwana]

On Thu, Feb 12, 2009 at 09:45:58AM -0600, Josh Whitver wrote:
> It's actually possible we are using BDB - earlier in the mail server's  
> life we moved it from a PowerPC G5 Xserve to the Intel Xserve, and we  
> needed to work around the endian issues inherent in some part of the  
> mail server, so I recall converting a database in some direction, either 
> from BDB to skiplist or vice-versa.  My memory escapes  me now as to 
> which way we went, though.  How would I check?

grep mboxlist_db /etc/imapd.conf

The default is skiplist, so it will be skiplist unless you have
something else there.

(but then, I know it's skiplist because I have a copy of it now!)

Bron.

Cyrus Home Page: http://cyrusimap.web.cmu.edu/
Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html

Re: Cyrus DB Errors "DBERROR: error fetching user.username" even after reconstructs

[Josh Whitver]

It's actually possible we are using BDB - earlier in the mail server's  
life we moved it from a PowerPC G5 Xserve to the Intel Xserve, and we  
needed to work around the endian issues inherent in some part of the  
mail server, so I recall converting a database in some direction,  
either from BDB to skiplist or vice-versa.  My memory escapes  me now  
as to which way we went, though.  How would I check?
--
Josh Whitver
whitv...@urbandale.k12.ia.us / j...@whitver.net
(If you can't hear me, it's because I'm in parentheses)


On Feb 11, 2009, at 8:40 PM, Bron Gondwana wrote:

>
> On Tue, 10 Feb 2009 15:59:09 -0600, "Josh Whitver" 
>  > said:
>> Whenever an IMAP connection is attempted, I see this in the log:
>> Feb 10 09:14:17 urbandale imap[34508]: DBERROR: error fetching user.
>> [username]: cyrusdb error
>
> OK - there are two spots in the code that can produce exactly that
> error message.  One is in BDB, which I assume you're not using.  The
> other is in mboxlist (latest CVS changes this one to "error fetching
> mboxlist user.[username]: [error]" to be clearer!)
>
> So, it's in mboxlist_mylookup.  The specific error is being returned
> by:
>
>if (wrlock) {
>r = DB->fetchlock(mbdb, name, namelen, &data, &datalen, tid);
>} else {
>r = DB->fetch(mbdb, name, namelen, &data, &datalen, tid);
>}
>
>...
>
>default:
>syslog(LOG_ERR, "DBERROR: error fetching mboxlist %s: %s",
>   name, cyrusdb_strerror(r));
>return IMAP_IOERROR;
>break;
>
> Sorry I didn't get back to you before.  I really don't think I can
> debug this any further without a copy of your mailboxes.db file.
>
> I assume you've ruled out filesystem corruption by checking syslog/ 
> dmesg/
> whatever for signs of bad blocks?
>
> Bron.
> -- 
>  Bron Gondwana
>  br...@fastmail.fm
>
>


Cyrus Home Page: http://cyrusimap.web.cmu.edu/
Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html

Re: Cyrus DB Errors "DBERROR: error fetching user.username" even after reconstructs

[Bron Gondwana]

On Tue, 10 Feb 2009 15:59:09 -0600, "Josh Whitver" 
 said:
> Whenever an IMAP connection is attempted, I see this in the log:
> Feb 10 09:14:17 urbandale imap[34508]: DBERROR: error fetching user. 
> [username]: cyrusdb error

OK - there are two spots in the code that can produce exactly that
error message.  One is in BDB, which I assume you're not using.  The
other is in mboxlist (latest CVS changes this one to "error fetching
mboxlist user.[username]: [error]" to be clearer!)

So, it's in mboxlist_mylookup.  The specific error is being returned
by:

if (wrlock) {
r = DB->fetchlock(mbdb, name, namelen, &data, &datalen, tid);
} else {
r = DB->fetch(mbdb, name, namelen, &data, &datalen, tid);
}

...

default:
syslog(LOG_ERR, "DBERROR: error fetching mboxlist %s: %s",
   name, cyrusdb_strerror(r));
return IMAP_IOERROR;
break;

Sorry I didn't get back to you before.  I really don't think I can
debug this any further without a copy of your mailboxes.db file.

I assume you've ruled out filesystem corruption by checking syslog/dmesg/
whatever for signs of bad blocks?

Bron.
-- 
  Bron Gondwana
  br...@fastmail.fm


Cyrus Home Page: http://cyrusimap.web.cmu.edu/
Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html

Re: Cyrus DB Errors "DBERROR: error fetching user.username" even after reconstructs

[Dan White]

Dan White wrote:
>
> imapcmd="proxyd -U 30" listen="1.2.3.4:imap" 
> prefork=0 maxchild=200
> imaplh cmd="imapd -U 30 -D" listen="127.0.0.1:imap" 
> prefork=0 maxchild=200
>
>   

Typo. That's what I get for cutting and pasting from different systems. 
Both cmds should be imapd. I'm assuming you're not proxying.

- Dan

Cyrus Home Page: http://cyrusimap.web.cmu.edu/
Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html

Re: Cyrus DB Errors "DBERROR: error fetching user.username" even after reconstructs

[Dan White]

Josh Whitver wrote:
> Thanks, but I've already gone in via cyradm and deleted the mailboxes
> and recreated them, and following the steps above, completely rebuilt  
> the mailboxes.db file last night - same problems.  Thank you Mario,  
> but I think my princess is in another castle! :)
>   


Josh,

To get more details about what's going on underneath the hood, you can 
use the debug_command option (man imapd.conf) to obtain a back trace of 
the hanging imapd process.

For some configuration scenarios, see:

https://langhorst.com/cgi-bin/dwww//usr/share/doc/cyrus21-common/README.Debian.debug.gz

If you know the specific mailbox that is causing the problem, and you 
want to only debug specific IMAP connections, you could configure (in 
/etc/cyrus.conf):

imapcmd="proxyd -U 30" listen="1.2.3.4:imap" 
prefork=0 maxchild=200
imaplh cmd="imapd -U 30 -D" listen="127.0.0.1:imap" 
prefork=0 maxchild=200

where 1.2.3.4 is the address your users connect to. And then connect to 
the 127.0.0.1 imap port to debug that user's connection.

- Dan

Cyrus Home Page: http://cyrusimap.web.cmu.edu/
Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html

Re: Cyrus DB Errors "DBERROR: error fetching user.username" even after reconstructs

[Josh Whitver]

On Feb 11, 2009, at 1:49 PM, Blake Hudson wrote:
>> On Feb 10, 2009, at 9:52 PM, Josh Whitver wrote:
>>
>> Yeah, you have a broken mailboxes.db I'd say!
>>
>> Here's what I would do:
>>
>> # stop cyrus
>> cyr_dbtool /var/imap/mailboxes.db skiplist show > mailboxes.dump
>> cyr_dbtool -n /var/lib/mailboxes_new.db skiplist set <
>> mailboxes.dump
>> mv /var/imap/mailboxes.db /var/imap/mailboxes_old.db
>> mv /var/lib/mailboxes_new.db /var/imap/mailboxes.db
>> # start cyrus
>>
>> This will give you a brand new clean mailboxes.db (but keep the  
>> old
>> one
>> just in case)
>>
>> Bron.
>>
>>> Well, I just tried it - no dice.  Same issues persist, even with a
>>> fresh mailboxes.db file.
>>>
>>> Next steps?
>>>
>> Anyone?  Bueller?
>>
> I agree it looks like a mailbox db problem. My inclination after a  
> failed reconstruct would be to remove and recreate the mailbox and  
> permissions (perhaps checking the mailbox db in between steps).
>
> -Blake


Thanks, but I've already gone in via cyradm and deleted the mailboxes  
and recreated them, and following the steps above, completely rebuilt  
the mailboxes.db file last night - same problems.  Thank you Mario,  
but I think my princess is in another castle! :)
--
Josh Whitver
whitv...@urbandale.k12.ia.us / j...@whitver.net
I once planted some birdseed.  A bird came up.
Now I don't know what to feed it.

Cyrus Home Page: http://cyrusimap.web.cmu.edu/
Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html

Re: Cyrus DB Errors "DBERROR: error fetching user.username" even after reconstructs

[Blake Hudson]

 Original Message  
Subject: Re: Cyrus DB Errors "DBERROR: error fetching user.username"
evenafter reconstructs
From: Josh Whitver 
To: info-cyrus@lists.andrew.cmu.edu
Date: Wednesday, February 11, 2009 1:32:52 PM
> On Feb 10, 2009, at 9:52 PM, Josh Whitver wrote:
>   
>>>>> Yeah, you have a broken mailboxes.db I'd say!
>>>>>
>>>>> Here's what I would do:
>>>>>
>>>>> # stop cyrus
>>>>> cyr_dbtool /var/imap/mailboxes.db skiplist show > mailboxes.dump
>>>>> cyr_dbtool -n /var/lib/mailboxes_new.db skiplist set <
>>>>> mailboxes.dump
>>>>> mv /var/imap/mailboxes.db /var/imap/mailboxes_old.db
>>>>> mv /var/lib/mailboxes_new.db /var/imap/mailboxes.db
>>>>> # start cyrus
>>>>>
>>>>> This will give you a brand new clean mailboxes.db (but keep the old
>>>>> one
>>>>> just in case)
>>>>>
>>>>> Bron.
>>>>>   
>> Well, I just tried it - no dice.  Same issues persist, even with a
>> fresh mailboxes.db file.
>>
>> Next steps?
>> 
>
> Anyone?  Bueller?
>   
I agree it looks like a mailbox db problem. My inclination after a
failed reconstruct would be to remove and recreate the mailbox and
permissions (perhaps checking the mailbox db in between steps).

-Blake

Cyrus Home Page: http://cyrusimap.web.cmu.edu/
Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html

Re: Cyrus DB Errors "DBERROR: error fetching user.username" even after reconstructs

[Josh Whitver]

On Feb 10, 2009, at 9:52 PM, Josh Whitver wrote:
 Yeah, you have a broken mailboxes.db I'd say!

 Here's what I would do:

 # stop cyrus
 cyr_dbtool /var/imap/mailboxes.db skiplist show > mailboxes.dump
 cyr_dbtool -n /var/lib/mailboxes_new.db skiplist set <
 mailboxes.dump
 mv /var/imap/mailboxes.db /var/imap/mailboxes_old.db
 mv /var/lib/mailboxes_new.db /var/imap/mailboxes.db
 # start cyrus

 This will give you a brand new clean mailboxes.db (but keep the old
 one
 just in case)

 Bron.
> Well, I just tried it - no dice.  Same issues persist, even with a
> fresh mailboxes.db file.
>
> Next steps?

Anyone?  Bueller?
--
Josh Whitver
whitv...@urbandale.k12.ia.us / j...@whitver.net
"Give me ambiguity or give me something else!"


Cyrus Home Page: http://cyrusimap.web.cmu.edu/
Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html

Re: Cyrus DB Errors "DBERROR: error fetching user.username" even after reconstructs

[Josh Whitver]

On Feb 10, 2009, at 6:11 PM, Bron Gondwana wrote:

> On Tue, Feb 10, 2009 at 05:20:42PM -0600, Josh Whitver wrote:
>> On Feb 10, 2009, at 5:08 PM, Bron Gondwana wrote:

>>>
>>> Yeah, you have a broken mailboxes.db I'd say!
>>>
>>> Here's what I would do:
>>>
>>> # stop cyrus
>>> cyr_dbtool /var/imap/mailboxes.db skiplist show > mailboxes.dump
>>> cyr_dbtool -n /var/lib/mailboxes_new.db skiplist set <  
>>> mailboxes.dump
>>> mv /var/imap/mailboxes.db /var/imap/mailboxes_old.db
>>> mv /var/lib/mailboxes_new.db /var/imap/mailboxes.db
>>> # start cyrus
>>>
>>> This will give you a brand new clean mailboxes.db (but keep the old
>>> one
>>> just in case)
>>>
>>> Bron.
>>>
>>
>> Thanks - is this one of those operations that will kill the read/ 
>> unread
>> status of my messages, or should all that stuff be preserved?
>
> No, it won't kill anything (hopefully).  You may want to compare the
> output of show on the new file with show on the old file.  They  
> _should_
> be identical.
>
> If you want to email me (privately) a copy of your old mailboxes.db,  
> I'd
> be happy to have a look through it and check for corruption.   
> Obviously
> it contains private details (usernames, folder names and ACLs - no
> actual email) of your users, so it's up to you.
>
> Bron ( who knows the skiplist format far too intimately! )

Well, I just tried it - no dice.  Same issues persist, even with a  
fresh mailboxes.db file.

Next steps?
--
Josh Whitver
whitv...@urbandale.k12.ia.us / j...@whitver.net
This message transmitted on 100% recycled electrons.

Cyrus Home Page: http://cyrusimap.web.cmu.edu/
Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html

Re: Cyrus DB Errors "DBERROR: error fetching user.username" even after reconstructs

[Bron Gondwana]

On Tue, Feb 10, 2009 at 05:20:42PM -0600, Josh Whitver wrote:
> On Feb 10, 2009, at 5:08 PM, Bron Gondwana wrote:
>>>
>>
>> Yeah, you have a broken mailboxes.db I'd say!
>>
>> Here's what I would do:
>>
>> # stop cyrus
>> cyr_dbtool /var/imap/mailboxes.db skiplist show > mailboxes.dump
>> cyr_dbtool -n /var/lib/mailboxes_new.db skiplist set < mailboxes.dump
>> mv /var/imap/mailboxes.db /var/imap/mailboxes_old.db
>> mv /var/lib/mailboxes_new.db /var/imap/mailboxes.db
>> # start cyrus
>>
>> This will give you a brand new clean mailboxes.db (but keep the old  
>> one
>> just in case)
>>
>> Bron.
>>
>
> Thanks - is this one of those operations that will kill the read/unread 
> status of my messages, or should all that stuff be preserved?

No, it won't kill anything (hopefully).  You may want to compare the
output of show on the new file with show on the old file.  They _should_
be identical.

If you want to email me (privately) a copy of your old mailboxes.db, I'd
be happy to have a look through it and check for corruption.  Obviously
it contains private details (usernames, folder names and ACLs - no
actual email) of your users, so it's up to you.

Bron ( who knows the skiplist format far too intimately! )

Cyrus Home Page: http://cyrusimap.web.cmu.edu/
Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html

Re: Cyrus DB Errors "DBERROR: error fetching user.username" even after reconstructs

[Josh Whitver]

On Feb 10, 2009, at 5:08 PM, Bron Gondwana wrote:
>>
>
> Yeah, you have a broken mailboxes.db I'd say!
>
> Here's what I would do:
>
> # stop cyrus
> cyr_dbtool /var/imap/mailboxes.db skiplist show > mailboxes.dump
> cyr_dbtool -n /var/lib/mailboxes_new.db skiplist set < mailboxes.dump
> mv /var/imap/mailboxes.db /var/imap/mailboxes_old.db
> mv /var/lib/mailboxes_new.db /var/imap/mailboxes.db
> # start cyrus
>
> This will give you a brand new clean mailboxes.db (but keep the old  
> one
> just in case)
>
> Bron.
>

Thanks - is this one of those operations that will kill the read/ 
unread status of my messages, or should all that stuff be preserved?
--
Josh Whitver
whitv...@urbandale.k12.ia.us / j...@whitver.net
Give a man a fish, and you'll feed him for a day. Teach a man to fish,  
and he'll buy a funny hat. Talk to a hungry man about fish, and you're  
a consultant.

Cyrus Home Page: http://cyrusimap.web.cmu.edu/
Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html

Re: Cyrus DB Errors "DBERROR: error fetching user.username" even after reconstructs

[Bron Gondwana]

On Tue, Feb 10, 2009 at 03:59:09PM -0600, Josh Whitver wrote:
> Hello all,
> 
> I've got one user on my mail system that Cyrus seems to have it in  
> for.  IMAP connections stall out, mail messages to her get stuck in  
> the Postfix queue indefinitely, and things just generally aren't  
> working for her.  Server is an Intel Xserve running Mac OS X 10.5.5  
> Server, clients are 10.5.4 using Mail.app (but issues appear using any  
> IMAP client, such as our RoundCube webmail system).  All other users  
> (more than 500 of them) are fine.
> 
> Whenever an IMAP connection is attempted, I see this in the log:
> Feb 10 09:14:17 urbandale imap[34508]: DBERROR: error fetching user. 
> [username]: cyrusdb error
> 
> We've seen this kind of issue before, and usually doing the following  
> clears it up:
> sudo /usr/bin/cyrus/bin/reconstruct -r -f user/[username]
> 
> Under Tiger Server, you had to be sure to use sudo -u cyrusimap so  
> that the cyrus files would have the correct permissions, but under  
> Leopard, running it as root seems to do the job (the cyrus files are  
> owned by _cyrus afterwards, like they should be).
> 
> At any rate, that didn't solve her issues, so I ended up deleting the  
> cyrus.* files in all her mail boxes and her Inbox and running it  
> again, creating fresh copies.  Still no dice.  So then I tried:
> sudo /usr/bin/cyrus/bin/reconstruct -x -r user/[username]
> 
> Which again created fresh files, but the issues still persist.  I  
> backed up the user's mailboxes and went into cyradm and deleted them  
> altogether, and re-created them.  I didn't move any of the mail  
> messages back because I wanted to see if it would work with a blank  
> slate.  Same issue.
> 
> This seems to imply that something's borked in the main Cyrus  
> database, if I'm not mistaken.  The question then becomes what to do  
> about that.  Suggestions, anyone?  I'm rapidly running out of ideas -  
> any help you can offer would be appreciated.  Thanks!

Yeah, you have a broken mailboxes.db I'd say!

Here's what I would do:

# stop cyrus
cyr_dbtool /var/imap/mailboxes.db skiplist show > mailboxes.dump
cyr_dbtool -n /var/lib/mailboxes_new.db skiplist set < mailboxes.dump
mv /var/imap/mailboxes.db /var/imap/mailboxes_old.db
mv /var/lib/mailboxes_new.db /var/imap/mailboxes.db
# start cyrus

This will give you a brand new clean mailboxes.db (but keep the old one
just in case)

Bron.

Cyrus Home Page: http://cyrusimap.web.cmu.edu/
Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html

Cyrus DB Errors "DBERROR: error fetching user.username" even after reconstructs

[Josh Whitver]

Hello all,

I've got one user on my mail system that Cyrus seems to have it in  
for.  IMAP connections stall out, mail messages to her get stuck in  
the Postfix queue indefinitely, and things just generally aren't  
working for her.  Server is an Intel Xserve running Mac OS X 10.5.5  
Server, clients are 10.5.4 using Mail.app (but issues appear using any  
IMAP client, such as our RoundCube webmail system).  All other users  
(more than 500 of them) are fine.

Whenever an IMAP connection is attempted, I see this in the log:
Feb 10 09:14:17 urbandale imap[34508]: DBERROR: error fetching user. 
[username]: cyrusdb error

We've seen this kind of issue before, and usually doing the following  
clears it up:
sudo /usr/bin/cyrus/bin/reconstruct -r -f user/[username]

Under Tiger Server, you had to be sure to use sudo -u cyrusimap so  
that the cyrus files would have the correct permissions, but under  
Leopard, running it as root seems to do the job (the cyrus files are  
owned by _cyrus afterwards, like they should be).

At any rate, that didn't solve her issues, so I ended up deleting the  
cyrus.* files in all her mail boxes and her Inbox and running it  
again, creating fresh copies.  Still no dice.  So then I tried:
sudo /usr/bin/cyrus/bin/reconstruct -x -r user/[username]

Which again created fresh files, but the issues still persist.  I  
backed up the user's mailboxes and went into cyradm and deleted them  
altogether, and re-created them.  I didn't move any of the mail  
messages back because I wanted to see if it would work with a blank  
slate.  Same issue.

This seems to imply that something's borked in the main Cyrus  
database, if I'm not mistaken.  The question then becomes what to do  
about that.  Suggestions, anyone?  I'm rapidly running out of ideas -  
any help you can offer would be appreciated.  Thanks!
--
Josh Whitver
whitv...@urbandale.k12.ia.us / j...@whitver.net
Don't anthropomorphize computers.  They hate that.



Cyrus Home Page: http://cyrusimap.web.cmu.edu/
Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html

Re: lmtpunix: DBERROR db4: Logging region out of memory; you may need to increase its size

[Bron Gondwana]

On Fri, Sep 19, 2008 at 03:05:37PM -0400, Adam Tauno Williams wrote:
> > I got no answer on this subject, does someone has a suggestions, or 
> > maybe should I give more details ?
> 
> Possibly create a DB_CONFIG file in the db directory and restart Cyrus?
> I ***ASSUME*** that Cyrus will honor the settings in the DB_CONFIG file.
> (?)
> 
> 
> 
> This is a common issue with somewhat older versions of OpenLDAP when
> mixed with admins who refuse to read the documentation.  But I've never
> encountered it with Cyrus.

This is the what we put in DB_CONFIG at FastMail:

$ cat $cyrushome/db/DB_CONFIG
set_cachesize 0 2097152 1
set_lg_regionmax 2097152
set_lg_bsize 2097152
set_lg_max 4194304
set_tx_max 200
set_tas_spins 1
$

(off the top of my head, I don't have a clue how sane those values are -
we don't use berkeley for much, and I didn't write the config file!)

Bron.

Cyrus Home Page: http://cyrusimap.web.cmu.edu/
Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html

Re: lmtpunix: DBERROR db4: Logging region out of memory; you may need to increase its size

[Adam Tauno Williams]

> I got no answer on this subject, does someone has a suggestions, or 
> maybe should I give more details ?

Possibly create a DB_CONFIG file in the db directory and restart Cyrus?
I ***ASSUME*** that Cyrus will honor the settings in the DB_CONFIG file.
(?)

<http://www.oracle.com/technology/documentation/berkeley-db/db/ref/env/db_config.html>

This is a common issue with somewhat older versions of OpenLDAP when
mixed with admins who refuse to read the documentation.  But I've never
encountered it with Cyrus.

> >> I know this problem has been answered on different lists, but I don't 
> >> understand what to do to correct it ?
> >>
> >> lmtpunix[16846]: DBERROR db4: Logging region out of memory; you may need 
> >> to increase its size



Cyrus Home Page: http://cyrusimap.web.cmu.edu/
Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html

Re: lmtpunix: DBERROR db4: Logging region out of memory; you may need to increase its size

[Denis BUCHER]

Hello,

I got no answer on this subject, does someone has a suggestions, or 
maybe should I give more details ?

Denis

>> I know this problem has been answered on different lists, but I don't 
>> understand what to do to correct it ?
>>
>> lmtpunix[16846]: DBERROR db4: Logging region out of memory; you may need 
>> to increase its size
>>
>> If anyone could tell me exactly which commands or config to use it would 
>> be great !
> 
> These are the complete logs :
> 
> Sep 11 20:05:35 host lmtpunix[16846]: DBERROR db4: Logging region out of 
> memory; you may need to increase its size
> 
> Sep 11 20:05:35 host lmtpunix[16846]: DBERROR: opening 
> /var/lib/imap/deliver.db: Cannot allocate memory
> 
> Sep 11 20:05:35 host lmtpunix[16846]: DBERROR: opening 
> /var/lib/imap/deliver.db: cyrusdb error
> 
> Sep 11 20:05:35 host lmtpunix[16846]: FATAL: lmtpd: unable to init 
> duplicate delivery database
> 
> Denis

Cyrus Home Page: http://cyrusimap.web.cmu.edu/
Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html

Re: lmtpunix: DBERROR db4: Logging region out of memory; you may need to increase its size

[Denis BUCHER]

Denis BUCHER a écrit :
> I know this problem has been answered on different lists, but I don't 
> understand what to do to correct it ?
> 
> lmtpunix[16846]: DBERROR db4: Logging region out of memory; you may need 
> to increase its size
> 
> If anyone could tell me exactly which commands or config to use it would 
> be great !

These are the complete logs :

Sep 11 20:05:35 host lmtpunix[16846]: DBERROR db4: Logging region out of 
memory; you may need to increase its size

Sep 11 20:05:35 host lmtpunix[16846]: DBERROR: opening 
/var/lib/imap/deliver.db: Cannot allocate memory

Sep 11 20:05:35 host lmtpunix[16846]: DBERROR: opening 
/var/lib/imap/deliver.db: cyrusdb error

Sep 11 20:05:35 host lmtpunix[16846]: FATAL: lmtpd: unable to init 
duplicate delivery database

Denis

Cyrus Home Page: http://cyrusimap.web.cmu.edu/
Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html

lmtpunix: DBERROR db4: Logging region out of memory; you may need to increase its size

[Denis BUCHER]

Hello,

I know this problem has been answered on different lists, but I don't 
understand what to do to correct it ?

lmtpunix[16846]: DBERROR db4: Logging region out of memory; you may need 
to increase its size

If anyone could tell me exactly which commands or config to use it would 
be great !

Thanks a lot !

Denis

Cyrus Home Page: http://cyrusimap.web.cmu.edu/
Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html

"DBERROR: error listing log files" if only skiplist

[Marco Broglia]

I have cyrus-imapd v2.3.12p2, and no db with `berkeley' in imapd.conf. 
Then, every checkpoint period (now I have 30m), the following errors 
appears in log (3 times):

[...] ctl_cyrusdb[42037]: DBERROR: error listing log files: DB_NOTFOUND: 
No matching key/data pair found
[...]ctl_cyrusdb[42037]: DBERROR: archive /cyrus/imap/db: cyrusdb error

I try to set duplicatesuppression with berkeley and they disappeared.

I check the source and see that without any berkeley log files in 
`/cyrus/imap/db' the errors is sure.

I think that it could be easily solved, or do I miss something ?

Follows the db part of `imapd.conf':

  - annotation_db: skiplist
  - duplicate_db: skiplist (duplicatesuppression: no)
  - mboxlist_db: skiplist
  - #ptscache_db: berkeley (I don't use it)
  - seenstate_db: skiplist
  - #statuscache_db: berkeley-nosync (I think I don't use it)
  - subscription_db: flat
  - #tlscache_db: berkeley-nosync (I don't use it)

Bye.
Marco.

-- 
% Marco Broglia
% via per Vimodrone 9, I-20093 Cologno Monzese (MI)
% email: [EMAIL PROTECTED]

Cyrus Home Page: http://cyrusimap.web.cmu.edu/
Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html

Re: DBERROR - how do I recover?

[Shelley Waltz]

Blake Hudson wrote:
> You should be able to delete the deliver, annotations, and tls_sessions
> db files along with the files in /var/lib/imap/db and restart without
> any loss of data.
>
> If this does not fix the problem you likely have issue with the
> mailboxes db file. In that case, you will likely have to replace it with
> a file from /var/lib/imap/db.backup1 You will lose any new
> folders/mailboxes created since the backup was created. You can use
> reconstruct -rf to find these though
>
> --Blake
>
>  Original Message  

>> I am still in trouble on my production system - help
>>
>> Jun 23 12:57:34 chipmunk lmtpunix[4948]: DBERROR db4: fatal region error
>> detected; run recovery
>> Jun 23 12:57:34 chipmunk lmtpunix[4948]: DBERROR: dbenv->open
>> '/var/lib/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database
>> recovery
>> Jun 23 12:57:34 chipmunk lmtpunix[4948]: DBERROR: init() on berkeley
>> Jun 23 12:57:34 chipmunk lmtpunix[4948]: executed
>> Jun 23 12:57:34 chipmunk lmtpunix[4948]: DBERROR db4: environment not
>> yet
>> opened
>> Jun 23 12:57:34 chipmunk lmtpunix[4948]: DBERROR: opening
>> /var/lib/imap/deliver.db: Invalid argument
>> Jun 23 12:57:34 chipmunk lmtpunix[4948]: DBERROR: opening
>> /var/lib/imap/deliver.db: cyrusdb error
>> Jun 23 12:57:34 chipmunk lmtpunix[4948]: FATAL: lmtpd: unable to init
>> duplicate delivery database
>> Jun 23 12:57:34 chipmunk master[1691]: process 4948 exited, status 75
>> Jun 23 12:57:34 chipmunk master[1691]: service lmtpunix pid 4948 in
>> READY
>> state: terminated abnormally
>> Jun 23 12:57:34 chipmunk master[4949]: about to exec
>> /usr/lib/cyrus-imapd/lmtpd
>>
>> what can i do to recover from this problem - no mail is going through.
>>
>> thanks S
>>
>> 
>> Cyrus Home Page: http://cyrusimap.web.cmu.edu/
>> Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki
>> List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
>>
>
> 
> Cyrus Home Page: http://cyrusimap.web.cmu.edu/
> Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki
> List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
>

Thanks for this concise information, I am keeping it on file for next
time(hopefully never).

What I did and what did repair the problem was

db_recover -v -h /var/lib/imap/db




Cyrus Home Page: http://cyrusimap.web.cmu.edu/
Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html

Re: DBERROR - how do I recover?

[Alain Spineux]

On Mon, Jun 23, 2008 at 7:08 PM, Shelley Waltz <[EMAIL PROTECTED]> wrote:
> I just restarted my cyrus-imapd 2.2 and got a DBERROR.  I removed the
> duplicate db since the error persisted and this has worked in the past.
>
> I am still in trouble on my production system - help
>
> Jun 23 12:57:34 chipmunk lmtpunix[4948]: DBERROR db4: fatal region error
> detected; run recovery
> Jun 23 12:57:34 chipmunk lmtpunix[4948]: DBERROR: dbenv->open
> '/var/lib/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database
> recovery
> Jun 23 12:57:34 chipmunk lmtpunix[4948]: DBERROR: init() on berkeley
> Jun 23 12:57:34 chipmunk lmtpunix[4948]: executed
> Jun 23 12:57:34 chipmunk lmtpunix[4948]: DBERROR db4: environment not yet
> opened
> Jun 23 12:57:34 chipmunk lmtpunix[4948]: DBERROR: opening
> /var/lib/imap/deliver.db: Invalid argument

Do the dliver.db file exists ?
What are the unix right ? What are the unix right for the directory ?

> Jun 23 12:57:34 chipmunk lmtpunix[4948]: DBERROR: opening
> /var/lib/imap/deliver.db: cyrusdb error
> Jun 23 12:57:34 chipmunk lmtpunix[4948]: FATAL: lmtpd: unable to init
> duplicate delivery database
> Jun 23 12:57:34 chipmunk master[1691]: process 4948 exited, status 75
> Jun 23 12:57:34 chipmunk master[1691]: service lmtpunix pid 4948 in READY
> state: terminated abnormally
> Jun 23 12:57:34 chipmunk master[4949]: about to exec
> /usr/lib/cyrus-imapd/lmtpd
>
> what can i do to recover from this problem - no mail is going through.
>
> thanks S
>
> 
> Cyrus Home Page: http://cyrusimap.web.cmu.edu/
> Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki
> List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
>



-- 
Alain Spineux
aspineux gmail com
May the sources be with you

Cyrus Home Page: http://cyrusimap.web.cmu.edu/
Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html

Re: DBERROR - how do I recover?

[Blake Hudson]

You should be able to delete the deliver, annotations, and tls_sessions 
db files along with the files in /var/lib/imap/db and restart without 
any loss of data.

If this does not fix the problem you likely have issue with the 
mailboxes db file. In that case, you will likely have to replace it with 
a file from /var/lib/imap/db.backup1 You will lose any new 
folders/mailboxes created since the backup was created. You can use 
reconstruct -rf to find these though

--Blake

 Original Message  
Subject: DBERROR - how do I recover?
From: Shelley Waltz <[EMAIL PROTECTED]>
To: info-cyrus@lists.andrew.cmu.edu
Date: Monday, June 23, 2008 12:08:51 PM
> I just restarted my cyrus-imapd 2.2 and got a DBERROR.  I removed the
> duplicate db since the error persisted and this has worked in the past.
>
> I am still in trouble on my production system - help
>
> Jun 23 12:57:34 chipmunk lmtpunix[4948]: DBERROR db4: fatal region error
> detected; run recovery
> Jun 23 12:57:34 chipmunk lmtpunix[4948]: DBERROR: dbenv->open
> '/var/lib/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database
> recovery
> Jun 23 12:57:34 chipmunk lmtpunix[4948]: DBERROR: init() on berkeley
> Jun 23 12:57:34 chipmunk lmtpunix[4948]: executed
> Jun 23 12:57:34 chipmunk lmtpunix[4948]: DBERROR db4: environment not yet
> opened
> Jun 23 12:57:34 chipmunk lmtpunix[4948]: DBERROR: opening
> /var/lib/imap/deliver.db: Invalid argument
> Jun 23 12:57:34 chipmunk lmtpunix[4948]: DBERROR: opening
> /var/lib/imap/deliver.db: cyrusdb error
> Jun 23 12:57:34 chipmunk lmtpunix[4948]: FATAL: lmtpd: unable to init
> duplicate delivery database
> Jun 23 12:57:34 chipmunk master[1691]: process 4948 exited, status 75
> Jun 23 12:57:34 chipmunk master[1691]: service lmtpunix pid 4948 in READY
> state: terminated abnormally
> Jun 23 12:57:34 chipmunk master[4949]: about to exec
> /usr/lib/cyrus-imapd/lmtpd
>
> what can i do to recover from this problem - no mail is going through.
>
> thanks S
>
> 
> Cyrus Home Page: http://cyrusimap.web.cmu.edu/
> Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki
> List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
>   


Cyrus Home Page: http://cyrusimap.web.cmu.edu/
Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html

DBERROR - how do I recover?

[Shelley Waltz]

I just restarted my cyrus-imapd 2.2 and got a DBERROR.  I removed the
duplicate db since the error persisted and this has worked in the past.

I am still in trouble on my production system - help

Jun 23 12:57:34 chipmunk lmtpunix[4948]: DBERROR db4: fatal region error
detected; run recovery
Jun 23 12:57:34 chipmunk lmtpunix[4948]: DBERROR: dbenv->open
'/var/lib/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database
recovery
Jun 23 12:57:34 chipmunk lmtpunix[4948]: DBERROR: init() on berkeley
Jun 23 12:57:34 chipmunk lmtpunix[4948]: executed
Jun 23 12:57:34 chipmunk lmtpunix[4948]: DBERROR db4: environment not yet
opened
Jun 23 12:57:34 chipmunk lmtpunix[4948]: DBERROR: opening
/var/lib/imap/deliver.db: Invalid argument
Jun 23 12:57:34 chipmunk lmtpunix[4948]: DBERROR: opening
/var/lib/imap/deliver.db: cyrusdb error
Jun 23 12:57:34 chipmunk lmtpunix[4948]: FATAL: lmtpd: unable to init
duplicate delivery database
Jun 23 12:57:34 chipmunk master[1691]: process 4948 exited, status 75
Jun 23 12:57:34 chipmunk master[1691]: service lmtpunix pid 4948 in READY
state: terminated abnormally
Jun 23 12:57:34 chipmunk master[4949]: about to exec
/usr/lib/cyrus-imapd/lmtpd

what can i do to recover from this problem - no mail is going through.

thanks S


Cyrus Home Page: http://cyrusimap.web.cmu.edu/
Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html

DBERROR: error committing seen txn; seen state lost: cyrusdb error

[Martin Bachem]

Hello Cyrus imap friends ;)

I have a very annoying and highly recurring problem with a cyrus imap mailbox 
system:

db /var/imap/user/c/cc.seen, inconsistent pre-checkpoint, bailing out
DBERROR: error committing seen txn; seen state lost: cyrusdb error


I run the cyrus imap server with a lot of clients logged in using the same 
user, so everyone is working with the same (very big) imap archive.
I 'solve' the problem by restoring an old cc.seen file, but it happens again 
and again.
I already updated my 2.2.13 cryus to 2.3.9, and than to 2.3.11 to see if it has 
been improved, but it did not ;(

is anyone able to help me?

greetings, Martin

-- 
Der GMX SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen! 
Ideal für Modem und ISDN: http://www.gmx.net/de/go/smartsurfer

Cyrus Home Page: http://cyrusimap.web.cmu.edu/
Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html

ctl_cyrusdb - DBERROR db4

[Torsten Bunde]

Hi @all,

I've got a question about Cyrus where I didn't even find a solution with
google, etc. until now.

We are using a Cyrus server here that causes some problems sometimes and
we don't know why. We are able to repair this but we would like to know
why this happens.

We are using

- SUSE Linux Enterprise Server 9
- Cyrus 2.2.3

The first problem is, that there are sometimes database errors because
of wrong user rights. After a rotation the user cyrus is not allowed to
write in same files because they are owned by root. But this is not the
main problem.

Today in the morning the server logfiles had the following messages

Jan 17 06:00:01 zeus ctl_cyrusdb[5101]: DBERROR db4: Log sequence error:
page LSN 7 1172797; previous LSN 17 2099307
Jan 17 06:00:01 zeus ctl_cyrusdb[5101]: DBERROR db4: Recovery function
for LSN 7 1148884 failed on forward pass
Jan 17 06:00:01 zeus ctl_cyrusdb[5101]: DBERROR db4: PANIC: Invalid argument
Jan 17 06:00:01 zeus ctl_cyrusdb[5101]: DBERROR: critical database situation
Jan 17 06:00:01 zeus idled[5102]: DBERROR db4: PANIC: fatal region error
detected; run recovery
Jan 17 06:00:01 zeus idled[5102]: DBERROR: critical database situation
Jan 17 06:00:02 zeus ctl_cyrusdb[5104]: DBERROR db4: PANIC: fatal region
error detected; run recovery
Jan 17 06:00:02 zeus ctl_cyrusdb[5104]: DBERROR: critical database situation
Jan 17 06:00:04 zeus lmtpunix[5119]: DBERROR db4: PANIC: fatal region
error detected; run recovery
Jan 17 06:00:04 zeus lmtpunix[5119]: DBERROR: critical database situation
[...]

Does anyone has any idea what happened here?

Thanks
- Torsten Bunde

Cyrus Home Page: http://cyrusimap.web.cmu.edu/
Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html

Re: Help! lmtpd infinite loops with DBERROR

[Naoyuki Tai]

[EMAIL PROTECTED] wrote:
> Hello,
>
> I have a major problem with the mail delivery with LMTP.
>
> In short,
>
> Dec 16 09:59:23 luxor lmtp[10425]: FATAL: couldn't exec() sendmail
> Dec 16 09:59:23 luxor lmtp[10424]: DBERROR db4: Locker does not exist
> Dec 16 09:59:23 luxor lmtp[10424]: DBERROR: error fetching
> <[EMAIL PROTECTED]>: Invalid argument
> Dec 16 09:59:23 luxor lmtp[10424]: duplicate_check: error looking up
> <[EMAIL PROTECTED]>/user.ntai: cyrusdb error
> Dec 16 09:59:23 luxor lmtp[10424]: IOERROR: opening
> /servers/cyrus/mail/stage./10424-1197817163-0: No such file or directory
> Dec 16 09:59:23 luxor lmtp[10424]: IOERROR: error unlinking file
> /servers/cyrus/mail/stage./10424-1197817163-0: No such file or directory
>
> Then, the lmtpd process takes 100% cpu.
>
> The server has been running without a trouble for years, and the config
> has not been changed at all.
>
> The operating system is FreeBSD 6.2-RELEASE and has been stable for
> months, and the problem started a couple of days ago.
>
> If you could give me any clue, appriciated a lot.
>
> --
> Naoyuki "Tai" Tai, ntai a t smartfruit d o t com
>
>   

I took a look at the source code and realized that the reason is 
"sendmail" is not pointing to the right one, and the sieve script did 
not see any reject until now.

--
Naoyuki "Tai" Tai, ntai a t smartfruit d o t com




Cyrus Home Page: http://cyrusimap.web.cmu.edu/
Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html

Re: Help! lmtpd infinite loops with DBERROR

[Alain Spineux]

On Dec 16, 2007 4:22 PM,  <[EMAIL PROTECTED]> wrote:
> Hello,
>
> I have a major problem with the mail delivery with LMTP.
>
> In short,
>
> Dec 16 09:59:23 luxor lmtp[10425]: FATAL: couldn't exec() sendmail

Look for option "sendmail" in imapd.conf (man imapd.conf)
sendmail is used by sieve to forward emails


> Dec 16 09:59:23 luxor lmtp[10424]: DBERROR db4: Locker does not exist
> Dec 16 09:59:23 luxor lmtp[10424]: DBERROR: error fetching
> <[EMAIL PROTECTED]>: Invalid argument
> Dec 16 09:59:23 luxor lmtp[10424]: duplicate_check: error looking up
> <[EMAIL PROTECTED]>/user.ntai: cyrusdb error
> Dec 16 09:59:23 luxor lmtp[10424]: IOERROR: opening
> /servers/cyrus/mail/stage./10424-1197817163-0: No such file or directory
> Dec 16 09:59:23 luxor lmtp[10424]: IOERROR: error unlinking file
> /servers/cyrus/mail/stage./10424-1197817163-0: No such file or directory
>
> Then, the lmtpd process takes 100% cpu.
>
> The server has been running without a trouble for years, and the config
> has not been changed at all.
>
> The operating system is FreeBSD 6.2-RELEASE and has been stable for
> months, and the problem started a couple of days ago.
>
> If you could give me any clue, appriciated a lot.
>
> --
> Naoyuki "Tai" Tai, ntai a t smartfruit d o t com
>
>
> 
> Cyrus Home Page: http://cyrusimap.web.cmu.edu/
> Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki
> List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
>



-- 
Alain Spineux
aspineux gmail com
May the sources be with you

Cyrus Home Page: http://cyrusimap.web.cmu.edu/
Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html

Help! lmtpd infinite loops with DBERROR

[ntai]

Hello,

I have a major problem with the mail delivery with LMTP.

In short,

Dec 16 09:59:23 luxor lmtp[10425]: FATAL: couldn't exec() sendmail
Dec 16 09:59:23 luxor lmtp[10424]: DBERROR db4: Locker does not exist
Dec 16 09:59:23 luxor lmtp[10424]: DBERROR: error fetching
<[EMAIL PROTECTED]>: Invalid argument
Dec 16 09:59:23 luxor lmtp[10424]: duplicate_check: error looking up
<[EMAIL PROTECTED]>/user.ntai: cyrusdb error
Dec 16 09:59:23 luxor lmtp[10424]: IOERROR: opening
/servers/cyrus/mail/stage./10424-1197817163-0: No such file or directory
Dec 16 09:59:23 luxor lmtp[10424]: IOERROR: error unlinking file
/servers/cyrus/mail/stage./10424-1197817163-0: No such file or directory

Then, the lmtpd process takes 100% cpu.

The server has been running without a trouble for years, and the config
has not been changed at all.

The operating system is FreeBSD 6.2-RELEASE and has been stable for
months, and the problem started a couple of days ago.

If you could give me any clue, appriciated a lot.

--
Naoyuki "Tai" Tai, ntai a t smartfruit d o t com



Cyrus Home Page: http://cyrusimap.web.cmu.edu/
Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html

Re: DBERROR

[Bron Gondwana]

On Thu, Dec 06, 2007 at 05:56:29PM +0100, Alain Spineux wrote:
> On Dec 6, 2007 5:03 PM, Jeff Blaine <[EMAIL PROTECTED]> wrote:
> > bash-2.05# ls -l *db
> > -rw---   1 cyrusmail 144 Dec  5 16:56 annotations.db
> > -rw---   1 cyrusmail 144 Dec  5 16:56 deliver.db
> > -rw---   1 cyrusmail 144 Dec  5 16:56 mailboxes.db
> 
> 144 bytes !  Not a lot !

It is precisely the size of an empty skiplist file.

Cyrus Home Page: http://cyrusimap.web.cmu.edu/
Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html

Re: DBERROR

[Jeff Blaine]

There are no mailboxes.  This was a brand new install that
I have left untouched until I figure out the cause of this
error.

If it's throwing an error because there is nothing in the
databases yet, I consider that a bug.

Alain Spineux wrote:
> On Dec 6, 2007 5:03 PM, Jeff Blaine <[EMAIL PROTECTED]> wrote:
>> bash-2.05# ls -l *db
>> -rw---   1 cyrusmail 144 Dec  5 16:56 annotations.db
>> -rw---   1 cyrusmail 144 Dec  5 16:56 deliver.db
>> -rw---   1 cyrusmail 144 Dec  5 16:56 mailboxes.db
> 
> 144 bytes !  Not a lot !
> 
> If you have a backup, try to restore from it (make a copy of *.db and
> db/* files) before :-)
> If not try to repair using the log files (in db/*), but db_tools are
> very user unfriendly :-(
> Or remove theses files and recreate your mailboxes using cyradm.
> 
> 
> 
>> db:
>> total 29618
>> -rw---   1 cyrusmail8192 Dec  6 10:57 __db.001
>> -rw---   1 cyrusmail  663552 Dec  5 16:56 __db.002
>> -rw---   1 cyrusmail   98304 Dec  5 16:56 __db.003
>> -rw---   1 cyrusmail 21061632 Dec  5 16:56 __db.004
>> -rw---   1 cyrusmail   32768 Dec  5 16:56 __db.005
>> -rw---   1 cyrusmail   4 Dec  5 16:56 skipstamp
>> bash-2.05#
>>
>>
>> Alain Spineux wrote:
>>> On Dec 5, 2007 11:38 PM, Jeff Blaine <[EMAIL PROTECTED]> wrote:
>>>> This is a brand new install.  After running tools/mkimap and
>>>> starting master, I get this.  What's the deal?
>>>
>>>
>>> look for files :
>>>
>>> # ll /var/lib/imap/*.db
>>> -rw---  1 cyrus mail   144 Nov 28 11:01 /var/lib/imap/annotations.db
>>> -rw-r--r--  1 cyrus mail 16384 Dec  6 08:01 /var/lib/imap/deliver.db
>>> -rw---  1 cyrus mail  3760 Nov 28 11:01 /var/lib/imap/mailboxes.db
>>> -rw---  1 cyrus mail  8192 Dec  6 04:01 /var/lib/imap/tls_sessions.db
>>>
>>> look for access rights.
>>>
>>>> Dec  5 17:26:57 alberta.foo.com ctl_cyrusdb[3713]: DBERROR: error
>>>> listing log files: DB_NOTFOUND: No matching key/data pair found
>>>> Dec  5 17:26:57 alberta.foo.com ctl_cyrusdb[3713]: DBERROR: archive
>>>> /var/imap/db: cyrusdb error
>>>> Dec  5 17:26:57 alberta.foo.com ctl_cyrusdb[3713]: DBERROR: error
>>>> listing log files: DB_NOTFOUND: No matching key/data pair found
>>>> Dec  5 17:26:57 alberta.foo.com ctl_cyrusdb[3713]: DBERROR: archive
>>>> /var/imap/db: cyrusdb error
>>>>
>>>> 
>>>> Cyrus Home Page: http://cyrusimap.web.cmu.edu/
>>>> Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki
>>>> List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
>>>>
>>>
>>>
> 
> 
> 

Cyrus Home Page: http://cyrusimap.web.cmu.edu/
Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html

Re: DBERROR

[Alain Spineux]

On Dec 6, 2007 5:03 PM, Jeff Blaine <[EMAIL PROTECTED]> wrote:
> bash-2.05# ls -l *db
> -rw---   1 cyrusmail 144 Dec  5 16:56 annotations.db
> -rw---   1 cyrusmail 144 Dec  5 16:56 deliver.db
> -rw---   1 cyrusmail 144 Dec  5 16:56 mailboxes.db

144 bytes !  Not a lot !

If you have a backup, try to restore from it (make a copy of *.db and
db/* files) before :-)
If not try to repair using the log files (in db/*), but db_tools are
very user unfriendly :-(
Or remove theses files and recreate your mailboxes using cyradm.



>
> db:
> total 29618
> -rw---   1 cyrusmail8192 Dec  6 10:57 __db.001
> -rw---   1 cyrusmail  663552 Dec  5 16:56 __db.002
> -rw---   1 cyrusmail   98304 Dec  5 16:56 __db.003
> -rw---   1 cyrusmail 21061632 Dec  5 16:56 __db.004
> -rw---   1 cyrusmail   32768 Dec  5 16:56 __db.005
> -rw---   1 cyrusmail   4 Dec  5 16:56 skipstamp
> bash-2.05#
>
>
> Alain Spineux wrote:
> > On Dec 5, 2007 11:38 PM, Jeff Blaine <[EMAIL PROTECTED]> wrote:
> >> This is a brand new install.  After running tools/mkimap and
> >> starting master, I get this.  What's the deal?
> >
> >
> >
> > look for files :
> >
> > # ll /var/lib/imap/*.db
> > -rw---  1 cyrus mail   144 Nov 28 11:01 /var/lib/imap/annotations.db
> > -rw-r--r--  1 cyrus mail 16384 Dec  6 08:01 /var/lib/imap/deliver.db
> > -rw---  1 cyrus mail  3760 Nov 28 11:01 /var/lib/imap/mailboxes.db
> > -rw---  1 cyrus mail  8192 Dec  6 04:01 /var/lib/imap/tls_sessions.db
> >
> > look for access rights.
> >
> >> Dec  5 17:26:57 alberta.foo.com ctl_cyrusdb[3713]: DBERROR: error
> >> listing log files: DB_NOTFOUND: No matching key/data pair found
> >> Dec  5 17:26:57 alberta.foo.com ctl_cyrusdb[3713]: DBERROR: archive
> >> /var/imap/db: cyrusdb error
> >> Dec  5 17:26:57 alberta.foo.com ctl_cyrusdb[3713]: DBERROR: error
> >> listing log files: DB_NOTFOUND: No matching key/data pair found
> >> Dec  5 17:26:57 alberta.foo.com ctl_cyrusdb[3713]: DBERROR: archive
> >> /var/imap/db: cyrusdb error
> >>
> >> 
> >> Cyrus Home Page: http://cyrusimap.web.cmu.edu/
> >> Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki
> >> List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
> >>
> >
> >
> >
>



-- 
Alain Spineux
aspineux gmail com
May the sources be with you

Cyrus Home Page: http://cyrusimap.web.cmu.edu/
Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html

Re: DBERROR

[Jeff Blaine]

bash-2.05# ls -l *db
-rw---   1 cyrusmail 144 Dec  5 16:56 annotations.db
-rw---   1 cyrusmail 144 Dec  5 16:56 deliver.db
-rw---   1 cyrusmail 144 Dec  5 16:56 mailboxes.db

db:
total 29618
-rw---   1 cyrusmail8192 Dec  6 10:57 __db.001
-rw---   1 cyrusmail  663552 Dec  5 16:56 __db.002
-rw---   1 cyrusmail   98304 Dec  5 16:56 __db.003
-rw---   1 cyrusmail 21061632 Dec  5 16:56 __db.004
-rw---   1 cyrusmail   32768 Dec  5 16:56 __db.005
-rw---   1 cyrusmail   4 Dec  5 16:56 skipstamp
bash-2.05#

Alain Spineux wrote:
> On Dec 5, 2007 11:38 PM, Jeff Blaine <[EMAIL PROTECTED]> wrote:
>> This is a brand new install.  After running tools/mkimap and
>> starting master, I get this.  What's the deal?
> 
> 
> 
> look for files :
> 
> # ll /var/lib/imap/*.db
> -rw---  1 cyrus mail   144 Nov 28 11:01 /var/lib/imap/annotations.db
> -rw-r--r--  1 cyrus mail 16384 Dec  6 08:01 /var/lib/imap/deliver.db
> -rw---  1 cyrus mail  3760 Nov 28 11:01 /var/lib/imap/mailboxes.db
> -rw---  1 cyrus mail  8192 Dec  6 04:01 /var/lib/imap/tls_sessions.db
> 
> look for access rights.
> 
>> Dec  5 17:26:57 alberta.foo.com ctl_cyrusdb[3713]: DBERROR: error
>> listing log files: DB_NOTFOUND: No matching key/data pair found
>> Dec  5 17:26:57 alberta.foo.com ctl_cyrusdb[3713]: DBERROR: archive
>> /var/imap/db: cyrusdb error
>> Dec  5 17:26:57 alberta.foo.com ctl_cyrusdb[3713]: DBERROR: error
>> listing log files: DB_NOTFOUND: No matching key/data pair found
>> Dec  5 17:26:57 alberta.foo.com ctl_cyrusdb[3713]: DBERROR: archive
>> /var/imap/db: cyrusdb error
>>
>> 
>> Cyrus Home Page: http://cyrusimap.web.cmu.edu/
>> Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki
>> List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
>>
> 
> 
> 

Cyrus Home Page: http://cyrusimap.web.cmu.edu/
Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html

Re: DBERROR

[Alain Spineux]

On Dec 5, 2007 11:38 PM, Jeff Blaine <[EMAIL PROTECTED]> wrote:
> This is a brand new install.  After running tools/mkimap and
> starting master, I get this.  What's the deal?



look for files :

# ll /var/lib/imap/*.db
-rw---  1 cyrus mail   144 Nov 28 11:01 /var/lib/imap/annotations.db
-rw-r--r--  1 cyrus mail 16384 Dec  6 08:01 /var/lib/imap/deliver.db
-rw---  1 cyrus mail  3760 Nov 28 11:01 /var/lib/imap/mailboxes.db
-rw---  1 cyrus mail  8192 Dec  6 04:01 /var/lib/imap/tls_sessions.db

look for access rights.

>
> Dec  5 17:26:57 alberta.foo.com ctl_cyrusdb[3713]: DBERROR: error
> listing log files: DB_NOTFOUND: No matching key/data pair found
> Dec  5 17:26:57 alberta.foo.com ctl_cyrusdb[3713]: DBERROR: archive
> /var/imap/db: cyrusdb error
> Dec  5 17:26:57 alberta.foo.com ctl_cyrusdb[3713]: DBERROR: error
> listing log files: DB_NOTFOUND: No matching key/data pair found
> Dec  5 17:26:57 alberta.foo.com ctl_cyrusdb[3713]: DBERROR: archive
> /var/imap/db: cyrusdb error
>
> 
> Cyrus Home Page: http://cyrusimap.web.cmu.edu/
> Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki
> List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
>



-- 
Alain Spineux
aspineux gmail com
May the sources be with you

Cyrus Home Page: http://cyrusimap.web.cmu.edu/
Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html

DBERROR

[Jeff Blaine]

This is a brand new install.  After running tools/mkimap and
starting master, I get this.  What's the deal?

Dec  5 17:26:57 alberta.foo.com ctl_cyrusdb[3713]: DBERROR: error
listing log files: DB_NOTFOUND: No matching key/data pair found
Dec  5 17:26:57 alberta.foo.com ctl_cyrusdb[3713]: DBERROR: archive
/var/imap/db: cyrusdb error
Dec  5 17:26:57 alberta.foo.com ctl_cyrusdb[3713]: DBERROR: error
listing log files: DB_NOTFOUND: No matching key/data pair found
Dec  5 17:26:57 alberta.foo.com ctl_cyrusdb[3713]: DBERROR: archive
/var/imap/db: cyrusdb error


Cyrus Home Page: http://cyrusimap.web.cmu.edu/
Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html

Re: cyrus-imapd: DBERROR db4: Database handles still open at env

[Arnau Bria]

On Mon, 08 Oct 2007 12:14:15 +0200
Rudy Gevaert wrote:

Hi rudy,


> > Oct  5 18:22:21 afrodita pop3[14410]: DBERROR db4: Database handles still 
> > open at environment close
> > Oct  5 18:22:21 afrodita pop3[14410]: DBERROR db4: Open database handle: 
> > /var/imap/tls_sessions.db

> you can delete that db file, it will be recreated.

I've done so, but it still shows the error
afrodita imap # date
lun oct  8 12:36:03 CEST 2007
afrodita imap # ls -lsa tls_sessions.db
8 -rw-r- 1 cyrus cyrus 8192 oct  8 12:35 tls_sessions.db

> M
Thansk for your reply,
Arnau
 
PS: I don't know what's happening with my gmail account, I've sent this
reply but I don't see it in list archive. So, I'd like to say sorry if
you see this mail twice. I'm gonna unsuscribe from gmail.

Cyrus Home Page: http://cyrusimap.web.cmu.edu/
Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html

Re: cyrus-imapd: DBERROR db4: Database handles still open at env

[Rudy Gevaert]

Arnau Bria wrote:
> Hi,
> 
> I've posted my problem in gentoo forums, but after few days I still
> have no response, so I decide to ask here, sorry for the cross-posting.
> 
> I've updated my cyrus-imapd and now I'm not able to make it work again.
> Every time I try to fetch my mail (using pop3) I get an error in my MUA:
> 
> Error occurred while processing mail:
> -ERR [SYS/PERM] Error initializing TLS
> 
> 
> and I see this in log files:
> 
> Oct  5 18:22:21 afrodita pop3[14410]: DBERROR db4: Database handles still 
> open at environment close
> Oct  5 18:22:21 afrodita pop3[14410]: DBERROR db4: Open database handle: 
> /var/imap/tls_sessions.db

you can delete that db file, it will be recreated.

M

-- 
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
Rudy Gevaert  [EMAIL PROTECTED]  tel:+32 9 264 4734
Directie ICT, afd. Infrastructuur ICT Department, Infrastructure office
Groep SystemenSystems group
Universiteit Gent Ghent University
Krijgslaan 281, gebouw S9, 9000 Gent, Belgie   www.UGent.be
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --

Cyrus Home Page: http://cyrusimap.web.cmu.edu/
Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html

cyrus-imapd: DBERROR db4: Database handles still open at env

[Arnau Bria]

Hi,

I've posted my problem in gentoo forums, but after few days I still
have no response, so I decide to ask here, sorry for the cross-posting.

I've updated my cyrus-imapd and now I'm not able to make it work again.
Every time I try to fetch my mail (using pop3) I get an error in my MUA:

Error occurred while processing mail:
-ERR [SYS/PERM] Error initializing TLS


and I see this in log files:

Oct  5 18:22:21 afrodita pop3[14410]: DBERROR db4: Database handles still open 
at environment close
Oct  5 18:22:21 afrodita pop3[14410]: DBERROR db4: Open database handle: 
/var/imap/tls_sessions.db


This is my imapd.conf:


# grep . /etc/imapd.conf|grep -v "^#"
configdirectory:/var/imap
defaultpartition: default
partition-default:  /var/spool/imap
partition-news: /var/spool/cyrus/news
newsspool: /var/spool/news
altnamespace: no
unixhierarchysep: no
lmtp_downcase_rcpt: yes
sievedir:   /var/imap/sieve
tls_ca_path:/etc/ssl/postfix
tls_cert_file: /etc/ssl/postfix/newcert.pem
tls_key_file:  /etc/ssl/postfix/newkey.pem
tls_ca_file: /etc/ssl/postfix/cacert.pem
admins: cyrus
hashimapspool:  yes
allowanonymouslogin:no
allowplaintext: yes
popminpoll: 1
autocreatequota: 0
umask: 027
sasl_mech_list: PLAIN
sasl_minimum_layer: 0
sasl_pwcheck_method: saslauthd
sasl_auxprop_plugin: sasldb
sasl_auto_transition: no
tls_session_timeout: 1440
tls_cipher_list: TLSv1:SSLv3:SSLv2:!NULL:!EXPORT:!DES:!LOW:@STRENGTH


Notice I'm using postfix certs, cause I used:


#tls_cert_file: /etc/ssl/cyrus/newcert.pem
#tls_key_file:  /etc/ssl/cyrus/newkey.pem
#tls_ca_file: /etc/ssl/certs/cyrus-imapd-ca.pem


and now /etc/ssl/certs/cyrus-imapd-ca.pem does not exist, but I'm not sure if 
this is really important, we're talking about self-generated self-signed 
certs... I can generate new ones, but old were fine...

And those are cyrus' use flags:

Código:

[ebuild   R   ] net-mail/cyrus-imapd-2.2.13-r1  USE="ssl tcpd -afs -drac -idled 
-kerberos -pam -snmp -unsupported_8bit"



TIA,
-- 
Arnau Bria
http://blog.emergetux.net
Bombing for peace is like fucking for virginity

Cyrus Home Page: http://cyrusimap.web.cmu.edu/
Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html

syncserver DBERROR

[Per olof Ljungmark]

Hi,

After upgrade 2.3.8 -> 2.3.9 i see this in the log although everything 
seems normal. We're using skiplist or flat for all databases so I'm 
assuming the below it's just because Berkeley is compiled in but not 
used? Is there way to get rid of the message without recompiling cyrus?

/var/imap/db exists btw...

Sep 15 02:43:22 miracle syncserver[36301]: DBERROR db4: no absolute path 
for the current directory: No such file or directory
Sep 15 02:43:22 miracle syncserver[36301]: DBERROR db4: no absolute path 
for the current directory: No such file or directory
Sep 15 02:43:22 miracle syncserver[36301]: DBERROR: dbenv->open 
'/var/imap/db' failed: No such file or directory
Sep 15 02:43:22 miracle syncserver[36301]: DBERROR: init() on berkeley

Thanks,

Per olof

Cyrus Home Page: http://cyrusimap.web.cmu.edu/
Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html

Re: lately get DBERROR db4: PANIC

[Andrew Morgan]

On Fri, 14 Sep 2007, Björn Fahller wrote:


Hello list,

Lately I get the below error situations almost daily. I cannot see any
particular action that causes them. They just do. Perhaps once per day. Once
the error situation occurrs, I have to "kill -9" a number of stuck processes,
run ctl_cyrusdb -r, and recovery. After that, I can restart cyrus-imapd, and
it runs nicely until next time, which can be after a day or two, or only a
few hours.

The installation is cyrus-imapd-2.2.13 on a 2.6.22.1 linux kernel.

The installation is rediculously small with only 5 users.

Neither ctl_cyrusdb nor recover, tells what errors it corrects.

What can cause the below, and what can I do to avoid it?
  _
/Bjorn


I know this doesn't actually solve the Berkeley DB problem you are seeing, 
but have you considered switching your Cyrus databases from Berkeley DB to 
skiplist?  Skiplist seems to be much more reliable.  The conversion 
process is relatively simple and should take only 10 minutes of downtime.


Andy
Cyrus Home Page: http://cyrusimap.web.cmu.edu/
Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html

lately get DBERROR db4: PANIC

[Björn Fahller]

Hello list,

Lately I get the below error situations almost daily. I cannot see any 
particular action that causes them. They just do. Perhaps once per day. Once 
the error situation occurrs, I have to "kill -9" a number of stuck processes, 
run ctl_cyrusdb -r, and recovery. After that, I can restart cyrus-imapd, and 
it runs nicely until next time, which can be after a day or two, or only a 
few hours.

The installation is cyrus-imapd-2.2.13 on a 2.6.22.1 linux kernel.

The installation is rediculously small with only 5 users.

Neither ctl_cyrusdb nor recover, tells what errors it corrects.

What can cause the below, and what can I do to avoid it?
   _
/Bjorn

Sep 14 13:41:36 quetzalcoatlus master[23314]: about to 
exec /usr/lib/cyrus/imapd
Sep 14 13:41:36 quetzalcoatlus master[23315]: about to 
exec /usr/lib/cyrus/lmtpd
Sep 14 13:41:36 quetzalcoatlus imap[23314]: DBERROR db4: PANIC: fatal region 
error detected; run recovery
Sep 14 13:41:36 quetzalcoatlus imap[23314]: DBERROR: critical database 
situation
Sep 14 13:41:36 quetzalcoatlus lmtpunix[23315]: DBERROR db4: PANIC: fatal 
region error detected; run recovery
Sep 14 13:41:36 quetzalcoatlus lmtpunix[23315]: DBERROR: critical database 
situation
Sep 14 13:41:36 quetzalcoatlus master[16517]: process 23314 exited, status 75
Sep 14 13:41:36 quetzalcoatlus master[16517]: service imap pid 23314 in READY 
state: terminated abnormally
Sep 14 13:41:36 quetzalcoatlus master[23316]: about to 
exec /usr/lib/cyrus/imapd
Sep 14 13:41:36 quetzalcoatlus master[16517]: process 23315 exited, status 75
Sep 14 13:41:36 quetzalcoatlus master[16517]: service lmtpunix pid 23315 in 
READY state: terminated abnormally
Sep 14 13:41:36 quetzalcoatlus master[23317]: about to 
exec /usr/lib/cyrus/lmtpd
Sep 14 13:41:36 quetzalcoatlus imap[23316]: DBERROR db4: PANIC: fatal region 
error detected; run recovery
Sep 14 13:41:36 quetzalcoatlus imap[23316]: DBERROR: critical database 
situation
Sep 14 13:41:36 quetzalcoatlus lmtpunix[23317]: DBERROR db4: PANIC: fatal 
region error detected; run recovery
Sep 14 13:41:36 quetzalcoatlus lmtpunix[23317]: DBERROR: critical database 
situation
Sep 14 13:41:36 quetzalcoatlus master[16517]: process 23316 exited, status 75
Sep 14 13:41:36 quetzalcoatlus master[16517]: service imap pid 23316 in READY 
state: terminated abnormally
Sep 14 13:41:36 quetzalcoatlus master[16517]: process 23317 exited, status 75
Sep 14 13:41:36 quetzalcoatlus master[16517]: service lmtpunix pid 23317 in 
READY state: terminated abnormally
Sep 14 13:41:36 quetzalcoatlus master[23318]: about to 
exec /usr/lib/cyrus/imapd
Sep 14 13:41:36 quetzalcoatlus master[23319]: about to 
exec /usr/lib/cyrus/lmtpd
Sep 14 13:41:36 quetzalcoatlus imap[23318]: DBERROR db4: PANIC: fatal region 
error detected; run recovery
Sep 14 13:41:36 quetzalcoatlus imap[23318]: DBERROR: critical database 
situation
Sep 14 13:41:36 quetzalcoatlus lmtpunix[23319]: DBERROR db4: PANIC: fatal 
region error detected; run recovery
Sep 14 13:41:36 quetzalcoatlus lmtpunix[23319]: DBERROR: critical database 
situation

Cyrus Home Page: http://cyrusimap.web.cmu.edu/
Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html

"DBERROR db4: PANIC: fatal region error detected; run recovery" error

[Somnath_Pal]

 

Hi list,

 

I am running postfix-2.2.10 with cyrus-imap-2.2.12 on Redhat Enterprise
Linux 4

update 4 on s390x(IBM Z series). After installing cyrus-imap & I am
receving

the following error in /var/log/maillog :

 


---

Sep 12 13:09:50 linux08 imaps[16727]: DBERROR: critical database
situation

Sep 12 13:09:50 linux08 master[16728]: about to exec

/usr/lib64/cyrus-imapd/pop3d

Sep 12 13:09:50 linux08 pop3[16728]: DBERROR: invalid berkeley_cachesize
value,

using internal default

Sep 12 13:09:50 linux08 pop3[16728]: DBERROR db4: PANIC: fatal region
error

detected; run recovery

Sep 12 13:09:50 linux08 pop3[16728]: DBERROR: critical database
situation

Sep 12 13:09:50 linux08 master[16729]: about to exec

/usr/lib64/cyrus-imapd/pop3d

Sep 12 13:09:50 linux08 pop3s[16729]: DBERROR: invalid
berkeley_cachesize

value, using internal default

Sep 12 13:09:50 linux08 pop3s[16729]: DBERROR db4: PANIC: fatal region
error

detected; run recovery

Sep 12 13:09:50 linux08 pop3s[16729]: DBERROR: critical database
situation




 

I tried with "ctl_cyrusdb -r" but it did not work.

 


--

My /etc/cyrus.conf -

 

 

# standard standalone server implementation

 

START {

  # do not delete this entry!

  recover  cmd="ctl_cyrusdb -r"

 

  # this is only necessary if using idled for IMAP IDLE

#  idled cmd="idled"

}

 

# UNIX sockets start with a slash and are put into /var/lib/imap/sockets

SERVICES {

  # add or remove based on preferences

  imapcmd="imapd" listen="imap" prefork=5

  imaps  cmd="imapd -s" listen="imaps" prefork=1

  pop3cmd="pop3d" listen="pop3" prefork=3

  pop3s  cmd="pop3d -s" listen="pop3s" prefork=1

  sieve   cmd="timsieved" listen="sieve" prefork=0

 

  # these are only necessary if receiving/exporting usenet via NNTP

#  nntp  cmd="nntpd" listen="nntp" prefork=3

#  nntpscmd="nntpd -s" listen="nntps"
prefork=1

 

  # at least one LMTP is required for delivery

#  lmtp  cmd="lmtpd" listen="lmtp" prefork=0

  lmtpunixcmd="lmtpd" listen="/var/lib/imap/socket/lmtp"
prefork=1

 

  # this is only necessary if using notifications

#  notify   cmd="notifyd"
listen="/var/lib/imap/socket/notify" proto="udp" prefork=1

}

 

EVENTS {

  # this is required

#  checkpoint cmd="ctl_cyrusdb -c" period=30

  checkpointcmd="ctl_cyrusdb -c" period=5

 

  # this is only necessary if using duplicate delivery suppression,

  # Sieve or NNTP

  delprune   cmd="cyr_expire -E 3" at=0400

 

  # this is only necessary if caching TLS sessions

  tlsprune cmd="tls_prune" at=0400

}

 


---

My /etc/imapd.conf -

 

configdirectory: /var/lib/imap

partition-default: /var/spool/imap

admins: cyrus

sievedir: /var/lib/imap/sieve

sendmail: /usr/sbin/sendmail

hashimapspool: true

sasl_pwcheck_method: saslauthd

sasl_mech_list: PLAIN

tls_cert_file: /usr/share/ssl/certs/cyrus-imapd.pem

tls_key_file: /usr/share/ssl/certs/cyrus-imapd.pem

tls_ca_file: /usr/share/ssl/certs/ca-bundle.crt

 


--

 

Pls suggest how to fix this problem. My cyrus imap server is not coming
up at

all.

 

Thanks in advance,

Somnath



DISCLAIMER:
This email (including any attachments) is intended for the sole use of the 
intended recipient/s and may contain material that is CONFIDENTIAL AND PRIVATE 
COMPANY INFORMATION. Any review or reliance by others or copying or 
distribution or forwarding of any or all of the contents in this message is 
STRICTLY PROHIBITED. If you are not the intended recipient, please contact the 
sender by email and delete all copies; your cooperation in this regard is 
appreciated.

Cyrus Home Page: http://cyrusimap.web.cmu.edu/
Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html

Rw: DBERROR "strange character": db4

[Arnau Bria]

HI,

first of all, apologies for breaking the threat, but I did not receive
my question.

Second, I have solved my problem, but I've lost all my mail, and I have
a question about what has happenend.

Third, list archieve does not work. I tried to contact webmaster, but
got no response.

Let's go with my explanation:

Here's what I have done:
I ignored strange character in error message and looked for similar
errors in gentoo forums and google, found many:
http://forums.gentoo.org/viewtopic-t-482191-highlight-dberror.html
http://forums.gentoo.org/viewtopic-t-499634-highlight-dberror.html
...

My first try was recovering /var/imap/db/* so I did:
db4.3_recover log.05

which said something about ignoring that log and looked for
log.0006 which did not exist, so I exited.

When I saw I could not recover (or I did not know how) my db, I decided
to delete all db:
  687  rm /var/imap/*.db 
  688  rm /var/imap/db*/* 

And restart cyrus. Fianlly, cyrus started fine.
So, and here comes my error, I flushed my postfix queue (postqueue -f)
and all mails were recieved by cyrus, but when I tried to recover my
mail with MUA (sylpheed) I got a "Unable to locate maildrop:
Mailbox does not exist" or something similar...

So, I start playing with imtest and checked if my user was correctly
created etc...

imtest -m login -a arnau localhost

C: C01 CAPABILITY
S: * CAPABILITY IMAP4 IMAP4rev1 ACL QUOTA LITERAL+ MAILBOX-REFERRALS NAMESPACE 
UIDPLUS ID NO_ATOMIC_RENAME UNSELECT CHILDREN MULTIAPPEND BINARY SORT 
THREAD=ORDEREDSUBJECT THREAD=REFERENCES ANNOTATEMORE IDLE STARTTLS LISTEXT 
LIST-SUBSCRIBED X-NETSCAPE
S: C01 OK Completed
Please enter your password:
C: L01 LOGIN arnau {8}
S: + go ahead
C:
S: L01 OK User logged in
Authenticated.
Security strength factor: 0

And I, wrongly, assumed that my user was fine...

After a little playing with cyradm, I decided to delete my mailbox and
create it again:
cyradm -user cyrus localhost
lm
dm
cm ...

And here is when I deleted all my mail, deleting/creating my user. (I
suppose).

What I don't understand is why my old users was not able to receive my
mail at MUA level, and why postfix was able to dleiver mail to a user
that has no mailbox (or that is what cyrus says).

I don't remember previous lm output, but I prettty sure I created my
user with "cm arnau" (checking my notes) and now, I had to create my
user like "cm user.arnau", why?

Anyone knows why happens this with a simple update? I did not see any
update notes in elog (package log saved by emerge)


Many thanks in advance,
-- 
Arnau Bria
http://blog.emergetux.net
Bombing for peace is like fucking for virginity

Cyrus Home Page: http://cyrusimap.web.cmu.edu/
Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html

DBERROR "strange character": db4

[Arnau Bria]

Hi,

I've updated my gentoo, and when I restarted the service, I find that
it does not work, and I find a very strange character in the error: a
interrogation mark in a black circle...

[...]
Jun 13 19:10:45 afrodita master[20674]: service notify pid 995 in READY state: 
terminated abnormally
Jun 13 19:10:45 afrodita master[20674]: service pop3 pid 996 in READY state: 
terminated abnormally
Jun 13 19:10:45 afrodita notify[998]: DBERROR @: db4
Jun 13 19:10:45 afrodita master[20674]: service notify pid 998 in READY state: 
terminated abnormally
Jun 13 19:10:45 afrodita lmtpunix[997]: DBERROR : db4
Jun 13 19:10:45 afrodita master[20674]: exiting on SIGTERM/SIGINT
Jun 13 19:10:45 afrodita master[1037]: process started
Jun 13 19:10:45 afrodita ctl_cyrusdb[1041]: DBERROR `�: db4
Jun 13 19:10:45 afrodita ctl_cyrusdb[1041]: recovering cyrus databases
Jun 13 19:10:46 afrodita ctl_cyrusdb[1041]: skiplist: recovered 
/var/imap/mailboxes.db (6 records, 1016 bytes) in 1 second
Jun 13 19:10:46 afrodita ctl_cyrusdb[1041]: skiplist: recovered 
/var/imap/annotations.db (0 records, 144 bytes) in 0 seconds
Jun 13 19:10:46 afrodita ctl_cyrusdb[1041]: DBERROR `�: db4
Jun 13 19:10:46 afrodita ctl_cyrusdb[1041]: DBERROR `�: db4
Jun 13 19:10:46 afrodita cyr_expire[1050]: DBERROR ��: db4
Jun 13 19:10:46 afrodita tls_prune[1051]: DBERROR : db4
Jun 13 19:10:46 afrodita master[1037]: ready for work
Jun 13 19:10:46 afrodita tls_prune[1076]: DBERROR : db4
Jun 13 19:10:46 afrodita cyr_expire[1077]: DBERROR ��: db4
Jun 13 19:10:46 afrodita ctl_cyrusdb[1078]: DBERROR `�: db4
Jun 13 19:10:46 afrodita notify[1079]: DBERROR @: db4
Jun 13 19:10:48 afrodita master[1037]: service notify pid 1079 in READY state: 
terminated abnormally
Jun 13 19:10:48 afrodita notify[1081]: DBERROR @: db4
Jun 13 19:10:58 afrodita master[1037]: service notify pid 1081 in READY state: 
terminated abnormally
Jun 13 19:10:58 afrodita notify[1082]: DBERROR @: db4
Jun 13 19:11:08 afrodita master[1037]: service notify pid 1082 in READY state: 
terminated abnormally
Jun 13 19:11:08 afrodita notify[1083]: DBERROR @: db4
Jun 13 19:11:18 afrodita master[1037]: service notify pid 1083 in READY state: 
terminated abnormally
Jun 13 19:11:18 afrodita notify[1085]: DBERROR @: db4
[...]

I looked for it in google, but I found nothing, could someone help
 to find what is the service telling me?

I'm using cyrus-imapd-2.2.12-r4

TIA,

-- 
Arnau Bria
http://blog.emergetux.net
Bombing for peace is like fucking for virginity

Cyrus Home Page: http://cyrusimap.web.cmu.edu/
Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html

Re: Cyrus with a NFS storage. random DBERROR

[David Carter]

On Sun, 10 Jun 2007, Rob Mueller wrote:

> I can try and keep an eye on bailouts some more, and see if I can get 
> some more details. It would be nice if there was some more logging about 
> why the bail out code path was actually called!

It typically means that something deep in libimap has thrown an error. 
sync_client logs the only information that it has (the return code r).

It probably wouldn't hurt to try and log the current mailbox/user in some 
consistent fashion.

-- 
David Carter Email: [EMAIL PROTECTED]
University Computing Service,Phone: (01223) 334502
New Museums Site, Pembroke Street,   Fax:   (01223) 334679
Cambridge UK. CB2 3QH.

Cyrus Home Page: http://cyrusimap.web.cmu.edu/
Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html

Re: Cyrus with a NFS storage. random DBERROR

[Rob Mueller]

> I suspect that the problem is with mailbox renames, which are not atomic
> and can take some time to complete with very large mailboxes.

I think there's some other issues as well. For instance we still see 
skiplist seen state databases get corrupted every now and then. It seems 
certain corruption can result in the skiplist code calling abort() which 
terminates the sync_server, and causes the sync_client to bail out. I had a 
back trace on one of them the other day, but the stack frames were all wrong 
so it didn't seem that useful.

> HERMES_FAST_RENAME:
>   Translates mailbox rename into filesystem rename() where possible.
>   Useful because sync_client chdir()s into the working directory.
>   Would be less useful in 2.3 with split metadata.

It would still be nice to do this to make renames faster anyway. If you did.

1. Add new mailboxes to mailboxes.db
2. Filesystem rename
3. Remove old mailboxes

You end up with a race condition, but it's far shorter than the mess you can 
end up with at the moment if a restart occurs during a rename.

> Together with my version of delayed expunge this pretty much guarantees 
> that things aren't moving around under sync_client's feet. Its been an 
> awful long time (about a year?) since I last had a sync_client bail out.
>
> We are moving to 2.3 over the summer (initially using my own original 
> replication code), so this is something that I would like to sort out.
>
> Any suggestions?

I can try and keep an eye on bailouts some more, and see if I can get some 
more details. It would be nice if there was some more logging about why the 
bail out code path was actually called!

Rob


Cyrus Home Page: http://cyrusimap.web.cmu.edu/
Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html

Re: Cyrus with a NFS storage. random DBERROR

[David Carter]

On Sat, 9 Jun 2007, Rob Mueller wrote:

>> I run it directly, outside of master.  That way when it crashes, it
>> can be easily restarted.  I have a script that checks that it's
>> running, that the log file isn't too big, and that there are no log-
>> PID files that are too old.  If anything like that happens, it pages
>> someone.
>
> Ditto, we do almost exactly the same thing.

And for that matter, so I do.

> I think there's certain race conditions that still need ironing out, 
> because rerunning sync_client on the same log file that caused a bail 
> out usually succeeds the second time.

I suspect that the problem is with mailbox renames, which are not atomic 
and can take some time to complete with very large mailboxes.

sync_client retries a number of times and then bails out.

 if (folder_list->count) {
int n = 0;
do {
sleep(n*2);  /* XXX  should this be longer? */
 ...
} while (r && (++n < SYNC_MAILBOX_RETRIES));

if (r) goto bail;
 }

This was one of the most significant compromises that Ken had to make when 
integrating my code into 2.3.

My original code cheats, courtesy of two other patches:

HERMES_FAST_RENAME:
   Translates mailbox rename into filesystem rename() where possible.
   Useful because sync_client chdir()s into the working directory.
   Would be less useful in 2.3 with split metadata.

HERMES_SYNC_SNAPSHOT:
   If mailbox action fails, promote to user action (no shared mailboxes)
   If user action fails then lock user out of the mboxlist and try again.

Together with my version of delayed expunge this pretty much guarantees 
that things aren't moving around under sync_client's feet. Its been an 
awful long time (about a year?) since I last had a sync_client bail out.

We are moving to 2.3 over the summer (initially using my own original 
replication code), so this is something that I would like to sort out.

Any suggestions?

-- 
David Carter Email: [EMAIL PROTECTED]
University Computing Service,Phone: (01223) 334502
New Museums Site, Pembroke Street,   Fax:   (01223) 334679
Cambridge UK. CB2 3QH.

Cyrus Home Page: http://cyrusimap.web.cmu.edu/
Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html

Re: Cyrus with a NFS storage. random DBERROR

[Rob Mueller]

> does the IMAP spec specify how large a UUID can be?

UUIDs aren't part of the IMAP spec. It's an addition to cyrus to help 
replication. By default, there's no way to access UUIDs via IMAP at all 
since they're not part of the IMAP spec.

The UUID size chosen was done by David Carter when he implemented 
replication. It would be possible to change them again, but it would mean 
changing the cyrus.index file format and upgrading all cyrus.index files. 
Seemed easier not to do that.

Rob


Cyrus Home Page: http://cyrusimap.web.cmu.edu/
Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html

Re: Cyrus with a NFS storage. random DBERROR

[David Lang]

On Sat, 9 Jun 2007, Rob Mueller wrote:

> So - added is a new option "uuidmode" in imapd.conf. Set it to md5 and you
> will get UUIDs of the form: 02(first 11 bytes of the MD5 value for the
> message) which takes up the same space, but allows pretty good integrity
> checking.
>
> Is it safe? - we calulated that with one billion messages you have a one in
> 1 billion chance of a birthday collision (two random messages with the same
> UUID). They then have to get in the same MAILBOXES collection to sync_client
> to affect each other anyway. The namespace available for generated UUIDs is
> much smaller than this, since they have no collision risk - but if you had
> that many delivering you would hit the limits and start getting blank UUIDs
> anyway.

does the IMAP spec specify how large a UUID can be?

David Lang

Cyrus Home Page: http://cyrusimap.web.cmu.edu/
Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html

Re: Cyrus with a NFS storage. random DBERROR

[Rob Mueller]

>I run it directly, outside of master.  That way when it crashes, it
> can be easily restarted.  I have a script that checks that it's
> running, that the log file isn't too big, and that there are no log-
> PID files that are too old.  If anything like that happens, it pages
> someone.

Ditto, we do almost exactly the same thing.

Also if we switch master/replica roles, our code looks for any incomplete 
log files after stopping the master, and runs those first to ensure that 
replication was completely up to date.

It seems anyone seriously using replication has to unfortunately do these 
things manually at the moment. Replication just isn't reliable enough, we 
see sync_client bail out quite regularly, and there's not enough logging to 
exactly pinpoint why each time. I think there's certain race conditions that 
still need ironing out, because rerunning sync_client on the same log file 
that caused a bail out usually succeeds the second time. It would be nice if 
some code was actually made part of the core cyrus distribution to make this 
all work properly, including switching master/replica roles.

Rob


Cyrus Home Page: http://cyrusimap.web.cmu.edu/
Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html

Re: Cyrus with a NFS storage. random DBERROR

[Rob Mueller]

> I don't have something to consume make_md5 data, yet, either.  My
> plan is to note the difference between the replica and the primary.
> On a subsequent run, if those differences aren't gone, then they
> would be included in a report.

Rather than make_md5, check the MD5 UUIDs patch below. Using this, we have a 
script that regularly checks both sides of a master/replica pair to check 
everything is consistent between the UUID and the computed MD5. It was this 
that let us discover the rare "didn't unlink old files" bug reported about 3 
months back.

---
http://cyrus.brong.fastmail.fm/

One problem we've had is the inability to easily check that the files on 
disk correspond to what was originally delivered to check for cyrus data 
corruption after either a disk problem or some other bug has caused us to be 
unsure of our data integrity.
I wanted to calculate a digest and store it somewhere in the index file, but 
messing with the file format and fixing sync to still work, etc... it all 
sounded too painful.

So - added is a new option "uuidmode" in imapd.conf. Set it to md5 and you 
will get UUIDs of the form: 02(first 11 bytes of the MD5 value for the 
message) which takes up the same space, but allows pretty good integrity 
checking.

Is it safe? - we calulated that with one billion messages you have a one in 
1 billion chance of a birthday collision (two random messages with the same 
UUID). They then have to get in the same MAILBOXES collection to sync_client 
to affect each other anyway. The namespace available for generated UUIDs is 
much smaller than this, since they have no collision risk - but if you had 
that many delivering you would hit the limits and start getting blank UUIDs 
anyway.

Mitigating even the above risk: you could alter sync_client to not use UUID 
for copying. It's not like it's been working anyway (see our other UUID 
related patch). As an integrity check it's much more useful.


The attached patch adds the md5 method, a "random" method which I've never 
tested and is almost certainly bogus, but is there for educational 
value[tm], the following FETCH responses in imapd:

FETCH UUID => 24 character hex string (02 + first 11 bytes of MD5) FETCH 
RFC822.MD5 => 32 character hex string (16 bytes of MD5) FETCH 
RFC822.FILESIZE => size of actual file on disk (via stat or mmap)

Totally non-standard of course, but way useful for our replication checking 
scripts. Embrace and extend 'r' us.

Anyone feel like writing an RFC for fetching the digest of a message via 
IMAP? If the server calculated it on delivery and cached it then you'd have 
a great way to clean up after a UIDVALIDITY change or other destabilising 
event without having to fetch every message again.

---

Rob


Cyrus Home Page: http://cyrusimap.web.cmu.edu/
Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html

Re: Cyrus with a NFS storage. random DBERROR

[Wesley Craig]

I run it directly, outside of master.  That way when it crashes, it  
can be easily restarted.  I have a script that checks that it's  
running, that the log file isn't too big, and that there are no log- 
PID files that are too old.  If anything like that happens, it pages  
someone.

:wes

On 08 Jun 2007, at 11:48, Nik Conwell wrote:
> Do people run sync_client in the SERVICES section rather than START?
> The install-replication docs indicate to put it in START.  If my
> replica goes away for a little while, sync_client exits and then I
> have to restart it manually and then process any pending logs.  Would
> be nice if it just started automatically and picked up where it left
> off.

Cyrus Home Page: http://cyrusimap.web.cmu.edu/
Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html

Re: Cyrus with a NFS storage. random DBERROR

[Wesley Craig]

On 08 Jun 2007, at 06:52, Paul Dekkers wrote:
> * I'm still not fully using make_md5 myself. Still need to write a
> script, that walks through the files, and only compares the messages
> that are in both folders. If I run make_md5, it's never working on a
> folder on both servers at the same time, so there's always a gap.  
> So the
> files aren't always equal, I think. Oh well.

I don't have something to consume make_md5 data, yet, either.  My  
plan is to note the difference between the replica and the primary.   
On a subsequent run, if those differences aren't gone, then they  
would be included in a report.

:wes

Cyrus Home Page: http://cyrusimap.web.cmu.edu/
Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html