Hello,
after upgrade (Debian wheezy) from dovecot 2:2.2.13-1~auto+103 => 2:2.2.13-1~auto+113 I discovered that in my log and all mails stuck in the Queue. I’ve had downgrade v 2:2.2.13-1~auto+103 an everything is fine. What’s wrong? Any ideas or solution greatly appreciated. Thanks.
Jul 25 11:03:01 server2 dovecot: lmtp(25638): Fatal: master: service(lmtp): child 25638 killed with signal 11 (core dumps disabled) Jul 25 11:03:01 server2 dovecot: lmtp(25639): Connect from local Jul 25 11:03:01 server2 dovecot: lmtp(25639): Fatal: master: service(lmtp): child 25639 killed with signal 11 (core dumps disabled) Jul 25 11:03:01 server2 postfix/lmtp[25617]: 20773D10003: to=<web7p1@server1.art-domains.de>, orig_to=<jk@jkart.de>, relay=server1.art-domains.de[private/dovecot-lmtp], delay=0.05, delays=0.03/ 0/0.01/0.02, dsn=4.4.2, status=deferred (lost connection with server1.art-domains.de[private/dovecot-lmtp] while sending end of data -- message may be sent more than once) Jul 25 11:03:01 server2 amavis[25541]: (25541-01) Passed CLEAN {RelayedInbound}, [213.203.238.6]:53401 [193.175.143.182] <postfixbuch-users-bounces@listen.jpberlin.de> -> <jk@jkart.de>, Queue-I D: 62B8BD10001, Message-ID: <53D21B91.2070109@fh-landshut.de>, mail_id: AE71HPGl9ZR5, Hits: -5, size: 13518, queued_as: 20773D10003, 2771 ms Jul 25 11:03:01 server2 amavis[25541]: (25541-01) Passed CLEAN, <postfixbuch-users-bounces@listen.jpberlin.de> -> <jk@jkart.de>, Hits: -5, tag=-9999.9, tag2=2.5, kill=3, queued_as: 20773D10003, L/Y/0/0 Jul 25 11:03:01 server2 postfix/lmtp[25607]: 62B8BD10001: to=<jk@jkart.de>, relay=127.0.0.1[127.0.0.1]:10024, delay=3.9, delays=1.2/0/0.01/2.8, dsn=2.0.0, status=sent (250 2.0.0 from MTA(smtp:[ 127.0.0.1]:10025): 250 2.0.0 Ok: queued as 20773D10003) Jul 25 11:03:01 server2 postfix/qmgr[25508]: 62B8BD10001: removed Jul 25 11:03:02 server2 postfix/lmtp[25615]: 20773D10003: to=<web1p9@server1.art-domains.de>, orig_to=<admin@art-domains.de>, relay=server1.art-domains.de[private/dovecot-lmtp], delay=0.06, del ays=0.03/0/0.03/0.01, dsn=4.4.2, status=deferred (lost connection with server1.art-domains.de[private/dovecot-lmtp] while sending end of data -- message may be sent more than once) Jul 25 11:03:02 server2 dovecot: lmtp(25653): Connect from local Jul 25 11:03:02 server2 dovecot: lmtp(25653): Fatal: master: service(lmtp): child 25653 killed with signal 11 (core dumps disabled)
-- Mit freundlichen Grüßen, with kind regards, Jim Knuth
Die Freiheit der Rede hat den Nachteil, daß immer wieder Dummes, Häßliches und Bösartiges gesagt wird. Wenn wir aber alles in allem nehmen, sind wir doch eher bereit, uns damit abzufinden, als sie abzuschaffen. [Churchill]
Am 25.07.2014 11:23, schrieb Jim Knuth:
after upgrade (Debian wheezy) from dovecot 2:2.2.13-1~auto+103 => 2:2.2.13-1~auto+113 I discovered that in my log and all mails stuck in the Queue. I’ve had downgrade v 2:2.2.13-1~auto+103 an everything is fine What’s wrong?
the Debian package
Any ideas or solution greatly appreciated. Thanks.
downgrade
Jul 25 11:03:01 server2 dovecot: lmtp(25638): Fatal: master: service(lmtp): child 25638 killed with signal 11 (core dumps disabled) Jul 25 11:03:01 server2 dovecot: lmtp(25639): Connect from local Jul 25 11:03:01 server2 dovecot: lmtp(25639): Fatal: master: service(lmtp): child 25639 killed with signal 11 (core dumps disabled)
http://unixhelp.ed.ac.uk/CGI/man-cgi?signal+7 SIGSEGV 11 Core Invalid memory reference
am 25.07.14 11:38 schrieb Reindl Harald <h.reindl@thelounge.net>:
Am 25.07.2014 11:23, schrieb Jim Knuth:
after upgrade (Debian wheezy) from dovecot 2:2.2.13-1~auto+103 => 2:2.2.13-1~auto+113 I discovered that in my log and all mails stuck in the Queue. I’ve had downgrade v 2:2.2.13-1~auto+103 an everything is fine What’s wrong?
the Debian package
thanks, but that is from
deb http://xi.rename-it.nl/debian/ stable-auto/dovecot-2.2 main
Any ideas or solution greatly appreciated. Thanks.
downgrade
Jul 25 11:03:01 server2 dovecot: lmtp(25638): Fatal: master: service(lmtp): child 25638 killed with signal 11 (core dumps disabled) Jul 25 11:03:01 server2 dovecot: lmtp(25639): Connect from local Jul 25 11:03:01 server2 dovecot: lmtp(25639): Fatal: master: service(lmtp): child 25639 killed with signal 11 (core dumps disabled)
http://unixhelp.ed.ac.uk/CGI/man-cgi?signal+7 SIGSEGV 11 Core Invalid memory reference
-- Mit freundlichen Grüßen, with kind regards, Jim Knuth
Better to reign in hell, than to serve in heaven! (John Milton)
Am 25.07.2014 11:49, schrieb Jim Knuth:
am 25.07.14 11:38 schrieb Reindl Harald <h.reindl@thelounge.net>:
Am 25.07.2014 11:23, schrieb Jim Knuth:
after upgrade (Debian wheezy) from dovecot 2:2.2.13-1~auto+103 => 2:2.2.13-1~auto+113 I discovered that in my log and all mails stuck in the Queue. I’ve had downgrade v 2:2.2.13-1~auto+103 an everything is fine What’s wrong?
the Debian package
thanks, but that is from deb http://xi.rename-it.nl/debian/ stable-auto/dovecot-2.2 main
how does it matter from where it is?
so what - you updated, the new version leads in SEGFAULTS so that binary is at least on your machine broken and unstable
the answer to "what's wrong" remains: that package
Any ideas or solution greatly appreciated. Thanks.
downgrade
Jul 25 11:03:01 server2 dovecot: lmtp(25638): Fatal: master: service(lmtp): child 25638 killed with signal 11 (core dumps disabled) Jul 25 11:03:01 server2 dovecot: lmtp(25639): Connect from local Jul 25 11:03:01 server2 dovecot: lmtp(25639): Fatal: master: service(lmtp): child 25639 killed with signal 11 (core dumps disabled)
http://unixhelp.ed.ac.uk/CGI/man-cgi?signal+7 SIGSEGV 11 Core Invalid memory reference
am 25.07.14 12:14 schrieb Reindl Harald <h.reindl@thelounge.net>:
Am 25.07.2014 11:49, schrieb Jim Knuth:
am 25.07.14 11:38 schrieb Reindl Harald <h.reindl@thelounge.net>:
Am 25.07.2014 11:23, schrieb Jim Knuth:
after upgrade (Debian wheezy) from dovecot 2:2.2.13-1~auto+103 => 2:2.2.13-1~auto+113 I discovered that in my log and all mails stuck in the Queue. I’ve had downgrade v 2:2.2.13-1~auto+103 an everything is fine What’s wrong?
the Debian package
thanks, but that is from deb http://xi.rename-it.nl/debian/ stable-auto/dovecot-2.2 main
how does it matter from where it is?
so what - you updated, the new version leads in SEGFAULTS so that binary is at least on your machine broken and unstable
the answer to "what's wrong" remains: that package
yes, I know. ;) But my question goes also to the Maintainer.
Any ideas or solution greatly appreciated. Thanks.
downgrade
Jul 25 11:03:01 server2 dovecot: lmtp(25638): Fatal: master: service(lmtp): child 25638 killed with signal 11 (core dumps disabled) Jul 25 11:03:01 server2 dovecot: lmtp(25639): Connect from local Jul 25 11:03:01 server2 dovecot: lmtp(25639): Fatal: master: service(lmtp): child 25639 killed with signal 11 (core dumps disabled)
http://unixhelp.ed.ac.uk/CGI/man-cgi?signal+7 SIGSEGV 11 Core Invalid memory reference
-- Mit freundlichen Grüßen, with kind regards, Jim Knuth
“Jesus wurde gekreuzigt, weil er bemerkt wurde. Deswegen verschwinde ich häufig von der Bildfläche.” Bob Dylan
Hi Jim,
Jim Knuth wrote:
Jul 25 11:03:01 server2 dovecot: lmtp(25638): Fatal: master: service(lmtp): child 25638 killed with signal 11 (core dumps disabled)
You should try to get a core dump and a gdb backtrace with debug symbols package installed.
The following article describes how to get one: http://www.dovecot.org/bugreport.html
Regards Daniel
participants (3)
-
Daniel Parthey
-
Jim Knuth
-
Reindl Harald