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
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
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
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
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
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
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
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
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
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
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:
t?
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
s-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: BDB006
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
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
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
Hi,
--On 30. Juli 2015 01:17:29 +0300 Dudi Finkel dudi.fin...@atrinet.com
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
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
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
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
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
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
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
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
*
- /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
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
On 12/06/2010 07:45 AM, Antoine Jacoutot wrote:
On Mon, 06 Dec 2010 02:55:57 +0100, IMAP List Administration li...@y42.org
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
[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
]: 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
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
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
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
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
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
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
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
:
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
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
http://docs.opengroupware.org/Members/whitemice/wmogag/file_view
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
, entries seems to be normal.
In fact I managaged to solve the problem by removing the quota file in
/var/lib/imap/quota/x/user/ 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
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
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
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
(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
) 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
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
2009 15:59:09 -0600, Josh Whitver
whitv...@urbandale.k12.ia.us
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
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
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
Original Message
Subject: Re: Cyrus DB Errors DBERROR: error fetching user.username
evenafter reconstructs
From: Josh Whitver whitv...@urbandale.k12.ia.us
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
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
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,
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
On Tue, 10 Feb 2009 15:59:09 -0600, Josh Whitver
whitv...@urbandale.k12.ia.us 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
, 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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
[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
-- 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
.
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
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
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
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---
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
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
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
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
.
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
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
/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
:
---
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
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
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
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
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
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
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
Michael Menge wrote:
Hi,
after the problem with the wiki was solved, i added a summery about
CyrusCluster
http://cyrusimap.web.cmu.edu/twiki/bin/view/Cyrus/CyrusCluster .
Could you, please, describe more detailed problems with replication:
CyrusReplication: ... The replication is asynchrony
Hi,
i havent used the replication my selfe, so the information is only based on
what i have read on this list.
The sync_client discovers all changes on the mailboxes queues them and send
them to the server. In case of a system crash ther might be changes
that are still queued and not send to
Michael Menge wrote:
Hi,
i havent used the replication my selfe, so the information is only
based on
what i have read on this list.
The sync_client discovers all changes on the mailboxes queues them and
send
them to the server. In case of a system crash ther might be changes
that are
Hi,
Dmitriy Kirhlarov wrote:
Michael Menge wrote:
after the problem with the wiki was solved, i added a summery about
CyrusCluster
http://cyrusimap.web.cmu.edu/twiki/bin/view/Cyrus/CyrusCluster .
Could you, please, describe more detailed problems with replication:
Dmitriy Kirhlarov wrote:
Michael Menge wrote:
i havent used the replication my selfe, so the information is only
based on
what i have read on this list.
The sync_client discovers all changes on the mailboxes queues them and
send
them to the server. In case of a system crash ther
On Jun 8, 2007, at 11:36 AM, Paul Dekkers wrote:
Dmitriy Kirhlarov wrote:
Which reminds me... isn't it strange that an unfinished logfile is
removed when the cyrus master (or was it the sync_client -r) is
restarted? Would make sense to me if the file is renamed / stored for
later running
Hi, list.
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
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
1 - 100 of 304 matches
Mail list logo
