similar to: test80: assert/core debug info

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

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

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

Timo, Test-80, running on our production IMAP server. Setup: Solaris 9, compiled with gcc 4.0.1, mbox format, configured like so: VERSION=test80 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 --with-rawlog --enable-debug > configure.out Still seeing

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

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:

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

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

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

If the first message in an mbox is deleted by an external program, therefore removing the X-IMAPbase header, an error such as the following occurs. Apr 9 20:10:51 sm1 dovecot: imap(306812): file mbox-sync-update.c: line 460 (mbox_sync_update_header_from): assertion failed: (ctx->mail.uid == 0 || ctx->mail.uid_broken || ctx->mail.uid == mail->uid) This prevents the user from logging

http://dovecot.org/test/ If nothing new comes up in a few days, this will become the first release in 1.0alpha series. Authentication code got some larger changes, so something might be broken in it. - inotify patch by Johannes Berg - Send untagged FLAGS / PERMANENTFLAGS replies if keywords list changed. - Don't even open mbox file when changing flags and mbox_lazy_writes=yes - Fixed

We are currently running dovecot 2.2.rc3. I am trying to 'dsync mirror' old Qpopper/mbox inboxes to our new Dovecot/mdbox servers. For most of the several thousand accounts, it works without issue. But there are a handful of accounts that are generating the following errors. dsync(joe): Error: Sync failed for mbox file /var/opt/migrate/users/joe/inbox: seq=981 uid=981 uid_broken=0

hi all, i've built dovecot: Sep 09 18:04:24 Info: Dovecot v1.0-test80 starting up on OSX 10.4.2. in addition to pgsql auth, which is working 4 me, i'd like to step-by-step verify simple passwd-file authentication/testing. unfortunately, i'm having a problem with the login process NOT FINDING the ".../cur" dir. here are the details .... my config includes: ...

Has anyone else encountered weird date behavior with mbox-style folders? I am nearly ready to bite the bullet and convert my UW imap hierarchy (which is in mbx format) to Dovecot. In so doing, I need to convert each UW-specific mbx-format mailboxes to the more portable mbox format, which Dovecot can read. (This is done with the 'mbxcvt' utility that's part of UW.) I am then

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

Hi Timo, Awhile back I'd written about making changes to some of the log levels that dovecot writes to to stop the process from writing these to monitor. I wanted to run a few changes by you for this, just to make sure these won't cause problems somewhere else. And to send this to the list, in case anyone else wants to make similar changes in the future. In the file

Here's a new one with CVS version from 2005-11-03. The mbox size is currently 42951945 bytes. dovecot: Nov 24 12:05:50 Error: 11520 imap(username): Unexpectedly lost From-line at offset 33979772 from mbox file /mailhome/new/a/l/username/mbox dovecot: Nov 24 12:05:50 Error: 11520 imap(username): file mbox-sync-rewrite.c: line 552 (mbox_sync_rewrite): assertion failed:

I've been getting a few of these errors on a couple different mboxes. This is using the CVS version as of May 14. So far, these are the only errors and it looks like most/all of the older ones are gone. (maybe I shouldn't say that ;-) dovecot: May 16 17:41:07 Error: 20973 IMAP(todd.bluegenesis.com): file mbox-sync.c: line 1165 (mbox_sync_handle_eof_updates): assertion failed:

Hi, When the Dovecot 1.0.rc19 IMAP server encounters X-UID headers with gaps in them, it hangs indefinitely. I've attached a sample mailbox (in mbox format) which repeatably exhibits this behavior. The mbox contains only three messages with the following X-UIDs in order: 774, 785, 787. If I remove the X-UID headers from each message, Dovecot handles the mailbox without any problems. UW-IMAP