similar to: 1.0alpha1: new assert/core

Hi, Two cores over the weekend, same assert message in syslog: imap(user): file message-body-search.c: line 393 (message_body_search_ctx): assertion failed: (input->v_offset <= part->physical_pos) Setup: Solaris 9, imap usage only, mbox format, dovecot compiled with gcc 4.0.1. gdb sessions of the two core files attached. Let me know if you need further analysis of the cores.

My setup: Solaris 9, dovecot built with gcc 4.0.2. Mailboxes on remote NFS file mount from another S9 box (mbox format), index files local disk. IMAP usage only. Dovecot build like so: VERSION=1.0.alpha5 CC=gcc CFLAGS="-g -O" CPPFLAGS=-I/opt/openssl/include \ LDFLAGS=-L/opt/openssl/lib \ ./configure --prefix=/opt/dovecot.$VERSION --with-ssl=openssl \ --with-ssldir=/opt/openssl/ssl

Hi, Wow, I haven't had an assert/core in dovecot in a long time. Here goes: Setup: Solaris 10, dovecot built with gcc 4.1.1, imap and imaps only. User's home directory lives on a ZFS filesystem, but I don't think that makes a difference. So does every other user here (>3K). Assert: IMAP(mulepri): file message-body-search.c: line 393 (message_body_search_ctx): assertion failed:

