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

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 Mi

Re: R: Re: DBERROR: critical database situation

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

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

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 Mittw

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

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

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

Re: DBERROR: critical database situation

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

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]: DBERROR db5: pthread sus

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

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 quota and all is good Th

Re: DBERROR error fetching user.toto cyrusdb error

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 mailb

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

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

Re: DBERROR with Cyrus 2.2.12

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

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 >> >> Should I be worried by these messages ? >>

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 the greatest Cyrus or

Re: DBERROR with Cyrus 2.2.12

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)

Re: DBERROR with Cyrus 2.2.12

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

Re: DBERROR with Cyrus 2.2.12

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 rea

Re: DBERROR - how do I recover?

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

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 > > Jun 23 12:57:34 ch

Re: DBERROR - how do I recover?

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 wit

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

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

Re: DBERROR

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 b

Re: DBERROR

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

Re: DBERROR

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

Re: DBERROR: skiplist recovery mailboxes.db 0090 - suddenly all is failing!

On Mon, 5 Mar 2007, Gregor Wenkelewsky wrote: I don't really know about that. Here is from the log during another "controlled shutdown and reboot", of course I had to make sure that my mailboxes.db error would not occur on every reboot. (It did not occur again.) These are the last lines, no sign

Re: DBERROR: skiplist recovery mailboxes.db 0090 - suddenly all is failing!

On Mon, 19 Feb 2007 22:26:10 +0100, Andrew Morgan wrote: > On Mon, 19 Feb 2007, Gregor Wenkelewsky wrote: > >> On Thu, 15 Feb 2007 18:15:53 +0100, Andrew Morgan wrote: >> Cyrus has been installed here just a few weeks ago, and after some hard days it was working smoothly and very well. U

Re: DBERROR: skiplist recovery mailboxes.db 0090 - suddenly all is failing!

On Mon, 19 Feb 2007, Gregor Wenkelewsky wrote: On Thu, 15 Feb 2007 18:15:53 +0100, Andrew Morgan <[EMAIL PROTECTED]> wrote: Cyrus has been installed here just a few weeks ago, and after some hard days it was working smoothly and very well. Until suddenly, sadly today it started to fail complet

Re: DBERROR: skiplist recovery mailboxes.db 0090 - suddenly all is failing!

On Thu, 15 Feb 2007 18:15:53 +0100, Andrew Morgan <[EMAIL PROTECTED]> wrote: >> Cyrus has been installed here just a few weeks ago, and after some hard >> days it was working smoothly and very well. Until suddenly, sadly today >> it started to fail completely with this error message in mail.warn,

Re: DBERROR: skiplist recovery mailboxes.db 0090 - suddenly all is failing!

On Thu, 15 Feb 2007, Gregor Wenkelewsky wrote: Hi there, Cyrus has been installed here just a few weeks ago, and after some hard days it was working smoothly and very well. Until suddenly, sadly today it started to fail completely with this error message in mail.warn, mail.error and syslog:

Re: DBERROR: dbenv->open

Ramya Krishnan wrote: Hi.. I. I get db error when i try to start master. Nov 21 18:14:59 ramya master[2855]: about to exec /var/cyrus/sbin/ctl_cyrusdb Nov 21 18:15:17 ramya ctl_cyrusdb[2855]: DBERROR ¬<8e>^F^H: db4 Nov 21 18:15:17 ramya ctl_cyrusdb[2855]: DBERROR: dbenv->open '/var/lib/imap/db

Re: DBERROR - lockers

