similar to: beta8: cores on corrupted index file

Hello, Latest HG assert crashes with imap(user): Panic: file mail-storage.c: line 1836 (mailbox_transaction_begin): assertion failed: (box->opened) Full backtrace is attached. Thanks, e-frog -------------- next part -------------- Core was generated by `dovecot/imap'. Program terminated with signal SIGABRT, Aborted. #0 0xb775d424 in __kernel_vsyscall () (gdb) bt full #0 0xb775d424 in

We uograded our dovecot from version 2.1.10 -> 2.10.12, but within the first hour of use, dovecot-lda would segfault during delivery. This left a lock file lying around causing the user's mail readers to hang; much hilarity ensues. All further deliveries to the same user will result in a crash. The only thing that fixes this condition is to blow away the user's INBOX cache index.

100% reproducible. User is using alpine to write an email. Continue postponed composition (answering "No" won't erase it)? y -> [>Empty folder! No messages really postponed!<] Can't delete {mproxy.charite.de/ssl/novalidate-cert/user=theusername}postponed-msgs Setup: ====== http://wiki2.dovecot.org/HowTo/ImapcProxy coredump available for further inspection Full

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

My setup: Solaris 9, built with gcc 4.0.2 (I now have gcc 4.1 installed on my system, but have not rebuilt dovecot). A couple of asserts and cores in the last few days: Mar 1 09:25:13 emerald dovecot: [ID 107833 mail.error] imap(tmwillia): file mbox-sync.c: line 1471 (mbox_sync_do): assertion failed: (!sync_ctx->mbox->mbox_sync_dirty || (flags & MBOX_SYNC_UNDIRTY) == 0) Mar 1

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

Timo, I upgraded from alpha3 to alpha4 yesterday, and I am seeing a few of the following asserts: imap(user): file mbox-lock.c: line 379 (mbox_lock_fcntl): assertion failed: (lock_type == F_UNLCK) Gdb info on a couple of the cores is attached. It looks like the arg lock_type for mbox_lock_fcntl() is not getting passed in correctly, like the enum "enum mbox_lock_type type" in

Hi, sorry for the double post, I stupidly composed this as a reply to an earlier mail, which causes it to appear in an older thread. Posting again so it doesn't get lost in the archives: dovecot 1.1.7 reliably crashes every time I try to open a mailbox using IMAP. Error in the logs: dovecot: Dec 02 23:14:15 Error: setmntent(/etc/mtab) failed: No such file or directory dovecot: Dec 02

I would like to report a bug we are seeing on an new deployment here: Linux: Debian Jessie, inside a Docker container Dovecot version: 2.2.23 (806d709) / 2.2.23-1~bpo8+1 doveconf -n: http://pastebin.com/2xA2xuRw Filesystem: CephFS - Jewel After migrating our users from our old server to our new one we can't access a few mailboxes. Backtrace follows: root at dovecot:/# gdb --args

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

On 11.05.2016 22:45, Daniel van Ham Colchete wrote: > I can confirm that this bug also happens on the latest version available: > > root at dovecot:/# dovecot --version > 2.2.devel (ebf2e93) > root at dovecot:/# dpkg -l|grep dovecot > ii dovecot-core 2:2.2.24-1~auto+23 amd64 > secure POP3/IMAP server - core files > ii dovecot-dbg

hi- i'm setting up an imap proxy in front of a novell groupwise server. it seems to so far be partially working, but dovecot is having trouble in certain cases. i expect that it's ultimately due to what i believe is a very poor implementation of imap provided by groupwise [at least based on other experiences in the past] - but that's a big part of why i'd like to have

On 10/05/2015 5:47 PM, Timo Sirainen wrote: >> How do I go about debugging this further? How do I go about >> getting a backtrace on what is essentially a child process that >> doesn't produce a core? (Note that my installation normally does >> produce cores when it crashes, so there's something different about >> these indexer processes..) > > One

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Hi all, we're experiencing "Out of Memory" Problems caused by Sieve-Filters delivering mail to huge IMAP folders. From the logs, I'm beginning to think the problem is that the sieve/lmtp process loads the "dovecot.index.cache" file apparently twice into memory to do something with it. We've set our memory limit per

I've managed to re-compile the alpine packages inside the container, creating the debug symbols and disabling compile time optimizations, as they also disturbed the backtrace. The following output looks much more meaningful. But unfortunately there are still some symbols missing for lucene-core. Let me know if this is enough to work with. (It doesn't seem to be musl after all?) Reading

Hi all, we're having a bad day with email :) I have a user who was complaining of poor performance today when opening mailboxes. Total time to open the box was about 1 minute. Upon truss'ing the imap process during an open, I saw the trace quoted below at the end of the email. As you can see, for each "FETCH" line of response, we were seeing dovecot do a ton of work-- mmaping

Hi, I now this is kinda impolite to ask, but I would like some feedback on this issue. I'm representing the Mailu user group here, plus the fact that my own production server is affected and starts to crash due to file corruption as a result of the indexer-worker segfaults. Last night my server became unavailable with logs like: Error: imap(tim at

The Asterisk development team has released versions 1.2.28, 1.4.19.1, and 1.6.0-beta8. All of these releases contain a security patch for the vulnerability described in the AST-2008-006 security advisory. 1.6.0-beta8 is also a regular update to the 1.6.0 series with a number of bug fixes over the previous beta release. Early last year, we made some modifications to the IAX2 channel driver to

The Asterisk development team has released versions 1.2.28, 1.4.19.1, and 1.6.0-beta8. All of these releases contain a security patch for the vulnerability described in the AST-2008-006 security advisory. 1.6.0-beta8 is also a regular update to the 1.6.0 series with a number of bug fixes over the previous beta release. Early last year, we made some modifications to the IAX2 channel driver to

Next release will probably be called 1.0.rc1. People just don't seem to like the beta name in the version number. :) Also I think we're nearing the final v1.0. * Fixed a security hole with mbox: "1 LIST .. *" command could list all directories and files under the mbox root directory, so if your mails were stored in eg. /var/mail/%u/ directory, the command would list