similar to: lmtp segfault after upgrade

On 2017-05-01 19:26, Aki Tuomi wrote: >> On May 1, 2017 at 8:21 PM Tom Sommer <mail at tomsommer.dk> wrote: >> >> >> I just upgraded our Director to 2.2.29.1 from 2.2.26, and now my dmesg >> and /var/log/messages are getting flooded by these errors: >> >> lmtp[45758]: segfault at 21 ip 00007fb412d3ad11 sp 00007ffe83ad2df0 >> error 4 in

> On May 1, 2017 at 8:26 PM Aki Tuomi <aki.tuomi at dovecot.fi> wrote: > > > > > On May 1, 2017 at 8:21 PM Tom Sommer <mail at tomsommer.dk> wrote: > > > > > > I just upgraded our Director to 2.2.29.1 from 2.2.26, and now my dmesg > > and /var/log/messages are getting flooded by these errors: > > > > lmtp[45758]: segfault at

On 2017-05-02 09:35, Aki Tuomi wrote: > On 2017-05-02 10:20, Tom Sommer wrote: >> On 2017-05-01 19:26, Aki Tuomi wrote: >>>> On May 1, 2017 at 8:21 PM Tom Sommer <mail at tomsommer.dk> wrote: >>>> >>>> >>>> I just upgraded our Director to 2.2.29.1 from 2.2.26, and now my >>>> dmesg >>>> and /var/log/messages

On 2017-05-02 10:20, Tom Sommer wrote: > On 2017-05-01 19:26, Aki Tuomi wrote: >>> On May 1, 2017 at 8:21 PM Tom Sommer <mail at tomsommer.dk> wrote: >>> >>> >>> I just upgraded our Director to 2.2.29.1 from 2.2.26, and now my dmesg >>> and /var/log/messages are getting flooded by these errors: >>> >>> lmtp[45758]: segfault at

lmtp on Director crash with 2.3.2.1 # gdb /usr/libexec/dovecot/lmtp /var/core/60174 GNU gdb (GDB) Red Hat Enterprise Linux (7.2-92.el6) Copyright (C) 2010 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

> On May 1, 2017 at 8:21 PM Tom Sommer <mail at tomsommer.dk> wrote: > > > I just upgraded our Director to 2.2.29.1 from 2.2.26, and now my dmesg > and /var/log/messages are getting flooded by these errors: > > lmtp[45758]: segfault at 21 ip 00007fb412d3ad11 sp 00007ffe83ad2df0 > error 4 in libdovecot.so.0.0.0[7fb412c95000+11c000] > > Any ideas? > >

On 2017-05-01 19:34, Aki Tuomi wrote: >> On May 1, 2017 at 8:26 PM Aki Tuomi <aki.tuomi at dovecot.fi> wrote: >> >> >> >> > On May 1, 2017 at 8:21 PM Tom Sommer <mail at tomsommer.dk> wrote: >> > >> > >> > I just upgraded our Director to 2.2.29.1 from 2.2.26, and now my dmesg >> > and /var/log/messages are getting

My director has started segfaulting since upgradeing to 2.3.2: # gdb /usr/libexec/dovecot/imap-login ./core.9757 GNU gdb (GDB) Red Hat Enterprise Linux (7.2-92.el6) Copyright (C) 2010 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

When in the process of testing out the 2.3.0 version of Dovecot, we noticed that on a busy server, imap-login can sometimes take 100% CPU and remain there indefinitely. We grabbed a gdb trace while it was happening: dovenull 36053 31.2 0.0 60460 17316 ? R 04:38 11:55 dovecot/imap-login root at server [~]# strace -p 36053 Process 36053 attached ^CProcess 36053 detached root at server

Hi, got the following with beta4 while uploading messages from a local mbox to the dovecot server in my LAN, tested with mutt and sylpheed, the same action works with 1.2.11: Mar 29 13:42:46 [dovecot] imap(juergen): Panic: stream doesn't support seeking backwards Mar 29 13:42:46 [dovecot] imap(juergen): Raw backtrace: /usr/lib/dovecot/libdovecot.so.0 [0xb76b7ec4] ->