On Mon, 24 Oct 2005, Pascal Maes wrote: hello cyrus-imapd : 2.2.12 Berkeley DB : 4.3.28 Solaris x86 5.10 I see a lot of errors like : Oct 24 01:04:38 mail imap[17520]: [ID 866726 local0.warning] DBERROR \354\305 Oct 24 01:04:38 mail ^H: 263 lockers Oct 24 10:23:25 mail imap[2673]: [ID 86

Re: DBERROR

> On Thu, 2005-07-14 at 15:29 +0200, Per-Olov Sjöholm wrote: >> Thank you VERY much Gary. You were right. It worked if I first did a >> change directory to /. >> >> Hope the bug will be fixed for next release. > > Simon, > > I haven't seen this on my RH systems, but it might be a good idea to put >

Re: DBERROR

Simon Matter wrote: What is the problem here? Try to cd in /var/imap before restarting or stopping/starting cyrus and see if it helps. Antoine --- Cyrus Home Page: http://asg.web.cmu.edu/cyrus Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu List Archives/Info: http://asg.web.cmu.edu/cyrus/m

Re: DBERROR

On Thu, 2005-07-14 at 15:29 +0200, Per-Olov Sjöholm wrote: > Thank you VERY much Gary. You were right. It worked if I first did a > change directory to /. > > Hope the bug will be fixed for next release. Simon, I haven't seen this on my RH systems, but it might be a good idea to put a 'cd /var/l

Re: DBERROR

Thank you VERY much Gary. You were right. It worked if I first did a change directory to /. Hope the bug will be fixed for next release. Thanks /Per-Olov >> >> Jul 13 22:50:06 xanadu ctl_cyrusdb[2060]: checkpointing cyrus >> databases >> >> Jul 13 22:50:07 xanadu ctl_cyrusdb[2060]: done checkpo

Re: DBERROR

On Thu, Jul 14, 2005 at 09:34:04AM +0200, Per-Olov Sjöholm wrote: > Simon Matter said: > >> Adding the following to the original post as well. > > > >> Jul 13 22:50:06 xanadu ctl_cyrusdb[2060]: checkpointing cyrus databases > >> Jul 13 22:50:07 xanadu ctl_cyrusdb[2060]: done checkpointing cyrus > >

Re: DBERROR

Simon Matter said: >> Adding the following to the original post as well. >> >> Directly after boot, the log looks like this. And then it will continue >> to >> look good with checkpointings until I restart the cyrus process... >> >> Jul 13 22:50:02 xanadu master[1766]: process started >> Jul 13 22

Re: DBERROR

> Adding the following to the original post as well. > > Directly after boot, the log looks like this. And then it will continue > to > look good with checkpointings until I restart the cyrus process... > > Jul 13 22:50:02 xanadu master[1766]: process started > Jul 13 22:50:03 xanadu ctl_cyrusdb[1

Re: DBERROR

Adding the following to the original post as well. Directly after boot, the log looks like this. And then it will continue to look good with checkpointings until I restart the cyrus process... Jul 13 22:50:02 xanadu master[1766]: process started Jul 13 22:50:03 xanadu ctl_cyrusdb[10342]: recove

Re: DBERROR - not enough space

Quoting Igor Brezac <[EMAIL PROTECTED]>: It is hard to tell. Your cache size appears to be large enough, there are plenty of lockers available (but this is still a suspect), although you seem to have a rather large number of cyrus processes running (700+) or your processes are dying without rel

Re: DBERROR - not enough space

On Wed, 11 May 2005, Didi Rieder wrote: Quoting Igor Brezac <[EMAIL PROTECTED]>: I really don't understand what "not enough space" means... You are running out of space in one of the Berkeley DB memory regions (cache logging, locking or transactions). Check http://www.sleepycat.com/docs/ref/debug

Re: DBERROR - not enough space

Quoting Didi Rieder <[EMAIL PROTECTED]>: May 10 13:07:35 sbox imap[3540]: [ID 866726 local6.warning] DBERROR db4: Logging region out of memory; you may need to increase its size May 10 13:07:35 sbox imap[3540]: [ID 729713 local6.error] DBERROR: opening /mail/imap/tls_sessions.db: Not enough space

Re: DBERROR - not enough space

Quoting Igor Brezac <[EMAIL PROTECTED]>: I really don't understand what "not enough space" means... You are running out of space in one of the Berkeley DB memory regions (cache logging, locking or transactions). Check http://www.sleepycat.com/docs/ref/debug/runtime.html to see how to get more de

Re: DBERROR - not enough space

On Tue, 10 May 2005, Didi Rieder wrote: Quoting Igor Brezac <[EMAIL PROTECTED]>: This will not work, you need to run db_recover or remove the contents of /mail/imap/db in addition to removing the two databases. Aha... so is it save to remove every file from /mail/imap/db? yes, remove all files in

Re: DBERROR - not enough space

Quoting Igor Brezac <[EMAIL PROTECTED]>: This will not work, you need to run db_recover or remove the contents of /mail/imap/db in addition to removing the two databases. Aha... so is it save to remove every file from /mail/imap/db? yes, remove all files in /mail/imap/db. Do this while the server

Re: DBERROR - not enough space

On Tue, 10 May 2005, Didi Rieder wrote: Quoting Igor Brezac <[EMAIL PROTECTED]>: I removed the two databases after I made those settings and then started cyrus again, so they should be fresh and the settings should be in action, right? This will not work, you need to run db_recover or remove the

Re: DBERROR - not enough space

Quoting Igor Brezac <[EMAIL PROTECTED]>: I removed the two databases after I made those settings and then started cyrus again, so they should be fresh and the settings should be in action, right? This will not work, you need to run db_recover or remove the contents of /mail/imap/db in addition t

Re: DBERROR - not enough space

Quoting Igor Brezac <[EMAIL PROTECTED]>: How soon after you reset your db env do you start seeing DBERRORs? Do and of the cyrus services (imapd/lmtpd/pop3d) crash? It starts about 5 minutes after I restart the server. And it seems only to happen when many users use the system, eg. between ~ 8:3

Re: DBERROR - not enough space

On Tue, 10 May 2005, Didi Rieder wrote: Quoting Wil Cooley <[EMAIL PROTECTED]>: On Tue, 2005-05-10 at 13:25 +0200, Didi Rieder wrote: I already tried to generate a DB_CONFIG file in /mail/imap/db, and added the following entries: set_mp_mmapsize 65536000 set_cachesize 0 16384000 2 set_lg_bsize 6553

Re: DBERROR - not enough space

Quoting Wil Cooley <[EMAIL PROTECTED]>: On Tue, 2005-05-10 at 13:25 +0200, Didi Rieder wrote: I already tried to generate a DB_CONFIG file in /mail/imap/db, and added the following entries: set_mp_mmapsize 65536000 set_cachesize 0 16384000 2 set_lg_bsize 65536 This didn't change anything. I also se

Re: DBERROR - not enough space

On Tue, 10 May 2005, Didi Rieder wrote: Quoting Igor Brezac <[EMAIL PROTECTED]>: On Tue, 10 May 2005, Didi Rieder wrote: Quoting Igor Brezac <[EMAIL PROTECTED]>: Do you get errors when cyrus performs checkpointing? No not at all. It starts an terminates without errors. I forgot to mention that I do

Re: DBERROR - not enough space

Quoting Igor Brezac <[EMAIL PROTECTED]>: On Tue, 10 May 2005, Didi Rieder wrote: Quoting Igor Brezac <[EMAIL PROTECTED]>: Do you get errors when cyrus performs checkpointing? No not at all. It starts an terminates without errors. I forgot to mention that I do get the same errors with the deliver.db

Re: DBERROR - not enough space

On Tue, 2005-05-10 at 13:25 +0200, Didi Rieder wrote: > I already tried to generate a DB_CONFIG file in /mail/imap/db, and > added the following entries: > > set_mp_mmapsize 65536000 > set_cachesize 0 16384000 2 > set_lg_bsize 65536 > > This didn't change anything. > I also searched the web but

Re: DBERROR - not enough space

On Tue, 10 May 2005, Didi Rieder wrote: Quoting Igor Brezac <[EMAIL PROTECTED]>: Do you get errors when cyrus performs checkpointing? No not at all. It starts an terminates without errors. I forgot to mention that I do get the same errors with the deliver.db I start cyrus from 'configdirectory' (/m

Re: DBERROR - not enough space

Quoting Igor Brezac <[EMAIL PROTECTED]>: Do you get errors when cyrus performs checkpointing? No not at all. It starts an terminates without errors. I forgot to mention that I do get the same errors with the deliver.db Didi -Igor On Tue, 10 May 2005, Didi Rieder wrote: Hi all, I hope somone can exp

Re: DBERROR - not enough space

Do you get errors when cyrus performs checkpointing? -Igor On Tue, 10 May 2005, Didi Rieder wrote: Hi all, I hope somone can explain the following error messages and tell me how to fix the problem. We get lots of them in the cyrus logs: May 10 13:07:35 sbox imap[3540]: [ID 866726 local6.warning]

Re: DBERROR db4: fatal region error detected

Hi, Jens Ahlin wrote: I have upgraded our mailserver to Tao Linux from RH 8 and cyrus from 2.1.12-3 to cyrus 2.2.8-1 using Simons RPMS. All works ok until I shutdown cyrus and starts it again. The the error below hit me in the face. To recover I delete the deliver.db and all under /var/lib/imap/db/

Re: DBERROR db4: Logging region out of memory

## Grisu Marc ([EMAIL PROTECTED]): Please trim your lines to about 72 characters. > Has anyone an exemple of a Berkeley DB_Config file? set_cachesize 0 8388608 8 set_lg_regionmax 524288 set_lg_bsize 2097152 About 20,000 users, works fine. Regards, Christoph -- Spare Space. --- Cyrus Home Pag

RE: DBERROR db3: 4 lockers

On Thu, 25 Sep 2003, Andrew Brink wrote: > Im just curious because we have been experience high DB lockers, and I > can't recall if we dumped and undumped when we migrated to 2.x. (It was > sometime ago) I guess a better question would be, would it work at all > if we didn't? The dump/undump is j

RE: DBERROR db3: 4 lockers

i [mailto:[EMAIL PROTECTED] > Sent: Thursday, September 25, 2003 7:09 PM > To: Andrew Brink > Cc: [EMAIL PROTECTED] > Subject: RE: DBERROR db3: 4 lockers > > > On Thu, 25 Sep 2003, Andrew Brink wrote: > > > Oh. I meant if you didn't compile the binaries with ski

RE: DBERROR db3: 4 lockers

Oh. I meant if you didn't compile the binaries with skiplist, just DB4. Should you still dump and undump? > -Original Message- > From: Rob Siemborski [mailto:[EMAIL PROTECTED] > Sent: Thursday, September 25, 2003 7:06 PM > To: Andrew Brink > Cc: [EMAIL PROTECTED] &g

RE: DBERROR db3: 4 lockers

On Thu, 25 Sep 2003, Andrew Brink wrote: > Oh. I meant if you didn't compile the binaries with skiplist, just DB4. > > Should you still dump and undump? What, if you just recompile the binaries with the same configure settigns? No, there really isn't a need then. If you're upgrading from 1.x to

RE: DBERROR db3: 4 lockers

On Thu, 25 Sep 2003, Andrew Brink wrote: > > In theory, what would happen if you didn't dump the mailbox list before > upgrading? > Uh, you wouldn't have a readable mailbox list, really... The binaries would be expecting a skiplist mailbox list, but you'd be giving them a Berkeley DB one. -Rob

RE: DBERROR db3: 4 lockers

In theory, what would happen if you didn't dump the mailbox list before upgrading? > -Original Message- > From: Rob Siemborski [mailto:[EMAIL PROTECTED] > Sent: Thursday, September 25, 2003 5:06 PM > To: Robert Covell > Cc: [EMAIL PROTECTED] > Subject: Re:

Re: DBERROR db3: 4 lockers

Mensaje citado por Rob Siemborski <[EMAIL PROTECTED]>: > On Thu, 25 Sep 2003, Robert Covell wrote: > > Sep 25 16:12:09 mail1b lmtpd[155]: DBERROR db3: 4 lockers > Note that in reality, esepcially for smaller sites, these messages > on > their own aren't a severe concern. Only if the number is r

Re: DBERROR db3: 4 lockers

On Thu, 25 Sep 2003, Paul M Fleming wrote: > We found limiting the number of lmtp processes to 10 helped with locker > problems. Let sendmail/postfix handle the queuing and lmtp the > delivery.. When we tried to blast 10-20 messages/sec at our test server > locking became a problem with the dup

Re: DBERROR db3: 4 lockers

We found limiting the number of lmtp processes to 10 helped with locker problems. Let sendmail/postfix handle the queuing and lmtp the delivery.. When we tried to blast 10-20 messages/sec at our test server locking became a problem with the duplicate delivery db. Across 3 servers and 600 concurren

Re: DBERROR db3: 4 lockers

On Thu, 25 Sep 2003, Robert Covell wrote: > We are in the process of replacing our 1.5.24 Cyrus box with a new 2.1.15 > box. After we got everything setup, tested and stabilized we rebooted the > box and got: > > Sep 25 16:12:09 mail1b ctl_cyrusdb[152]: checkpointing cyrus databases > Sep 25 16:1

Re: dberror seen db

Agri wrote: is it a bug? :-\ I don't know. Its working for other people. What are the permissions on /var/cyrus? Can i do smth to fix it? You could do an strace on the imapd process to see what it is doing. You could also make the directories by hand. Agri On Sat, 13 Sep 2003 08:09:01 -0

Re: dberror seen db

is it a bug? :-\ Can i do smth to fix it? Agri On Sat, 13 Sep 2003 08:09:01 -0400 Ken Murchison <[EMAIL PROTECTED]> wrote: > > > Agri wrote: > > Hm my /var/cyrus do exits, and its content > > > > [EMAIL PROTECTED] cyrus]# ls -l > > total 19 > > -rw---1 cyrusmail 2048 S

Re: dberror seen db

Agri wrote: Hm my /var/cyrus do exits, and its content [EMAIL PROTECTED] cyrus]# ls -l total 19 -rw---1 cyrusmail 2048 Sep 13 04:04 annotations.db drwxr-xr-x2 cyrusmail 1024 Sep 11 18:04 db drwx--2 cyrusmail 1024 Sep 13 10:34 db.backup1

Re: dberror seen db

Hm my /var/cyrus do exits, and its content [EMAIL PROTECTED] cyrus]# ls -l total 19 -rw---1 cyrusmail 2048 Sep 13 04:04 annotations.db drwxr-xr-x2 cyrusmail 1024 Sep 11 18:04 db drwx--2 cyrusmail 1024 Sep 13 10:34 db.backup1 drwx--

Re: dberror seen db

Agri wrote: Thank you for answer. No, hash is turned off. my configs ** cat /etc/imapd.conf configdirectory: /var/cyrus partition-default: /var/imap sasl_pwcheck_method: auxprop tls_cert_file: /etc/openssl/certs/cert.pem tls_key_file:

Re: dberror seen db

Thank you for answer. No, hash is turned off. my configs ** > cat /etc/imapd.conf configdirectory: /var/cyrus partition-default: /var/imap sasl_pwcheck_method: auxprop tls_cert_file: /etc/openssl/certs/cert.pem tls_key_file: /etc/openssl

Re: dberror seen db

Agri wrote: i'm using imapd-2.2.1-beta i got messages at syslog imap[12855]: DBERROR: opening /var/cyrus/domain/q/7m.ru/user/a/agri.seen: cyrusdb error imap[12855]: DBERROR: opening /var/cyrus/domain/q/7m.ru/user/a/agri.seen: No such file or directory i have no any hashing for directories. W

Re: DBERROR and DB_CONFIG

On Wed, 2 Jul 2003, Julien Marchal wrote: > Hi, > > I have problem with cyrus and db berkeley : > > DBERROR:lmtpd: unable to init duplicate delivery database > DBERROR: opening /home/cyrus/conf/mailboxes.db: Cannot allocate memory > DBERROR: opening /home/cyrus/conf/mailboxes.db: cyrusdb error >

Re: DBERROR: archive

On Thu, 9 Jan 2003, Bob Meader wrote: > I get these recurring lines in log: > Jan 9 15:08:27 tuba ctl_cyrusdb[28368]: checkpointing cyrus databases > Jan 9 15:08:27 tuba ctl_cyrusdb[28368]: DBERROR: archive /var/imap/db: > cyrusdb error > Jan 9 15:08:27 tuba ctl_cyrusdb[28368]: done checkpointi

Re: DBERROR: skiplist recovery errors

Date: Mon, 23 Dec 2002 14:43:17 -0500 From: "John A. Tamplin" <[EMAIL PROTECTED]> I have a user mailbox that is genering thousands of these same "DBERROR: skiplist recovery: should be ADD or DELETE" messages. This machine hasn't been rebooted, and Cyrus hasn't even been rest

Re: DBERROR: skiplist recovery errors

I have a user mailbox that is genering thousands of these same "DBERROR: skiplist recovery: should be ADD or DELETE" messages. This machine hasn't been rebooted, and Cyrus hasn't even been restarted since this particular user was converted (on the Cyrus side, conversion entails simply doi

Re: DBERROR: skiplist recovery errors

So... is the berkley db3 more reliable then skiplist ? is it slower than skiplist ? Lawrence Greenfield wrote: Date: Wed, 11 Dec 2002 10:46:45 -0200 From: Alessandro Oliveira <[EMAIL PROTECTED]> [...] Dec 9 09:12:35 intra03 imapd[30212]: DBERROR: skiplist recovery: 0958 should b

Re: DBERROR: skiplist recovery errors

Quoting Lawrence Greenfield <[EMAIL PROTECTED]>: > Actually, for some drives the claim is that, if they are correctly > functioning, then that _won't_ happen. After all, it takes an > insignificant amount of time to write a single block to a modern > drive---there is plenty of power in capacitors

Re: DBERROR: skiplist recovery errors

Date: Thu, 12 Dec 2002 20:32:50 -0500 From: "John A. Tamplin" <[EMAIL PROTECTED]> Correct, but if the power gets cut to the drive during the block write, all bets are off for the content of that block. True, most of the time you won't get weird failures but then most of the time

Re: DBERROR: skiplist recovery errors

> I don't think I've ever heard of a filesystem that mingles more than > one file in a single block. (If they do, it's certainly news to me, > and no reasonable model can be made that will deal with it.) The "out ResierFS does this (though you can turn it off). One of it's claims is that it happi

Re: DBERROR: skiplist recovery errors

Quoting Lawrence Greenfield <[EMAIL PROTECTED]>: > Obviously disks do not write one byte at a time. Writes happen to > blocks of data. However, the operating system will issue the block of > data identically to the old block except for the byte (or word, or > whatever) that I've changed. Correct,

Re: DBERROR: skiplist recovery errors

Quoting Lawrence Greenfield <[EMAIL PROTECTED]>: > [Sidebar: skiplist makes an assumption that a single byte write might > be in an interdeterminate state after a crash, that write will not > affect nearby data that is already known to be on stable storage. On > reflection I suspect the loop-forev

Re: DBERROR: skiplist recovery errors

Date: Thu, 12 Dec 2002 20:00:52 -0500 From: "John A. Tamplin" <[EMAIL PROTECTED]> [...] Disks don't write one byte at a time, so a system crash during a write can result in indeterminate state for the entire block (and it gets worse when you go through the filesystem rather than raw

Re: DBERROR: skiplist recovery errors

--On Friday, December 13, 2002 10:48 AM +1100 Rob Mueller <[EMAIL PROTECTED]> wrote: | Yes. I think it's better to at least startup with a reduced DB, then fail | to start at all. Which means mail to those poor soles that got dropped from the db will start bouncing horribly, right? If so, thes

Re: DBERROR: skiplist recovery errors

From: "Rob Mueller" <[EMAIL PROTECTED]> Date: Fri, 13 Dec 2002 10:48:20 +1100 >It's scarier when you see this on the mailboxes DB. > > You've had this problem on your mailboxes db? Yuck. Yes, after system crashes. I think it was a SCSI card/driver problem. Hmm. Well, this i

Re: DBERROR: skiplist recovery errors

>It's scarier when you see this on the mailboxes DB. > > You've had this problem on your mailboxes db? Yuck. Yes, after system crashes. I think it was a SCSI card/driver problem. > Doing this could destroy most of the database and could be even more > confusing to system administrators. I gu

Re: DBERROR: skiplist recovery errors

From: "Rob Mueller" <[EMAIL PROTECTED]> Date: Thu, 12 Dec 2002 13:01:48 +1100 Looks like you've got corrupted skiplist files. Delete the seen state databases with the problem and it will automatically rebuild them. That's what we do. It's scarier when you see this on the mailboxes

Re: DBERROR: skiplist recovery errors

Date: Wed, 11 Dec 2002 10:46:45 -0200 From: Alessandro Oliveira <[EMAIL PROTECTED]> [...] Dec 9 09:12:35 intra03 imapd[30212]: DBERROR: skiplist recovery: 0958 should be ADD or DELETE Dec 9 09:12:35 intra03 imapd[30212]: DBERROR: opening /var/lib/imap/user/n/natacha.se

RE: DBERROR: skiplist recovery errors

2002 11:02 AM > To: Alessandro Oliveira; [EMAIL PROTECTED] > Cc: Rob Siemborski > Subject: Re: DBERROR: skiplist recovery errors > > > Looks like you've got corrupted skiplist files. Delete the seen state > databases with the problem and it will automatically rebuild the

  1   2   >