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
Hi,
Am Dienstag, den 06.04.2010, 07:41 +0200 schrieb Simon Matter:
> > Hi,
> >
> > I got the following error in my log (cyrus 2.2.13-14+lenny3):
> >
> > --
> > Apr 5 04:12:48 server cyrus/lmtpunix[8473]: IOERROR:
> > lock_shared /var/lib/cyrus/deliver.db: Interrupted syste
Hi,
Am Dienstag, den 06.04.2010, 07:41 +0200 schrieb Simon Matter:
> >
> > I got the following error in my log (cyrus 2.2.13-14+lenny3):
> >
> > --
> > Apr 5 04:12:48 server cyrus/lmtpunix[8473]: IOERROR:
> > lock_shared /var/lib/cyrus/deliver.db: Interrupted system call
>
> Hi,
>
> I got the following error in my log (cyrus 2.2.13-14+lenny3):
>
> --
> Apr 5 04:12:48 server cyrus/lmtpunix[8473]: IOERROR:
> lock_shared /var/lib/cyrus/deliver.db: Interrupted system call
> Apr 5 04:12:48 server cyrus/lmtpunix[8473]: DBERROR:
> opening /var/lib/
On Wed, 2003-11-19 at 14:24, [EMAIL PROTECTED] wrote:
> Hello,
>
> i have the same problem. I think the reason is the db4
> database on redhat 9. I have the problem each day.
> But still no solution found !
> I will try it with another db4 version.
>
> My english is not good unfortunately ;)
