On 2011-11-04 22:26, Timo Sirainen wrote:
Nov 4 15:10:42 mail dovecot: imap (t...@aaaone.net): Error: Corrupted
transaction log file /mail/3340444/.TestMails/dovecot.index.log seq 2:
indexid changed 1320419300 - 1320419441 (sync_offset=0)
Session A had TestMails open and created with index
On 2011-11-04 22:26, Timo Sirainen wrote:
Nov 4 15:10:42 mail dovecot: imap (t...@aaaone.net): Error: Corrupted
transaction log file /mail/3340444/.TestMails/dovecot.index.log seq 2:
indexid changed 1320419300 - 1320419441 (sync_offset=0)
Session A had TestMails open and created with index
On Fri, 2011-11-04 at 20:23 +0100, Peter Mogensen wrote:
I'm running Dovecot 2.0.15 and have a client which keeps causing
log-entries like:
Nov 4 15:10:42 mail dovecot: imap (t...@aaaone.net): Error: Corrupted
transaction log file /mail/3340444/.TestMails/dovecot.index.log seq 2:
On Tue, 2010-10-26 at 23:52 -0200, Andre Nathan wrote:
They're not happening all the time. It showed up two or three times in
the logs during the night.
A few errors of this kind appeared in the logs last night. The Log
synchronization error appears more frequently than Corrupted
transaction
On Tue, 2010-10-26 at 23:52 -0200, Andre Nathan wrote:
On Tue, 2010-10-26 at 22:39 +0200, Timo Sirainen wrote:
Have you set mmap_disable=yes?
Yep.
Just out of curiosity, is this setting really needed, or is it for
performance reasons? OCFS2 claims to support mmap:
On 27.10.2010, at 15.48, Andre Nathan wrote:
On Tue, 2010-10-26 at 23:52 -0200, Andre Nathan wrote:
On Tue, 2010-10-26 at 22:39 +0200, Timo Sirainen wrote:
Have you set mmap_disable=yes?
Yep.
Just out of curiosity, is this setting really needed, or is it for
performance reasons? OCFS2
Hello
I run dovecot 2.0.6 on a two-machine cluster using OCFS2 as the file
system. I have some error messages like these in my log:
Oct 25 01:07:50 box5 dovecot: lmtp(8886,
suporte=100br@lmtp1.prv.f1.k8.com.br): Error: Corrupted transaction
log file
On 26.10.2010, at 19.58, Andre Nathan wrote:
I run dovecot 2.0.6 on a two-machine cluster using OCFS2 as the file
system. I have some error messages like these in my log:
Oct 25 01:07:50 box5 dovecot: lmtp(8886,
suporte=100br@lmtp1.prv.f1.k8.com.br): Error: Corrupted transaction
log
On Tue, 2010-10-26 at 22:39 +0200, Timo Sirainen wrote:
Have you set mmap_disable=yes?
Yep.
Those errors should fix themselves automatically. Still, it's not very good
if they keep happening. Sooner or later they will cause user visible problems.
They're not happening all the time. It
On Sun, 2008-10-05 at 19:20 -0400, Steven Winikoff wrote:
Oct 3 17:52:21 alcor dovecot: imap[14973] , NNN.NNN.NN.NNN: Corrupted
transaction log file /home//mail/.imap/sent-mail/dovecot.index.log:
record size too small (type=0xcd91, offset=8180, size=0)
This and some other bugs
On Fri, 2008-10-10 at 14:22 -0400, Steven Winikoff wrote:
Oct 10 04:48:46 alcor dovecot: Panic: pop3-login: file
client-authenticate.c: line 163 (sasl_callback): assertion failed:
(!client-destroyed || reply == SASL_SERVER_REPLY_CLIENT_ERROR || reply ==
SASL_SERVER_REPLY_MASTER_FAILED)
This and some other bugs are now fixed by this:
http://hg.dovecot.org/dovecot-1.1/rev/262c52055f2a
Thank you! Both for this and for
http://hg.dovecot.org/dovecot-1.1/rev/a0693aec0245
- Steven
Steven Winikoff
2) recompiled dovecot without optimization (ie, gcc -O0 instead of -O2)
(as per http://www.mail-archive.com/dovecot@dovecot.org/msg12936.html)
The problem here turned out to be a bug in Sun CC (and gcc -O2
apparently worked after all, so maybe a problem with testing).
Thanks. I'll
On Oct 10, 2008, at 9:22 PM, Steven Winikoff wrote:
I had hoped v1.1.3 would have fixed this. But perhaps this is also
related to the disk quota issues. Are there any other errors that are
logged before the assert?
Nothing obvious, I'm afraid. For example, this occurence is typical
of
the
[...]
Oct 8 13:56:40 alcor dovecot: Panic: imap[15143] USER4,
NNN.NNN.NNN.NNN: file index-mail.c: line 1091 (index_mail_close):
assertion failed: (!mail-data.destroying_stream)
Hmm. I think I thought of a different assert before when commenting.
This assert should be fixed by 1.1.4 /
On Tue, 2008-09-30 at 02:08 -0400, Steven Winikoff wrote:
Sep 30 00:09:56 alcor dovecot: pop3[5006] , NNN.NNN.NN.NNN: Corrupted
transaction log file /home//.imap/INBOX/dovecot.index.log: record size
too small (type=0x40, offset=12224, size=0)
..
I've been working around the
I've been working around the problem by deleting the contents of
~user/.imap for affected users, but I'd really prefer to fix it
properly. :-) Any suggestions would be gratefully received.
I think this should get fixed by itself? Although the first login fails,
the next one should succeed.
I recently upgradeded dovecot on one of our servers from version 1.0.10
to version 1.1.3. Ever since, we've been seeing occasional errors
similar to this sequence (with the username and IP addresses elided):
Sep 30 00:09:56 alcor dovecot: pop3-login: Login: [4954], ,
NNN.NNN.NN.NNN
On Fri, 2007-12-07 at 14:33 +, Daniel Watts wrote:
Following errors have happened quite a bit:
Dec 7 14:19:26 [EMAIL PROTECTED]/tg3 dovecot: IMAP([EMAIL PROTECTED]):
Transaction log file
/home/virtual/mydomain.com/home/peter.day/Maildir/.Trash/dovecot.index.log:
marked corrupted
Following errors have happened quite a bit:
Dec 7 14:19:26 [EMAIL PROTECTED]/tg3 dovecot: IMAP([EMAIL PROTECTED]):
Transaction log file
/home/virtual/mydomain.com/home/peter.day/Maildir/.Trash/dovecot.index.log:
marked corrupted
Dec 7 14:19:26 [EMAIL PROTECTED]/tg3 dovecot: IMAP([EMAIL
[snip]
Dec 7 14:19:26 [EMAIL PROTECTED]/tg3 dovecot: IMAP([EMAIL PROTECTED]):
Corrupted transaction log file
/home/virtual/mydomain.com/home/peter.day/Maildir/.Trash/dovecot.index.log:
Append with UID 50, but next_uid = 15870
This is the real error. What kind of a system do you
On Fri, 2007-12-07 at 15:01 +, Daniel Watts wrote:
Shouldn't Dovecot be able to recover from this?
It does, that's why there are those marked corrupted errors. But it
probably does cause the current operation to fail. v1.1 handles this by
logging the error but continuing
22 matches
Mail list logo
