Like I said in my message, I posted that well over a year ago...it was
caused by a bad temp file location hardcoded in the DB library.
----- Original Message -----
From: "Mark Bergsma" <mark@???>
To: "Sam Michaels" <sam@???>
Cc: <exim-users@???>
Sent: Monday, April 21, 2003 11:25 AM
Subject: Re: [Exim] signal 11 exit
> Sam Michaels wrote:
>
> > open("/var/spool/exim/db/retry", O_RDONLY) = 7
> > fcntl(7, F_SETFD, FD_CLOEXEC) = 0
> > fstat(7, {st_mode=S_IFREG|0640, st_size=20480, ...}) = 0
> > lseek(7, 0, SEEK_SET) = 0
> > read(7, "\0\0\0\0\0\0\0\0\0\0\0\0a\25\6\0\5\0\0\0\0\20\0\0\2\0\0"...,
4096)
> > = 4096
> > --- SIGSEGV (Segmentation fault) ---
> > +++ killed by SIGSEGV +++
> > ---snip---
> >
> > It's been attempting to deliver the messages since Feb 13th....I figured
the
> > retry times would have expired by now.
> >
> > Finally gave up and did an -Mrm on them. Any ideas what would cause
this?
>
> It looks like your retry database is corrupt. Please try removing all
> the files in /var/spool/exim/db - that won't cause loss of any important
> information.
>
> You might also want to check your DBM library setup.
>
> --
> Mark
>
> mark@???
>
>
