I as well had (hopefully) the same problem.  I have not had any errors today and I 
re-compiled and re-install early this morning.  I would have had at least 10 dealth 
messages by 3:00pm, anyway, this is what I did.
 
1.  Created the following link  in /usr/lib/  libdb-3.so   ->  libdb-3.2.so.  On 
redhat, by default the link is no created, however I discovered (with the help of my 
C++ co-workers) that the compulation was looking for db-3 which normally references 
{lib}db-3{.so} which of cource was not there.
 
2.  Adjusted the default configure.in file in the cyrus-sasl-1.5.24 source.   I did 
this because everytime I re-compiled specificly requestion db3, the Makefile would 
show just db.  In the configure.in, look for the following within a case structure:
 
case "$dblib" in
gdbm)
      ....stuff
ndbm)
     ....stuff
berkeley)
     ...stuff,
     SASL_DB_LIB="-ldb"
*)
 
Change the "-ldb" to "-ldb-3"
 
Save the file, retar the source, rebuild the rpm and re-install.  This has been 
running like a top since early this morning! and again, I sould have had at-lease 10 
death errors by now considering the mail volume is higher that normal today.
 
Best of luck....
 
Vernon Fort
 
-----Original Message----- 
From: Dan de Haan [mailto:[EMAIL PROTECTED]] 
Sent: Mon 1/28/2002 4:58 PM 
To: [EMAIL PROTECTED] 
Cc: 
Subject: RE: Death by 11



        Yes.  Just to be sure, I tried recompiling sasl and cyrus again.  Still have
        the same problem.
        
                        -Dan
        
        > -----Original Message-----
        > From: Tarjei Huse [mailto:[EMAIL PROTECTED]]
        > Sent: January 28, 2002 11:19 AM
        > To: [EMAIL PROTECTED]
        > Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]
        > Subject: Re: Death by 11
        >
        >
        > Have you checked the death by 11 section of cyrus-utils.sf.net/faq?
        >
        > Tarjei
        > > Hello,
        > >
        > > I initially thought this was a permissions issue when I saw similar
        > > messages.
        > > I've about convinced myself that its not and am now thinking that it
        > > may be
        > > a library issue, ie can't find the one it wants. My problem is that
        > > when sendmail invokes deliver, deliver dies with the signal 11. Has
        > > anyone
        > > else seen this and if so did you get it fixed?
        > >
        > > Regards,
        > > Earl Shannon
        > > --
        > > Systems Programmer, Computing Services, Information Technology
        > > NC State University.
        > > http://www4.ncsu.edu/~ershanno
        > >
        > > Dan de Haan wrote:
        > >>
        > >> I have Cyrus 2.0.16 and postfix installed on a RedHat 7.2 system.
        > >> About 8-10 times a day, either lmptd or imap will die. 
        > Once a thread
        > >> dies, the server is unusable, and has to be restarted
        > before it will
        > >> accept any connections. The server currently has only a
        > dozen boxes on
        > >> it, and transfers about 600 mail per day.
        > >>
        > >> Up until last Thursday, this system was running Redhat 7.1
        > with Cyrus
        > >> 2.0.16 and didn't have any problems.  A hard disk failure is the
        > >> reason for the re-install.
        > >>
        > >> Any ideas on what could cause this?
        > >>
        > >> Jan 28 04:24:16 gateway master[16786]: about to exec
        > >> /usr/cyrus/bin/lmtpd Jan 28 04:24:16 gateway
        > service-lmtpunix[16786]:
        > >> executed
        > >> Jan 28 04:24:17 gateway master[15917]: process 16786
        > exited, signaled
        > >> to death by 11
        > >>
        > >> db3-devel-3.2.9-4
        > >> db3-3.2.9-4
        > >> db3-utils-3.2.9-4
        > >> postfix-20011210-1pcreSASL
        > >> openssl-0.9.6b-8
        > >> openssl-devel-0.9.6b-8
        > >> glibc-2.2.4-19.3
        > >>
        > >>                 -Dan de Haan
        >
        >
        > ____________________
        > Tarjei Huse
        > 920 63 413
        >
        >
        >
        >
        >
        

Reply via email to