similar to: dovecot/imap crashes on Centos 7

Hi all, I have a Dovecot core that I am trying to track down, in an attempt to replicate so I can log a bug report, and am hoping others might be able to help me as I?m reaching my limit. My working theory is that two user sessions are active at the same time, one of the sessions is ?mid-search? (or perhaps in idle state) on a virtual folder where the number of results is zero (due to a null

Hi, Got a new one on 2.2.13: Sep 19 04:11:39 moxi dovecot: imap(cen at cor.ed): Error: Log synchronization error at seq=3,offset=144 for /Maildir/.Spam/dovecot.index: Extension record update for invalid uid=494 Sep 19 04:11:39 moxi dovecot: imap(cen at cor.ed): Warning: fscking index file /Maildir/.Spam/dovecot.index Sep 19 04:11:39 moxi dovecot: imap(cen at cor.ed): Panic: file

We have started seeing index corruption ever since we upgraded (we believe) our imap servers from SL6 to Centos 7. Mail/Indexes are stored on Netapps mounted via NFS. We have 2 lvs servers running surealived in dr/wlc, 2 directors and 6 backend imap/pop servers. Most of the core dumps I've looked at for different users are like "Backtrace 2" with some variations on folder path.

Hi, I got all excited about IMAP NOTIFY support and tried enabling mailbox_list_index on my server. Unfortunately, I rather quickly ran into trouble of the segfault variety. This prevented me from doing basic things like seeing the contents of some of my folders. Disabling mailbox_list_index got me back up and running, but... darnit, that's annoying. The only message I got in my log file

Hello, I have a segfault problem, and I can not resolve myself. The details below (stack trace, config....). Maybe important to reproduce, everithing working well until I connect with SoGo ActiveSync (SoGo web, and other IMAP clients are working well). So maybe the SoGo send something magical command if the user client use the ActiveSyn... (the IMAP debug attached too) Thanks, Balazs Toth

Hi, I have one user constantly crashing with: Core was generated by `dovecot/imap'. Program terminated with signal 11, Segmentation fault. #0 0x007e5b7c in mailbox_list_notify_next (notify=0x0, rec_r=0xbfee8f00) at mailbox-list-notify.c:28 28 return notify->list->v.notify_next(notify, rec_r); (gdb) bt #0 0x007e5b7c in mailbox_list_notify_next (notify=0x0,

Hi Timo, some imap processes seems to have some problems. Regards, Pascal -------------- next part -------------- Core was generated by `dovecot/imap'. Program terminated with signal 6, Aborted. #0 0x00007fbf87b25475 in raise () from /lib/x86_64-linux-gnu/libc.so.6 (gdb) bt full #0 0x00007fbf87b25475 in raise () from /lib/x86_64-linux-gnu/libc.so.6 No symbol table info available. #1

Hi! After upgrading from Debian wheezy with (self compiled) dovecot 2.2.15 to Debian jessie with (self compiled) 2.2.24, I observe the following segmentation fault in the logs: Jun 7 09:23:09 imap dovecot: imap(user at example.com): Error: read(<imap client>) failed: read(size=8003) failed: Connection reset by peer (uid=0, box=trash) Jun 7 09:23:09 imap dovecot: imap(user at

I noticed i had mail_location wrong, i was specifying INDEX=/dovecot-index instead of INDEX=~/dovecot-index so i modifed and restarted dovecot, one of my techs that happens to have thousands of emails reopened her mail and this showed up in the log. Not sure if this is critical or if more info/dovecot -n is needed dovecot: 2009-05-05 14:06:38 Panic: imap <REMOVED>: file mail-search.c: line

We had to move our dovecot from one server to another and used rsync to move the mail but it took us some time.. In our log at the new server, we are getting a lot of these..: 2010/10/08 23:28:23 imap(emailadr): Error: Index /opt/vmail/ba-avis.no/bpe/mail/.Nettforum/dovecot.index: Lost log for seq=22 offset=25248 2010/10/08 23:28:23 imap(emailadr): Warning: fscking index file

Program terminated with signal 6 GNU gdb (GDB) 7.0-debian Copyright (C) 2009 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was

See below: ----- Forwarded message from root <root at postamt.charite.de> ----- From: root <root at postamt.charite.de> Date: Sun, 24 Aug 2008 12:10:26 +0200 (CEST) To: ralf.hildebrandt at charite.de Subject: Backtrace:/usr/local/libexec/dovecot/imap GNU gdb 6.8-debian Copyright (C) 2008 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later

As promised, here is the bug report: # dovecot -n # 1.1.alpha2: /usr/local/etc/dovecot.conf protocols: imap pop3 ssl_cert_file: /etc/postfix/server.pem ssl_key_file: /etc/postfix/server.pem login_dir: /usr/local/var/run/dovecot/login login_executable(default): /usr/local/libexec/dovecot/imap-login login_executable(imap): /usr/local/libexec/dovecot/imap-login login_executable(pop3):

Version: 2.2.12 OS: Debian wheezy x86_64 2014 Mar 11 20:06:53 ptb-test imap(flor_hardy): Panic: file mail-index-map.c: line 547 (mail_index_map_lookup_seq_range): assertion failed: (first_uid > 0) 2014 Mar 11 20:06:53 ptb-test imap(flor_hardy): Fatal: master: service(imap): child 2760 killed with signal 6 (core dumped) GNU gdb (GDB) 7.4.1-debian Copyright (C) 2012 Free Software Foundation,

Hi, I've regularly crashes with a certain virtual folder. Erasing the dovecot-index.* files help just for few hours/days. Here are to backtraces: Core was generated by `imap'. Program terminated with signal 6, Aborted. [New process 25893] #0 0xf7df8556 in raise () from /lib/libc.so.6 #0 0xf7df8556 in raise () from /lib/libc.so.6 No symbol table info available. #1 0xf7df9d78 in abort

Hi All, I also tried with 16ff395c156e and 3d576d682137 patches that touch lib-storage/notify and still 2.2.19 cores: Core was generated by `dovecot/imap'. Program terminated with signal 11, Segmentation fault. #0 0x0043bb8c in mailbox_list_notify_next (notify=0x0, rec_r=0xbfdb34a0) at mailbox-list-notify.c:28 28 return notify->list->v.notify_next(notify, rec_r); (gdb)

Running 2.2.15 on FreeBSD 10.0. Forcing replication with: doveadm replicator replicate -f user at host.com on one user that I've seen some syslogs show up to see what's going on. Other users are fine. When I run the above command on the one user it produces a core dump. See below for syslog output and full backtrace: syslog output: Oct 26 22:44:09 d3cstorage dovecot: dsync-server(user

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

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've still asserts while accessing virtual folders: Program terminated with signal 6, Aborted. [New process 6714] #0 0xf7e57556 in raise () from /lib/libc.so.6 #0 0xf7e57556 in raise () from /lib/libc.so.6 No symbol table info available. #1 0xf7e58d78 in abort () from /lib/libc.so.6 No symbol table info available. #2 0x080f2eb5 in default_fatal_finish (type=<value optimized