similar to: New Assert Failure

These two are from CVS version as of 2005-11-03. There have only been these two asserts and we've had over 45000 logins. ---------------------------------------------------------------------- dovecot: Nov 16 13:35:34 Error: 18439 imap(username): Corrupted transaction log file /mailhome/new/c/h/username/.imap/INBOX/dovecot.index.log: Append with UID 53103, but next_uid = 53104 dovecot: Nov

Just installed the version from CVS as of Oct. 27. I noticed three problems quite quickly: Still seeing "(imap) killed with signal 14" My INBOX closed with "access error" after reading it for a bit. There's nothing in the logs or anything, but this hasn't happened for quite a while now. There where quite a lot of incoming messages at the time and I was marking

Timo, Attached is gdb information from core dumps related to the following assert in test-80: IMAP(username): 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) My setup: Solaris 9, mbox format. test-80 compiled with gcc 4.0.1 using the following configure options: CC=gcc

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

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

I've attached a few assertion errors in imap. Any fixes or advice on where to look are appreciated. This is with the CVS version, current as of April 27. Todd Burroughs -------------- next part -------------- dovecot: Apr 27 00:00:45 Error: 5714 IMAP(chairman): file mail-index-transaction.c: line 808 (mail_index_update_ext): assertion failed: (seq > 0 && (seq <=

Sorry, this time I've no core file, (I forgot to set ulimit -c unlimited before starting dovecot) Regards, Diego. --- dovecot: Dec 09 08:26:52 Panic: IMAP(user): file mbox-sync-rewrite.c: line 590 (mbox_sync_rewrite): assertion failed: (mails[idx].from_offset == start_offset) dovecot: Dec 09 08:26:52 Error: IMAP(user): Raw backtrace: /usr/libexec/dovecot/imap [0x80f739e] ->

It might not be a fault in dovecot, as the user is accessing the folder locally with alpine while also running imap-sessions. However it would have been nice with a more graceful action than panic? The panic is preceeded by Error: Next message unexpectedly corrupted in mbox file PATH Panic: file mbox-sync.c: line 152 (mbox_sync_read_next_mail): assertion failed:

Hello all, I'm getting a very often panic on my local dovecot setup when accessing some of the local folders. Error message is always Oct 25 14:34:50 imap(irusskikh): Panic: file mbox-sync.c: line 665 (mbox_sync_handle_header): assertion failed: (mail_ctx->mail.from_offset + move_diff != 1 && mail_ctx->mail.from_offset + move_diff != 2) Oct 25 14:34:50 imap(irusskikh): Error:

Here is another crash we've been seeing recently in rc15 on Solaris 10. (gdb) bt full #0 0xff1c12a4 in ?? () No symbol table info available. #1 0xff140040 in ?? () No symbol table info available. #2 0x000786a8 in t_buffer_alloc (size=688976) at data-stack.c:346 __PRETTY_FUNCTION__ = "file %s: line %" #3 0x00078190 in t_pop () at data-stack.c:149 frame_block = (struct

Timo, My first assert in beta2. Syslog said: Jan 24 09:57:16 emerald dovecot: [ID 107833 mail.error] imap(user): Cached message offset 94625 is invalid for mbox file /var/mail/m/user Jan 24 09:57:16 emerald dovecot: [ID 107833 mail.error] imap(user): file mbox-sync.c: line 1471 (mbox_sync_do): assertion failed: (!sync_ctx->mbox->mbox_sync_dirty || (flags & MBOX_SYNC_UNDIRTY) == 0) Gdb

The log messages are attached. The core dump is at <https://www.dropbox.com/s/9i80ms7xkyxoqj7/core.26450?dl=0> The server is $ uname -a Linux sbh16.songbird.com 2.6.18-8.1.14.el5 #1 SMP Thu Sep 27 18:58:54 EDT 2007 i686 i686 i386 GNU/Linux -- Mark Sapiro <mark at msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

Hi, on a clustered Dovecot server installation that was recently moved from a shared GPFS filesystem to GFS2, occasional corruptions in the users' INBOXes started appearing, where a new incoming message would be appended directly after a block of NUL bytes, and be scanned by dovecot as being glued to the preceding message. I traced this to the file extension operation performed in

Dovecot 1.1.7 is running so smoothly that I gave up checking its log files daily. :) I've just had a look, and among the usual "IMAP(username): FETCH for mailbox Sent UID xx got too little data: xx vs xx" messages (that means that unfortunately sometimes some messages are still written truncated) I saw this assertion failure: file mbox-sync.c: line 1305

Here's a couple of assertion failures from CVS version as of Oct. 6. There's also a segfault but the core file was empty so I don't know if the log entries are much help. BTW, the searching speed using pine has dramatically improved, nice work! Todd ----------------------------------------- dovecot: Oct 12 12:04:28 Error: 20278 imap(username): file mail-index-sync-ext.c: line 155

Hi, An assertion that I haven't seen before: Apr 20 11:15:32 emerald dovecot: [ID 107833 mail.error] IMAP(user): file mbox-sync-rewrite.c: line 106 (mbox_sync_headers_add_space): assertion failed: (start_pos < data_size) gdb output from the core file of imap is attached. My setup: Solaris 9, mbox format, INBOX is NFS mounted from a Solaris 10 system, imap and imaps only. Jeff Earickson

Upgraded to dovecot 2.2.15 (built from sources on Fedora linux), saw intermittent panics: From dovecot:imap Error: Next message unexpectedly corrupted in mbox file /home/xxxx/mail/Junk E-mail at 1202197 Panic: file mbox-sync.c: line 152 (mbox_sync_read_next_mail): assertion failed: (sync_ctx->input->v_offset != mail_ctx->mail.from_offset || sync_ctx->input->eof) Error: Raw

To some users happens this assertion failure while deleting a message. dovecot: Mar 10 08:40:44 Panic: IMAP(user): file index-sync.c: line 39 (index_mailbox_set_recent_uid): assertion failed: (seq_range_exists (&ibox->recent_flags, uid)) dovecot: Mar 10 08:40:44 Error: IMAP(user): Raw backtrace: [see bleow] dovecot: Mar 10 08:40:44 Error: child 17683 (imap) killed with signal 6 And the

Here's a new one. It just started with the latest (April 8) CVS version. In index-mail-headers.c, line 622: fields = t_new(struct mail_cache_field, count); count is 0 I'm seeing this with several mailboxes. We're using mbox. Here's the error message and backtrace. dovecot: Apr 09 10:53:18 Error: 3348 IMAP(chairman): Trying to allocate 0 bytes dovecot: Apr 09

I just noticed one instance of this in the current CVS version: dovecot: Jul 18 15:25:48 Error: 5962 IMAP(mailuser): mbox sync: Expunged message reappeared in mailbox /mailhome/new/o/h/mailuser/mbox (UID 2834 < 2872) dovecot: Jul 18 15:25:48 Error: 5962 IMAP(mailuser): file mail-index-transaction.c: line 129 (mail_index_buffer_convert_to_uids): assertion failed: (*seq != 0) dovecot: Jul