Hi, My second case of this assert, gdb analysis of the core dump attached. My setup: Solaris 9, dovecot built with gcc 4.0.2, mbox format, imap usage only. INBOX is NFS mounted from another Solaris 9 system, index files are local. Syslog complaint is: imap(user): file message-body-search.c: line 414 (message_body_search_ctx): assertion failed: (input->v_offset == part->physical_pos +

Hi, An assert and core with 1.0alpha3 on Solaris 9, mbox format, imap only, compiled with gcc 4.0.1. The syslog message was: imap(user): file message-body-search.c: line 393 (message_body_search_ctx): assertion failed: (input->v_offset <= part->physical_pos) gdb core dump analysis is attached. Jeff Earickson Colby College -------------- next part -------------- Script started on

Panic: IMAP(user): file message-parser.c: line 684 (preparsed_parse_next_header_init): assertion failed: (ctx->part- >physical_pos >= ctx->input->v_offset) Linux 2.6.24-19-386 Maildir on ext3 Looks similar to but different from http://dovecot.org/list/dovecot/2008-June/031523.html . #0 0xb7faf410 in __kernel_vsyscall () #1 0xb7e6f085 in raise () from

Hi, I did a bit of digging into the assertions from mbox-rewrite.c (hdr_parsed_size.physical_size == hdr_size). Every time it happens, hdr_size is 0, while hdr_parsed_size.physical_size is non-zero (presumably the correct value). Does this help track it down? I can't manage to get hold of an mbox that causes this though. Another infrequent assertion that's popped up: file

When I do a search in squirrelmail, it will start giving several results, but then fails. I use squirrelmail via https. maillog reveils: file message-body-search.c: line 391 (message_body_search_ctx): assertion failed: (input->v_offset <= part->physical_pos) Squirrel mail browser interface reveils: ERROR: Connection dropped by IMAP server. Query: SEARCH CHARSET UTF-8 ALL TEXT {4}

When I do a search in squirrelmail, it will start giving several results, but then fails. I use squirrelmail via https. maillog reveils: file message-body-search.c: line 391 (message_body_search_ctx): assertion failed: (input->v_offset <= part->physical_pos) Squirrel mail browser interface reveils: ERROR: Connection dropped by IMAP server. Query: SEARCH CHARSET UTF-8 ALL TEXT {4}

Hello. Recently I've got following assertion on my server with dovecot 0.99.14 when searching: file message-body-search.c: line 391 (message_body_search_ctx): assertion failed: (input->v_offset <= part->physical_pos) -- Ivan Pesin N-iX Newcomp GmbH

Implements more verbose imap logging (when client exits). Similar to existing logging in POP3. Due to the nature of imap and my incomplete understanding (of the dovecot code) the session statistics reported have varying accuracy. Much better than nothing IMO. Cheers, Jens ----------------------------------------------------------------------- 'This mail automatically becomes portable

Hi, Been using Dovecot for a few weeks now, must say it's very good.. I've been looking for a 'drop in' replacement for UWImap for ages! :) but just recently It's been giving me a few problem, I haven't tracked down exactly what causes the problem yet (I'm using Apple Mail on OS X 10.2.6) but after a good mail session it keep trying to log in over and over again..

Hi, I've been running 1.0alpha1 in production since August 18, and got my first assert and core yesterday. Otherwise it has been running flawlessly. My setup: Sun E220R, Solaris 9, compiled dovecot with gcc 4.0.1, configured dovecot like so: #!/usr/bin/sh VERSION=1.0-alpha1 CC=gcc CFLAGS="-g -O" CPPFLAGS=-I/opt/openssl/include LDFLAGS=-L/opt/openssl/lib \ ./configure

Hi, Today's core dump from 1.0alpha1 came from a syslog message of: IMAP(user): pool_data_stack_realloc(): stack frame changed gdb info on the resulting core dump attached. Question: how many people are building/using dovecot 1.0alpha1 with gcc 4.0.1 versus gcc 3.4.x? I am wondering if these issues come from the compiler instead of dovecot itself? Jeff Earickson Colby College

Same as reported before: Assert: IMAP(user): file mbox-sync-update.c: line 442 (mbox_sync_update_header_from): assertion failed: (ctx->mail.uid == 0 || ctx->mail.uid_broken || ctx->mail.uid == mail->uid) Setup: 1.0alpha1 on Solaris 9, built with gcc 4.0.1 Debug output of the core is attached. Jeff Earickson Colby College -------------- next part -------------- Script started on

Timo, Output of gdb session on the core file attached. This one only produced the following syslog: IMAP(user): UIDs broken with partial sync in mbox file /var/mail/r/user with no assert. Setup: Solaris 9, gcc 4.0.1 for dovecot build. Jeff Earickson Colby College -------------- next part -------------- Script started on Thu Sep 08 10:05:53 2005 %gdb imap core.rtohara GNU gdb 6.3 Copyright

I've noticed a burst of about 12000 of these mbox-rewrite msgs in the log, spread over about 10 minutes. They are always for the same person (XXX'd out here), and have not occurred before or since. There's no evidence of device problems in the message log. Jan 10 17:46:43 ls1 imap-login: Login: XXX [::ffff:10.2.0.1] Jan 10 17:46:43 ls1 imap(XXX): file mbox-rewrite.c: line 429

Hi, I've been using 1.0 but moved to beta to see if it works before release. Both b14 and b15 dies sometimes when accessing folders. Last time I fixed this by moving one message from folder to another and then back. Next I'm trying to build this with debugging enabled. Tomppa > Feb 14 11:52:33 dovecot: [ID 107833 mail.crit] IMAP(tomppa): file message-parser.c: line 674: assertion

Hi, there is a line in TODO: "- sieve-cmu.c crash: i_assert(buf->used - 1 == part->body_size.physical_size); ". Yes, we've really seen this crash. Therefore we upgraded to dovecot-1.2.3 with dovecot-1.2-sieve-0.1.11 in order to use sieve plugin (i.e. not cmu-sieve). We use Solaris 10 on Sun servers, we don't use NFS. However, unfortunately, dovecot with sieve crashes

Found a new segfault in imap. The first log entry always happens on my mailbox, but doesn't seem to affect anything. This is CVS version from Aug. 15. dovecot: Aug 21 17:16:56 Error: 28017 IMAP(todd): Corrupted index cache file /mailhome/new/t/b/todd/.imap/INBOX/dovecot.index.cache: Duplicated field in header: hdr.RESENT-TO dovecot: Aug 21 17:19:44 Error: child 28017 (imap) killed with