On 2007-03-01 Ronny Adsetts <[EMAIL PROTECTED]> wrote:
[...]
> I'll probably try the backports packages outside of office hours later
> today so that I can confirm if the crash is still there in later packages.
> Assuming the server causing the problems continues to connect anyway.
I have put un
Andreas Metzler said at 03/03/2007 09:41:
>
> I have put unstripped packages on http://www.bebt.de/debian/misc/
> (exim4-daemon-light_4.50-8sarge2+b0_i386.deb and
> exim4-daemon-light_4.50-8sarge2+b0_i386.deb). If you'd rather not
> install binaries from untrusted sources, that is no problem:
>
>
user [EMAIL PROTECTED]
usertags #412886 revisit-20060430
thanks
On Mon, Mar 05, 2007 at 11:40:37AM +, Ronny Adsetts wrote:
> Thanks for this. Unfortunately, I'm no longer seeing the server
> crashing as the server on the other end stopped trying to re-deliver
> the email on Friday. I'll see wh
Marc Haber said at 19/03/2007 11:15:
> On Mon, Mar 05, 2007 at 11:40:37AM +, Ronny Adsetts wrote:
>> Thanks for this. Unfortunately, I'm no longer seeing the server
>> crashing as the server on the other end stopped trying to re-deliver
>> the email on Friday. I'll see what I can do to get the
Marc Haber said at 19/03/2007 11:15:
> On Mon, Mar 05, 2007 at 11:40:37AM +, Ronny Adsetts wrote:
>> Thanks for this. Unfortunately, I'm no longer seeing the server
>> crashing as the server on the other end stopped trying to re-deliver
>> the email on Friday. I'll see what I can do to get the
Marc Haber said at 19/03/2007 11:15:
>
> On Mon, Mar 05, 2007 at 11:40:37AM +, Ronny Adsetts wrote:
>> Thanks for this. Unfortunately, I'm no longer seeing the server
>> crashing as the server on the other end stopped trying to re-deliver
>> the email on Friday. I'll see what I can do to get t
On Thu, Mar 22, 2007 at 11:14:10AM +, Ronny Adsetts wrote:
> Marc Haber said at 19/03/2007 11:15:
> > On Mon, Mar 05, 2007 at 11:40:37AM +, Ronny Adsetts wrote:
> >> Thanks for this. Unfortunately, I'm no longer seeing the server
> >> crashing as the server on the other end stopped trying t
Package: exim4
Version: 4.50-8sarge2
Severity: normal
I've recently, as of early this morning, started to see segfaults from
exim4. I'm seeing this in kern.log:
Feb 28 03:07:02 nakor kernel: exim4[4242]: segfault at
rip 002a96bbb220 rsp 007fbfffed58 error 4
Feb 28 03:07:
On 2007-02-28 Ronny Adsetts <[EMAIL PROTECTED]> wrote:
> Package: exim4
> Version: 4.50-8sarge2
> Severity: normal
> I've recently, as of early this morning, started to see segfaults from
> exim4. I'm seeing this in kern.log:
> Feb 28 03:07:02 nakor kernel: exim4[4242]: segfault at 0
Andreas Metzler said at 28/02/2007 19:37:
On 2007-02-28 Ronny Adsetts <[EMAIL PROTECTED]> wrote:
Package: exim4
Version: 4.50-8sarge2
Severity: normal
I've recently, as of early this morning, started to see segfaults from
exim4. I'm seeing this in kern.log:
Feb 28 03:07:02 nakor kernel: ex
On Wed, Feb 28, 2007 at 07:43:16PM +, Ronny Adsetts wrote:
> My first thought was hardware failure too, but it's not looking that way at
> the moment. The segfaults are too regular in their timing. I'll see if the
> same happens at 20:08.
What does your exim log say in the respective time fr
Marc Haber said at 01/03/2007 09:13:
On Wed, Feb 28, 2007 at 07:43:16PM +, Ronny Adsetts wrote:
My first thought was hardware failure too, but it's not looking that way at
the moment. The segfaults are too regular in their timing. I'll see if the
same happens at 20:08.
What does your ex
On Thu, Mar 01, 2007 at 09:50:40AM +, Ronny Adsetts wrote:
> I'm not seeing any problems on this server at all other than this segfault
> that started yesterday at ~3am and continues every hour when the same email
> is retried.
So the segfault is associated with a single message?
Please sen
Marc Haber said at 01/03/2007 09:54:
On Thu, Mar 01, 2007 at 09:50:40AM +, Ronny Adsetts wrote:
I'm not seeing any problems on this server at all other than this segfault
that started yesterday at ~3am and continues every hour when the same email
is retried.
So the segfault is associated
On Thu, Mar 01, 2007 at 09:50:40AM +, Ronny Adsetts wrote:
> Marc Haber said at 01/03/2007 09:13:
> >On Wed, Feb 28, 2007 at 07:43:16PM +, Ronny Adsetts wrote:
> >>
> >>My first thought was hardware failure too, but it's not looking that way
> >>at the moment. The segfaults are too regular
Marc Haber said at 01/03/2007 10:08:
On Thu, Mar 01, 2007 at 09:50:40AM +, Ronny Adsetts wrote:
Marc Haber said at 01/03/2007 09:13:
On Wed, Feb 28, 2007 at 07:43:16PM +, Ronny Adsetts wrote:
My first thought was hardware failure too, but it's not looking that way
at the moment. The se
On Thu, Mar 01, 2007 at 11:20:46AM +, Ronny Adsetts wrote:
> Strace for the crashing process attached.
Thanks. This unfortunately is not very conclusive.
Again, unfortunately, exim4 in sarge does not yet have a -dbg package.
Can you rebuild the exim packages locally, run an unstripped exim a
Marc Haber said at 01/03/2007 11:30:
On Thu, Mar 01, 2007 at 11:20:46AM +, Ronny Adsetts wrote:
Strace for the crashing process attached.
Thanks. This unfortunately is not very conclusive.
Again, unfortunately, exim4 in sarge does not yet have a -dbg package.
Can you rebuild the exim pac
Marc Haber said at 26/03/2007 21:58:
>
> Asking on exim-user yielded a pointer to core(5), which in turn
> pointed me to proc(5). Additionally, Jakob suggeested setting
> /proc/sys/fs/suid_dumpable to 1 or (safer) 2? to allow exim as a suid
> binary to dump core.
>
> The core file is going to be
On Wed, Mar 28, 2007 at 07:00:43PM +0100, Ronny Adsetts wrote:
> Marc Haber said at 26/03/2007 21:58:
> > Asking on exim-user yielded a pointer to core(5), which in turn
> > pointed me to proc(5). Additionally, Jakob suggeested setting
> > /proc/sys/fs/suid_dumpable to 1 or (safer) 2? to allow exim
Marc Haber said at 03/04/2007 12:13:
> On Wed, Mar 28, 2007 at 07:00:43PM +0100, Ronny Adsetts wrote:
[...]
>>
>> Do you have any pointers on getting exim4 to dump core without a
>> kernel upgrade? I can do it as a last resort with a backports.org
>> kernel if needed but would prefer to avoid this.
21 matches
Mail list logo