similar to: Dovecot 2.2.5: Panic: file mail-transaction-log.c: line 350 (mail_transaction_log_set_mailbox_sync_pos)

Hi! I've now seen this assertion failure from lmtp (most frequent), pop3 (next frequent), and imap (rarely). It didn't start happening until the number of accounts on the server was increased into the 10k-25k range. It happens when index->file_lock is a read lock and mail_index_lock is called asking for a write lock. Dovecot 2.x dies at the assertion on line 62 of mail-index-lock.c

Hi, While running imaptest with "clients=50 seed=123 msgs=100000000 random secs=600", I got errors : "Error: user at domain.com[55]: Unexpected BYE: * BYE IMAP session state is inconsistent, please relogin.". dovecot.log : Apr 03 10:23:47 imap(user at domain.com): Panic: file index- transaction.c: line 145 (index_transaction_rollback): assertion failed:

Hi, I've recently started using dovecot-lda to handle my local maildir deliveries from Exim. Unfortunately I've been experiencing the occasional failed delivery - My Exim logs were showing: Child process of virtual_dovecot_delivery transport (running command "/usr/local/libexec/dovecot/dovecot-lda -d $local_part@$domain -f $sender_address -a

Hi everybody, I'm runing dovecot 2.2.12 and a user mailbox got the "broken sync positions in index file" error twice in the last 20 days. this is an extract from the maillog maillog First Error -------------------- Mar 23 16:13:25 andromeda dovecot: pop3-login: Login: user=<myuser at mydomain.com>, method=PLAIN, rip=187.237.107.24, lip=207.7.90.83, mpid=3983,

Program received signal SIGSEGV, Segmentation fault. 0x00007f1975cccdee in expire_mailbox_transaction_commit (t=<value optimized out>, changes_r=<value optimized out>) at expire-plugin.c:169 169 } else if (strcmp(value, "0") == 0) { (gdb) bt #0 0x00007f1975cccdee in expire_mailbox_transaction_commit (t=<value optimized out>,

Hi, we are actually deploying a new IMAP-Server, targeting dovecot 2.1.17. Unfortunately, our tests with imaptest did not succeed, were ending in core dumps. We did this test: ./imaptest host=example.com port=143 user=strack pass=secret disconnect_quit no_pipelining mbox=dovecot-crlf That's what we get in dovecot's log: Sep 10 11:17:04 imap-login: Info: Login: user=<strack>,

Core dump upon client login with latest changes, gdb attached: ==> /var/log/dovecot.log <== Jun 8 19:26:05 spectre dovecot: master: Dovecot v2.0.beta5 (2d6cf78982dc) starting up Jun 8 19:26:21 spectre dovecot: imap-login: Login: user=<tlx at leuxner.net>, method=PLAIN, rip=10.10.10.10, lip=1.2.3.4, mpid=9997, TLS Jun 8 19:26:21 spectre dovecot: master: Error: service(imap): child

hello. Today I had a problem (core dumped) in a dovecot installation update yesterday. After many hours I found that when one settings "protocol imap" the option "replication" causes (core dumped). In this server settings "replication" was removed leaving only the "protocol imap" (my error) I send my documentation error so they can add a validation and

Hi I understand the crash below is caused by filesystem quota. I just report it because perhaps it could have a more graceful failure. Apr 29 09:39:17 danceny dovecot: dsync-local(jdoe): Error: Mailbox Sent: Saving failed: Not enough disk space Apr 29 09:39:17 danceny syslogd[165]: last message repeated 4 times Apr 29 09:39:17 danceny dovecot: doveadm: Error: dsync-remote(jdoe): Error: Cached

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, yesterday i tried to setup Dovecot with Solr (3.6.2) + Tika (1.8) for FTS. i used a fresh Debian 8.0 system in the beginning with Dovecot 2.2.13 from the Debian repository. After i got some issues with Tika/Dovecot and i read on the mailinglist that these problems where fixed in 2.2.14+, so i tried 2.2.18. With 2.2.18 i get panics with big (ok... huge) attachments. Most mailboxes (and their

Hi Timo, Was getting the following error repeatedly in my mail client (squirremail) "error: connection dropped by IMAP server" Looked at the logs for this user and found the following: Nov 19 17:11:32 mink dovecot: IMAP(bobuser at maildom.com): broken sync positions in index file /virtual/store2/mail/s/bobuser_maildom.com/Maildir/dovecot.index Nov 19 17:11:32 mink dovecot:

Latest HG dies upon client login. Rolling back to 2.0.rc2 (7dd7adba1c9e) restores functionality. Dump attached. Jul 17 07:31:04 spectre dovecot: master: Dovecot v2.0.rc2 (875598cd7e26) starting up [?] Jul 17 07:32:06 spectre dovecot: master: Error: service(imap): child 29169 killed with signal 11 (core dumped) GNU gdb 6.8-debian Copyright (C) 2008 Free Software Foundation, Inc. License GPLv3+:

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

Ok, thanks a lot for the reply. I'll keep digging then :) On 12/21/18 4:19 PM, Aki Tuomi wrote: > On 21.12.2018 15.01, Tim Mohlmann via dovecot wrote: >> 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

Hi, I have set up replication, but dovecot-lda now fails with a segmentation fault. Problem seems to be in replication/replication-plugin.c line 253: struct replication_user *ruser = REPLICATION_USER_CONTEXT(ctx->ns->user); resulting in ruser = 0x0 # 2.2.15: /usr/local/etc/dovecot/dovecot.conf # Pigeonhole version 0.4.6 (3e924b1b6c5c+) # OS: FreeBSD 10.0-RELEASE amd64 gdb

On 21.12.2018 15.01, Tim Mohlmann via dovecot wrote: > 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

Hi All, I upgrade my mail server from doveot 1.1.7 to 2.2.13 and encounter problems with file locking issues. The server has around 400 clients using IMAP and I get tons of "Warning: fscking index file .. dovecot.index" and "Error: Corrupted transaction log". Sometimes the transaction log problem is followed by "Panic: file mail-transaction-log.c: line 350

I'm really sorry, but it was a long day yesterday. I forgot to mention that I used alpine:edge (based on the alpine master branch) image to set up the build environment. So there were some version changes. dovecot --version: 2.3.3 (dcead646b) apk info musl: musl-1.1.20-r2 description: the musl c library (libc) implementation Configuration was unchanged wrt to my first mail. Maybe it's

OS: CentOS 7 x86_64 Dovecot version: 2.2.31 (65cde28) (GhettoForge RPM) Filesystem: GlusterFS, but working on changing that. Only one server is receiving activity. Was getting messages about corrupt dovecot.map.index files. Changed to dotlock from fcntl to try to fix that. Reading symbols from /usr/libexec/dovecot/imap...(no debugging symbols found)...done. [New LWP 74012] Core was generated by