Try to look at google, but didnt find anything.
Since last wednesday, when I updated my server to debian lenny, I receive every 15 minutes or so segfaults from lenny:
From my syslog:
From my mainlog:
I discovered 1 email in my mailqueue that at least triggers it:
(Removed emailaddress in TO) headers:
I dont see anything special on this. Does anyone have a idea what the solution can be? Untill now it looks like it only happens on spam, but maybe it also will happen on normal mail later.
Thanks.
Since last wednesday, when I updated my server to debian lenny, I receive every 15 minutes or so segfaults from lenny:
From my syslog:
Code:
Feb 27 22:40:21 sandy kernel: [196165.062101] exim[23542]: segfault at 1820160a ip 1820160a sp bfa7c09c error 4
Feb 27 22:40:21 sandy kernel: [196165.062101] exim[23543]: segfault at 1820160a ip 1820160a sp bfa7c0a0 error 4
Feb 27 22:40:21 sandy kernel: [196165.062101] exim[23544]: segfault at 1820160a ip 1820160a sp bfa7c09c error 4
Feb 27 22:40:21 sandy kernel: [196165.062340] exim[23545]: segfault at 1820160a ip 1820160a sp bfa7c0a0 error 4
Feb 27 22:40:21 sandy kernel: [196165.066100] exim[23546]: segfault at 1820160a ip 1820160a sp bfa7c09c error 4
Feb 27 22:40:21 sandy kernel: [196165.066100] exim[23547]: segfault at 1820160a ip 1820160a sp bfa7c0a0 error 4
Feb 27 22:40:21 sandy kernel: [196165.066100] exim[23548]: segfault at 1820160a ip 1820160a sp bfa7c0a0 error 4
Feb 27 22:40:21 sandy kernel: [196165.066100] exim[23549]: segfault at 1820160a ip 1820160a sp bfa7c0a0 error 4
Feb 27 22:40:21 sandy kernel: [196165.070292] exim[23550]: segfault at 1820160a ip 1820160a sp bfa7c09c error 4
Feb 27 22:40:21 sandy kernel: [196165.071187] exim[23551]: segfault at 1820160a ip 1820160a sp bfa7c09c error 4
Code:
2009-02-27 22:40:21 queue run: process 23542 crashed with signal 11 while delivering 1Ld5sg-0005L6-Iz
2009-02-27 22:40:21 queue run: process 23543 crashed with signal 11 while delivering 1Ld6x0-0007UF-74
2009-02-27 22:40:21 queue run: process 23544 crashed with signal 11 while delivering 1LchvU-0000tN-Q5
2009-02-27 22:40:21 queue run: process 23545 crashed with signal 11 while delivering 1LcjkG-0004N1-Pt
2009-02-27 22:40:21 queue run: process 23546 crashed with signal 11 while delivering 1LchwC-0000ui-T2
2009-02-27 22:40:21 queue run: process 23547 crashed with signal 11 while delivering 1Ld3RV-0000Z3-4o
2009-02-27 22:40:21 queue run: process 23548 crashed with signal 11 while delivering 1LcmQ0-0001BL-6S
2009-02-27 22:40:21 queue run: process 23549 crashed with signal 11 while delivering 1LcvxM-0003QR-LY
2009-02-27 22:40:21 queue run: process 23550 crashed with signal 11 while delivering 1Ld9SL-00046L-93
2009-02-27 22:40:21 queue run: process 23551 crashed with signal 11 while delivering 1LclQB-0007cF-An
2009-02-27 22:40:21 queue run: process 23552 crashed with signal 11 while delivering 1LcxcV-0006Lk-Ru
2009-02-27 22:40:21 queue run: process 23553 crashed with signal 11 while delivering 1Ld78X-0007qX-LC
2009-02-27 22:40:21 queue run: process 23554 crashed with signal 11 while delivering 1Lcky6-0006jM-7D
2009-02-27 22:40:21 queue run: process 23555 crashed with signal 11 while delivering 1LcnPq-00039U-0I
2009-02-27 22:40:21 queue run: process 23556 crashed with signal 11 while delivering 1Ld3T2-0000aM-50
2009-02-27 22:40:21 queue run: process 23557 crashed with signal 11 while delivering 1Lci9n-0001Ks-W4
2009-02-27 22:40:21 queue run: process 23558 crashed with signal 11 while delivering 1Lcqa9-0002Ir-B0
2009-02-27 22:40:21 queue run: process 23559 crashed with signal 11 while delivering 1Ld1Ed-0004cV-H4
2009-02-27 22:40:21 queue run: process 23560 crashed with signal 11 while delivering 1Lci9p-0001Kt-O8
2009-02-27 22:40:21 queue run: process 23561 crashed with signal 11 while delivering 1LclUt-0007la-Fs
2009-02-27 22:40:21 queue run: process 23562 crashed with signal 11 while delivering 1LcodC-0005W9-5h
2009-02-27 22:40:21 queue run: process 23563 crashed with signal 11 while delivering 1Lcx3K-0005Lv-Ec
2009-02-27 22:40:21 queue run: process 23564 crashed with signal 11 while delivering 1LcnHA-0002r8-KG
2009-02-27 22:40:21 queue run: process 23565 crashed with signal 11 while delivering 1Lcmqq-00020K-TH
2009-02-27 22:40:21 queue run: process 23566 crashed with signal 11 while delivering 1LcoEq-0004kw-M0
2009-02-27 22:40:21 queue run: process 23567 crashed with signal 11 while delivering 1Lcm3F-0000QP-RO
2009-02-27 22:40:21 queue run: process 23568 crashed with signal 11 while delivering 1Lcy5x-0007Bm-GV
2009-02-27 22:40:21 queue run: process 23569 crashed with signal 11 while delivering 1Ld4LR-0002JZ-Ru
2009-02-27 22:40:21 queue run: process 23570 crashed with signal 11 while delivering 1Ld29u-0006PZ-OC
2009-02-27 22:40:21 queue run: process 23571 crashed with signal 11 while delivering 1LcnGm-0002qV-KI
2009-02-27 22:40:21 queue run: process 23573 crashed with signal 11 while delivering 1Lci9d-0001Kq-Os
2009-02-27 22:40:21 queue run: process 23574 crashed with signal 11 while delivering 1LcxJv-0005mQ-Ds
2009-02-27 22:40:21 queue run: process 23575 crashed with signal 11 while delivering 1Lcxxd-0006xg-DH
2009-02-27 22:40:21 queue run: process 23576 crashed with signal 11 while delivering 1Lcspc-0006Nb-Rg
2009-02-27 22:40:21 queue run: process 23577 crashed with signal 11 while delivering 1Lcfvg-0005Vi-Lp
2009-02-27 22:40:21 queue run: process 23578 crashed with signal 11 while delivering 1Ld5DA-00042Y-38
2009-02-27 22:40:21 queue run: process 23579 crashed with signal 11 while delivering 1LcizD-0002ww-BZ
2009-02-27 22:40:21 queue run: process 23580 crashed with signal 11 while delivering 1Ld0Lk-0002wK-M2
2009-02-27 22:40:21 queue run: process 23581 crashed with signal 11 while delivering 1Ld9lP-0004ji-AJ
2009-02-27 22:40:21 queue run: process 23582 crashed with signal 11 while delivering 1Ld4jL-000368-GV
2009-02-27 22:40:21 queue run: process 23583 crashed with signal 11 while delivering 1LcyA6-0007Jd-JK
2009-02-27 22:40:21 queue run: process 23584 crashed with signal 11 while delivering 1LcxYe-0006E5-NC
2009-02-27 22:40:21 queue run: process 23585 crashed with signal 11 while delivering 1LciGs-0001Y1-31
2009-02-27 22:40:21 queue run: process 23586 crashed with signal 11 while delivering 1Lck28-0004wH-E1
2009-02-27 22:40:21 queue run: process 23587 crashed with signal 11 while delivering 1Ld4WB-0002ht-4Z
2009-02-27 22:40:21 queue run: process 23588 crashed with signal 11 while delivering 1Ld19R-0004TN-W8
2009-02-27 22:40:21 queue run: process 23589 crashed with signal 11 while delivering 1Ld2aB-0007KZ-QA
2009-02-27 22:40:21 queue run: process 23590 crashed with signal 11 while delivering 1Ld4Y2-0002k9-U3
2009-02-27 22:40:21 queue run: process 23591 crashed with signal 11 while delivering 1Lcywh-0000NI-ME
2009-02-27 22:40:21 queue run: process 23592 crashed with signal 11 while delivering 1LcmAE-0000eJ-Er
2009-02-27 22:40:21 queue run: process 23593 crashed with signal 11 while delivering 1LcmhK-0001gz-30
2009-02-27 22:40:21 queue run: process 23595 crashed with signal 11 while delivering 1LchPq-0008MA-Ai
2009-02-27 22:40:21 queue run: process 23596 crashed with signal 11 while delivering 1Lcmy1-0002Ed-6n
2009-02-27 22:40:21 queue run: process 23597 crashed with signal 11 while delivering 1Lcx1T-0005JA-2O
I discovered 1 email in my mailqueue that at least triggers it:
(Removed emailaddress in TO) headers:
Code:
1Ld6x0-0007UF-74-H
mail 8 8
<[email protected]>
1235757402 0
-helo_name 20158181037.user.veloxzone.com.br
-host_address 201.58.181.37.4102
-host_name 20158181037.user.veloxzone.com.br
-interface_address 89.18.168.236.25
-received_protocol esmtp
-body_linecount 3
-max_received_linelength 137
-deliver_firsttime
XX
1
[email protected]
241P Received: from 20158181037.user.veloxzone.com.br ([201.58.181.37])
by sandy.hosthuis.nl with esmtp (Exim 4.69)
(envelope-from <[email protected]>)
id 1Ld6x0-0007UF-74
for [email protected]; Fri, 27 Feb 2009 18:56:43 +0100
038 Date: Fri, 27 Feb 2009 14:56:42 -0300
045F From: =?koi8-r?B?9MHSzc8=?= <[email protected]>
031* Return-Path: <[email protected]>
023 X-Priority: 3 (Normal)
057I Message-ID: <[email protected]>
027T To: [email protected]
076 In-Reply-To: <[email protected]>
138 References: <[email protected]> <[email protected]>
059 Subject: =?koi8-r?B?1MXCxSDF3cUgztXWzs8gzc+jINfJxMXPPw==?=
018 MIME-Version: 1.0
041 Content-Type: text/plain; charset=koi8-r
032 Content-Transfer-Encoding: 8bit
I dont see anything special on this. Does anyone have a idea what the solution can be? Untill now it looks like it only happens on spam, but maybe it also will happen on normal mail later.
Thanks.