Mar 19 16:54:37 lmtp(xxxx at xxx.xxx): Panic: file file-lock.c: line 269: unreached Mar 19 16:54:37 lmtp(xxxx at xxx.xxx): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0 [0x35f647e07a] -> /usr/lib/dovecot/libdovecot.so.0 [0x35f647e0e6] -> /usr/lib/dovecot/libdovecot.so.0 [0x35f647d4ac] -> /usr/lib/dovecot/libdovecot.so.0 [0x35f6481edf] ->

On 18.05.2017 10:55, Tom Sommer wrote: > On 2017-05-18 09:36, Teemu Huovila wrote: >> Hello Tom >> >> On 02.05.2017 11:19, Timo Sirainen wrote: >>> On 2 May 2017, at 10.41, Tom Sommer <mail at tomsommer.dk> wrote: >>>> >>>> (gdb) bt full >>>> #0 i_stream_seek (stream=0x21, v_offset=0) at istream.c:298 >>>>

Hey, I'm getting "Error in MANAGESIEVE command received by server." and service(managesieve-login) killed with signal 11 (core dumped) when doing two line autenticate(sogo) to managesieve(). # telnet localhost 4190 Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. "IMPLEMENTATION" "Dovecot Pigeonhole" "SIEVE"

Hello, I have a new director ring I am setting up on centos 7 with dovecot 2.3.1. I haven't been able to replecate this in testing, but as soon as I start pushing production traffic to the new ring I see dozens of these in the logs: Apr 18 00:34:00 d.director.imapd.sonic.net kernel: imap-login[163107]: segfault at 10 ip 00007ff625698dd5sp 00007ffe4b77bb28 error 4 in

I see this in my logs after 2.3.3: using zlib plugin, ofc. Oct 02 10:01:39 imap(user at example.com)<50643></2k4Sjp3vMqC496W>: Panic: file ostream-zlib.c: line 37 (o_stream_zlib_close): assertion failed: (zstream->ostream.finished || zstream->ostream.ostream.stream_errno != 0 || zstream->ostream.error_handling_disabled) Oct 02 10:01:39 imap(user at

Hello Tom On 02.05.2017 11:19, Timo Sirainen wrote: > On 2 May 2017, at 10.41, Tom Sommer <mail at tomsommer.dk> wrote: >> >> (gdb) bt full >> #0 i_stream_seek (stream=0x21, v_offset=0) at istream.c:298 >> _stream = <value optimized out> >> #1 0x00007fe98391ff32 in i_stream_concat_read_next (stream=0x1efe6c0) at istream-concat.c:77 >>

Hi Timo With dovecot built from the latest 2.2.9 hg (342f6962390e) we get imap crashes. This only affects one account which is used by multiple clients. The first few logins seem to work ok, but after a few seconds the log is flooded with Dec 5 13:43:10 team dovecot: imap-login: Login: user=<sales at example.com>, method=PLAIN, rip=1.2.3.4, lip=5.6.7.8, mpid=27923, TLS,

Le 13/02/2015 16:19, Casey Stone a ?crit : > On Feb 5, 2015, at 10:39 PM, Casey Stone <tcstone at caseystone.com> wrote: > >> Hello: >> >> I've been looking forward to getting my mail server up to Dovecot 2.2+ to be able to use the sync mechanism. I run my own mail server just for myself, with a few different accounts, and want to keep a master and backup server

Hi, I have already mentioned this in http://www.dovecot.org/pipermail/dovecot/2014-November/098592.html I could reproduce the errors above in a self-compiled v2.2.18 and the prebuilt packages from xi.rename-it.nl (in addition to version 2.2.15 mentioned in the link) The problem occurs when enabling fts_tika in the plugins (tried tika 1.6, 1.7 and 1.8). I tried to move a folder of my mailbox

doveadm search -u dmiller at amfes.com text xyzxyz doveadm(dmiller at amfes.com): Panic: file istream-limit.c: line 79 (i_stream_limit_seek): assertion failed: (v_offset <= lstream->v_size) doveadm(dmiller at amfes.com): Error: Raw backtrace: /usr/local/lib/dovecot/libdovecot.so.0(+0x3ca8a) [0x7fcf3daaca8a] -> /usr/local/lib/dovecot/libdovecot.so.0(default_fatal_handler+0x32)