Re: cyrus 2.4 and DBERROR

till 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

cyrus 2.4 and DBERROR

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

tls_prune DBERROR

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

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

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

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

map/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 > argumen

Re: R: Re: DBERROR: critical database situation

) > ./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

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

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 impo

Re: R: Re: DBERROR: critical database situation

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 y

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

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

Re: R: Re: DBERROR: critical database situation

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 Session

R: Re: DBERROR: critical database situation

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

R: Re: DBERROR: critical database situation

rmat, 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

> 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]:

Re: DBERROR: critical database situation

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]: DB

DBERROR: critical database situation

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

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

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

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

DBERROR db4: Lock table is out of available locker entries

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:

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

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. > >

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

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

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

ebian 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). >> &g

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

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

Mystery cyrus/lmtp and cyrus/imap DBERROR log entries

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

Re: DBERROR error fetching user.toto cyrusdb error

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 q

Re: DBERROR error fetching user.toto cyrusdb error

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 s

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

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 environm

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

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 corr

Re: what is causing DBERROR?

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 sysl

Re: what is causing DBERROR?

tabases > 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 de

what is causing DBERROR?

sdb[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 im

Re: cyrus and DBERROR complains.

1 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 > /va

cyrus and DBERROR complains.

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

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

.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.) >

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

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 skip

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

ve 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 alread

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

s 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 &

cvt_cyrusdb: DBERROR Я^F^H: db4

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

DBERROR

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

Re: DBERROR with Cyrus 2.2.12

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 >

Re: DBERROR with Cyrus 2.2.12

> 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

Re: DBERROR with Cyrus 2.2.12

ve 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

Re: DBERROR with Cyrus 2.2.12

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 c

Re: DBERROR with Cyrus 2.2.12

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 >> &

Re: DBERROR with Cyrus 2.2.12

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

Re: DBERROR with Cyrus 2.2.12

- 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 me

Re: DBERROR with Cyrus 2.2.12

em 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/berkel

Re: DBERROR with Cyrus 2.2.12

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

DBERROR with Cyrus 2.2.12

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.* fi

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

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,

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

na 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

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

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 p

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

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

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

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! :) > Jos

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

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 >

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

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

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

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 < mailbox

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

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

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

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_dbtoo

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

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/im

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

ever 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/

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

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: erro

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

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 th

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

fferent 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

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

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]: DBERR

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

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

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

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

"DBERROR: error listing log files" if only skiplist

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[

Re: DBERROR - how do I recover?

t;> 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' f

Re: DBERROR - how do I recover?

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 &

Re: DBERROR - how do I recover?

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]&

DBERROR - how do I recover?

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

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

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

ctl_cyrusdb - DBERROR db4

ning 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 z

Re: Help! lmtpd infinite loops with DBERROR

[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:

Re: Help! lmtpd infinite loops with DBERROR

n 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_chec

Help! lmtpd infinite loops with DBERROR

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 P

Re: DBERROR

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 > >

Re: DBERROR

>>> -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

Re: DBERROR

> > -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. > > > &

Re: DBERROR

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]:

Re: DBERROR

nnotations.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

DBERROR

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]: DB

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

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/tl

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

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 >

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

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 han

syncserver DBERROR

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 1

Re: lately get DBERROR db4: PANIC

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

lately get DBERROR db4: PANIC

t 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

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

llog : --- 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 def

Rw: DBERROR "strange character": db4

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 wi

DBERROR "strange character": db4

y 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]: DB

Re: Cyrus with a NFS storage. random DBERROR

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 thro

Re: Cyrus with a NFS storage. random DBERROR

> 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 corrup

Re: Cyrus with a NFS storage. random DBERROR

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

Re: Cyrus with a NFS storage. random DBERROR

> 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 impl

Re: Cyrus with a NFS storage. random DBERROR

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 c

Re: Cyrus with a NFS storage. random DBERROR

>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

Re: Cyrus with a NFS storage. random DBERROR

> 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

Re: Cyrus with a NFS storage. random DBERROR

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

Re: Cyrus with a NFS storage. random DBERROR

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,

  1   2   3   4   >