Hi,
Am Mittwoch, den 21.04.2010, 00:37 +0200 schrieb Marcus:
[...]
> I did clean /var/lib/cyrus/db and deleted /var/lib/cyrus/deliver.db
> after stopping cyrus. But after three day I got the same error
[...]
I've checked the logs again tonight and the "IOERROR: lock_shared" only
comes up while du
Hi,
Am Dienstag, den 06.04.2010, 18:13 -0500 schrieb Dan White:
> On 07/04/10 00:45 +0200, Marcus wrote:
> >I've restarted cyrus and got a "recovery /var/lib/cyrus/deliver.db:
> >found partial txn, not replaying". Delivering is working fine and
> >dupelim check too. Could someone confirm, that Sim
On 07/04/10 00:45 +0200, Marcus wrote:
>I've restarted cyrus and got a "recovery /var/lib/cyrus/deliver.db:
>found partial txn, not replaying". Delivering is working fine and
>dupelim check too. Could someone confirm, that Simon's idea to clean
>up /var/lib/cyrus/db and remove deliver.db is _not_
On Wed, 7 Apr 2010, Marcus wrote:
>> Just guessing, maybe you have to stop cyrus, clean up the $configdir/db
>> directory, remove the existing deliver.db file and start up again.
>> Maybe you have some BDB stuff left over in ../db.
>
> I've restarted cyrus and got a "recovery /var/lib/cyrus/delive
red /var/lib/cyrus/deliver.db: Interrupted system call
> > Apr 5 04:12:48 server cyrus/lmtpunix[8473]: DBERROR:
> > opening /var/lib/cyrus/deliver.db: cyrusdb error
> > Apr 5 04:12:48 server cyrus/lmtpunix[8473]: FATAL: lmtpd: unable to
> > init duplicate delivery database
&
/deliver.db: Interrupted system call
> > Apr 5 04:12:48 server cyrus/lmtpunix[8473]: DBERROR:
> > opening /var/lib/cyrus/deliver.db: cyrusdb error
> > Apr 5 04:12:48 server cyrus/lmtpunix[8473]: FATAL: lmtpd: unable to
> > init duplicate delivery database
> > Apr
RROR:
> opening /var/lib/cyrus/deliver.db: cyrusdb error
> Apr 5 04:12:48 server cyrus/lmtpunix[8473]: FATAL: lmtpd: unable to
> init duplicate delivery database
> Apr 5 04:12:48 server cyrus/master[21374]: process 8473 exited, status
> 75
> Apr 5 04:12:48 server cyrus/master[21
/deliver.db: cyrusdb error
Apr 5 04:12:48 server cyrus/lmtpunix[8473]: FATAL: lmtpd: unable to
init duplicate delivery database
Apr 5 04:12:48 server cyrus/master[21374]: process 8473 exited, status
75
Apr 5 04:12:48 server cyrus/master[21374]: service lmtpunix pid 8473 in
READY state: terminated
init duplicate delivery
database
unable to initialize inviromnent loc
All these errors keep going on and on. I remove the contents of the db
folder and deliver.db and restarted cyrus-imapd. I did not help. These
mistakes stopped occuring when I removed /var/lib/imap/socket folder but
I was
On Fri, 15 Apr 2005, Martine James (02 23 23 71 31) wrote:
I installed Cyrus one year ago and it used to work nicely with option
"duplicatesuppression" as set by default (YES)
Things went wrong four days ago with this message:
Apr 14 12:00:04 machine.etu.univ-rennes1.fr pop3[7118]: [ID 729713
loc
569]: [ID 157947
local6.error] FATAL: lmtpd: unable to init duplicate delivery database
this a sendmail log:
Apr 14 14:28:37 machine.etu.univ-rennes1.fr postfix/lmtp[10031]: [ID 197553
mail.info] 8D46E4D: to=<[EMAIL PROTECTED]>, orig_to=<[EMAIL PROTECTED]>,
relay=none, delay=0, status=d
ap/deliver.db: Invalid argument
> Nov 18 13:49:09 tux lmtpd[19879]: DBERROR: opening
> /var/lib/imap/deliver.db: cyrusdb error
> Nov 18 13:49:09 tux lmtpd[19879]: FATAL: lmtpd: unable to init
> duplicate
> delivery database
> Nov 18 13:49:09 tux ctl_cyrusdb[19874]: done checkpointing
18 13:49:09 tux lmtpd[19879]: DBERROR: opening
/var/lib/imap/deliver.db: Invalid argument
Nov 18 13:49:09 tux lmtpd[19879]: DBERROR: opening
/var/lib/imap/deliver.db: cyrusdb error
Nov 18 13:49:09 tux lmtpd[19879]: FATAL: lmtpd: unable to init duplicate
delivery database
Nov 18 13:49:09 tux
18 13:49:09 tux lmtpd[19879]: DBERROR: opening
/var/lib/imap/deliver.db: Invalid argument
Nov 18 13:49:09 tux lmtpd[19879]: DBERROR: opening
/var/lib/imap/deliver.db: cyrusdb error
Nov 18 13:49:09 tux lmtpd[19879]: FATAL: lmtpd: unable to init duplicate
delivery database
Nov 18 13:49:09 tux
14 matches
Mail list logo
