Displaying 20 results from an estimated 100 matches similar to: "assertion failed in mail-transaction-log-view.c"
2012 Sep 21
3
Dovecot 1.2.11 panic in mail-transaction-log-view?
I'm seeing this periodically in my logs for a specific user (followed by a backtrace which I've deleted from this post):
Panic: file dovecot-1.2.11/src/lib-index/mail-transaction-log-view.c: line 290 (mail_transaction_log_view_set): assertion failed: (min_file_seq != max_file_seq || max_file_seq != view->head->hdr.file_seq || max_file_offset != (uoff_t)-1 || min_file_offset <=
2011 Feb 08
1
How to recover a mail box from an assertion failure
I'm running Dovecot version 1.2.11 and getting this assertion error on a user's mail:
Panic: file /home/durket/dovecot-1.2.11/src/lib-index/mail-transaction-log-view.c: line 290 (mail_transaction_log_view_set): assertion failed: (min_file_seq != max_file_seq || max_file_seq != view->head->hdr.file_seq || max_file_offset != (uoff_t)-1 || min_file_offset <=
2004 Jun 18
3
1.0-test17
http://dovecot.org/test/
Just mbox fixes since 1.0-test16. The logic is simpler and more correct
now. Can anyone break it anymore? I actually tested it a while with
Evolution and several mailboxes and it didn't break at least
immediately. :)
Now maybe a few more days and I dare trying this thing myself with my
real mboxes (yes, I'm still using them).
Dovecot mailing list archives could
2009 Oct 15
2
Dovecot 1.2.6 segfault in imap_fetch_begin
We recently upgraded from Dovecot 1.2.4 to 1.2.6 (with the sieve patches
of course). Everything has been running quite well since the upgrade.
The occasional issue with assert-crashing when expunging has gone away.
However, one of our users seems to have triggered a new issue. She's
been the only one to see it, but whenever she logs in, her imap process
segfaults immediately. It appears that
2014 Feb 18
3
dovecot antispam plugin not found
Hello,
I'm trying to setup dovecot-antispam, and even though the configuration
and the installation seem to have gone well, dovecot is telling me it's
not finding it.
Here is the symptom:
schmitta at top-wifi ~> /usr/local/Cellar/dovecot/2.2.10/libexec/dovecot/imap -c ~/.dovecotzimbra.rc
Fatal: Plugin 'antispam' not found from directory
2014 Feb 19
1
dovecot antispam plugin not found
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Tue, 18 Feb 2014, Alan Schmitt wrote:
> I'm trying to setup dovecot-antispam, and even though the configuration
> and the installation seem to have gone well, dovecot is telling me it's
> not finding it.
>
> schmitta at top-wifi ~> /usr/local/Cellar/dovecot/2.2.10/libexec/dovecot/imap -c ~/.dovecotzimbra.rc
> Fatal:
2006 Feb 25
1
dovecot-1.0-beta3 in production
Hello there!
I've migrated our courier-imap production imap/pop server to dovecot 1.0-beta
few days ago. In general dovecot performs excellent, but i've encountered
several "bugs" in dovecot log:
--- snip ---
dovecot.log.1.gz:Feb 24 16:05:21 elfstone dovecot: imap(user3 at domain.tld):
Maildir /export/mail/domain.tld/user3 sync: UID inserted in the middle of
mailbox (47681
2008 Feb 27
4
Index corruption with squirrelmail.
Hi.
I don't know if the problem is related with squirrelmail or not, but I
started to have index corruption when I started to try squirrelmail.
Some informaton about my instalation:
dovecot 1.0.5-1 debian package with maildir
squirrelmail 1.4.9a-2 debian package
Some log information:
dovecot: 2008-02-27 08:39:39 Warning: IMAP(<please don't send spam to
me>): fscking index file
2010 Jan 28
0
assertion mail-transaction-log-view.c
I'm not sure how useful this is with optimization turned back on, but
here it is anyway. This was just a one off that happened last night:
Jan 27 20:49:05 gehenna17.rutgers.edu dovecot: IMAP(user): fscking index
file /rci/nqu/rci/u2/user/dovecot/.INBOX/dovecot.index
Jan 27 20:49:05 gehenna17.rutgers.edu dovecot: IMAP(user): Panic: file
mail-transaction-log-view.c: line 108
2005 Mar 06
4
mail-cache-transaction.c error
Hello all. I've just recently (this last weekend) migrated to Dovecot
on my FreeBSD 4.x box. So far, so good, I like it a lot, and plan on
moving mboxes to Maildirs sometime this next weekend.
BUT....I've currently run into a problem. I'm seeing an error when
one user account tries to access the INBOX from Squirrelmail:
Mar 6 16:50:59 cerebus dovecot: IMAP(problemuser): file
2005 May 26
0
Core dumps when opening an IMAP folder (Was: Re: 1.0-test70)
Hello Timo, I can reproduce this issue even with mmap_disable and
mmap_no_write set to yes, please see the following back trace:
$ gdb /usr/local/libexec/dovecot/imap /tmp/imap.core
GNU gdb 6.3
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and
you are welcome to change it and/or distribute copies of it under
certain conditions.
2006 Mar 30
0
sig11 with 1.0.beta3 on openbsd-i386
i recently helped a friend of mine migrate from imap-uw using mboxes to
dovecot on top of Maildirs and came up against two issues. this is
quite embarrassing as ive been claiming dovecot is Solid As A Rock(tm)
and hasn't ever given me any issues.
1. if dovecot runs out of file descriptors it will loop forever trying
to open new logging pipes. the code in question is at line 624 of
2009 Apr 13
1
Handling ENFILE
My mail server consumed all of its configured file table slots and
started returning ENFILE ("Too many open files in system") for many
operations. This wreaked havoc with dovecot-1.1.13. Here are some
areas where dovecot should detect and more gracefully handle ENFILE
error returns:
1. Deliver should report an error more helpful than "Unknown internal
error" when
2008 Jul 10
2
file mail-transaction-log-view.c: assertion failed (v1.0.12)
Hi all.
Looking at previous weeks logs I discovered strange errors: "file mail-transaction-log-view.c: assertion failed"
dovecot v 1.0.12
Server is hosting more than 500 virtual users. It is compleate dovecot error log; only my own mailbox is affected ...and imap folder affected is "dovecots mailing list" :)
While "Corrupted transaction log file" as far as I know
2005 Jan 18
0
test61 error
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
dovecot: Jan 18 10:48:39 Error: IMAP(bfg at noviforum.si): file
mail-transaction-log-view.c: line 138 (mail_transaction_log_view_set):
assertion failed: (min_file_seq != max_file_seq
~ || min_file_offset <= max_file_offset)
dovecot: Jan 18 10:48:39 Error: child 18837 (imap) killed with signal 6
dovecot: Jan 18 10:48:52 Info: imap-login: Login:
2008 Apr 30
0
dovecot-1.0.3: Backtrace:/usr/local/libexec/dovecot/imap
GNU gdb 6.7.1-debian
Copyright (C) 2007 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as
2013 Jan 25
1
assert in mail-transaction-log-file.c
I setup new server with dovecot 2.1.12 and mboxes from backup (moboxes
was used with dovecot 1.1.6).
OS: FreeBSD 8.3-STABLE, amd64.
All index files from dovecot 1.1.6 has been deleted.
Some times dovecot processes aborted.
E. g.
Jan 25 03:01:52 ost dovecot: lda(user at example.ru): Panic: file mail-transaction-log-file.c: line 1694 (mail_transaction_log_file_map): assertion failed:
2005 Jun 04
0
Crash and Assertion Error
I've attached two backtraces, one from a segfault and another from an
assertion error in imap. I've seen a couple of the same assertion and
this is the only segfault. It looks like they could be related. They
both have to do with indexing anyway...
The code is from CVS as of May 30.
The segfault happened while imap was doing searches for my pine filters.
I've also noticed that in
2008 May 07
1
Bug [1.1rc5]: Crash during "CPU architecture changed" index upgrade
Hello List,
We just migrated from a PPC Xserve to an Intel Xserve.
I used "rsync" to bring everyone's home directories over, and in the
back of my mind wondered about how it would handle the binary index
files... only one way to find out! :)
Once I tried to login to IMAP, I got the following results:
May 6 19:46:48 posh dovecot[1169]: IMAP(cabel): Rebuilding index
file
2008 Mar 08
2
suspect valgrind error in mail-index-map.c
Hi
At line 1118 of src//lib-index/mail-index-map.c, inside the function
mail_index_map_move_to_memory, there is:
mail_index_map_copy_header(map, map);
Valgrind is stating that "Source and destination overlap in memcpy".
I'm wondering if this code is just coping the same memory over itself,
or if it is doing something useful.
Regards,
Diego Liziero.
---
1104 void