Since 2017 I don't get that error anymore. Please close the bug.
I confirm -- bug still happens very ocassionaly on version as below:
Exim version 4.84_2 #2 built 14-Jun-2017 14:38:31
Copyright (c) University of Cambridge, 1995 - 2014
(c) The Exim Maintainers and contributors in ACKNOWLEDGMENTS file, 2007
- 2014
Berkeley DB: Berkeley DB 5.3.28: (September
On Tue, May 31, 2016 at 09:46:55AM +0200, Marc Haber wrote:
Hi Marc,
> is this bug still present?
I cannot confirm at the moment as the box is unreachable
for me. But I did several updates in the past and so I am
pretty sure that I have exim with GNU-TLS active.
Feel free to close as fixed
Hi,
is this bug still present?
Greeetings
Marc
--
-
Marc Haber | "I don't trust Computers. They | Mailadresse im Header
Leimen, Germany| lose things."Winona Ryder | Fon: *49 6224 1600402
Nordisch by
On Tue, Jun 30, 2015 at 06:52:12PM +0200, Andreas Metzler wrote:
Hallo Andreas,
sorry for the late reply.
Hello,
are you running stable (jessie) or sid/testing?
Jessie
If you are running stable this might be
https://bugs.debian.org/788704 which I hope to be also fix in
jessie, see
On 2015-06-15 Christian Hilgers ch...@familie-hilgers.com wrote:
Hi Marc,
this is to sumup the past days of testing and collecting data.
From comparing with the other two Bug reporters, we found that we
all use a 32bit pae Kernel. Two of us run VIA CPUs:
[...]
#0 0xb69ec614 in
Hi Marc,
this is to sumup the past days of testing and collecting data.
From comparing with the other two Bug reporters, we found that we
all use a 32bit pae Kernel. Two of us run VIA CPUs:
from System 1 /proc/cpuinfo
processor : 0
vendor_id : CentaurHauls
cpu family : 6
On Mon, Jun 08, 2015 at 12:25:48PM +0200, Christian Hilgers wrote:
I will run memtest the next time I am onsite. But as only exim fails and it
started
after the upgrade I assume memtest will not show anything.
I have never seen a signal 11 in exim that was not caused by faulty
hardware. If
Package: exim4
Version: 4.84-8
Followup-For: Bug #741412
Dear Maintainer,
after upgrading from Wheezy to Jessie I see the behaviour described in this bug
happens on one box.
It shows up in dmesg
[51017.459665] exim4[10550]: segfault at eeec4996 ip b6ac4614 sp bfaea690 error
7 in
On Thu, Mar 13, 2014 at 09:30:53AM +0100, Marc Haber wrote:
tags #741412 unreproducible moreinfo
thanks
On Wed, Mar 12, 2014 at 10:43:14AM +0100, Leszek Dubiel wrote:
After upgradading debian to woody I started to get exim crashed for some
emails (a few emails for few thousand
tags #741412 unreproducible moreinfo
thanks
On Wed, Mar 12, 2014 at 10:43:14AM +0100, Leszek Dubiel wrote:
After upgradading debian to woody I started to get exim crashed for some
emails (a few emails for few thousand deliveries).
Woody has been out of support for, IIRC, ten years.
That
On Thu, Mar 13, 2014 at 10:02:32AM +0100, Leszek Dubiel wrote:
Strange thing is that it started to occur just after upgrading to
wheezey.
Other addresses, a different address model, code hardening, new
compiler. A truckload of possible reasons.
Anyway: if I am the only one with this problem,
Woody has been out of support for, IIRC, ten years.
Sorry! This is wheezy, debian version 7.4.
That being said, signal 11 errors usually indicate faulty hardware,
most probably bad RAM or a bad CPU. Please check with memtest or other
tools.
Strange thing is that it started to occur
Package: exim4
Version: 4.80-7
Severity: important
After upgradading debian to woody I started to get exim crashed for some
emails (a few emails for few thousand deliveries).
Email is delivered to exim, put into the queue, and never delivered.
Running the queue gives error message:
14 matches
Mail list logo
