> -----Original Message----- > From: Rejaine Monteiro [mailto:[EMAIL PROTECTED] > Sent: maandag 27 november 2006 12:03 > To: Jeff Funk > Cc: users@spamassassin.apache.org > Subject: Re: spamd crashing... > > > What you use to monitor and restarts spamd when failed? > I'm have some crashes too, so I'm using monit to do this. > My problems are : spamd daemon stop works or tcp port > 783 is not responding.
Spamd crashing is, seen from the program itself, rather unlikely. A child crashing? Maybe; but the parent? Sound more like your perl itself is unstable (core-dumping and such; any such indication in your system logs). I recently saw this posted: > ... @INC (@INC contains: > /usr/lib/perl5/site_perl/5.8.8/i386-linux-thread-multi > /usr/lib/perl5/site_perl/5.8.8 > /usr/lib/perl5/site_perl/5.8.7/i386-linux-thread-multi > /usr/lib/perl5/site_perl/5.8.6/i386-linux-thread-multi > /usr/lib/perl5/site_perl/5.8.5/i386-linux-thread-multi > /usr/lib/perl5/site_perl/5.8.4/i386-linux-thread-multi > /usr/lib/perl5/site_perl/5.8.3/i386-linux-thread-multi Never understood why Linux does this anyway (I'm on FreeBSD). Probably because someone thought it might be a cool idea to include stuff from an older installation in the INC path. Never mind that xs stuff compiled for a previous version can seriously instablize your system. At any rate, I would start looking in this direction first. My spamd, the old 2.54 I used for ages, and the new 3.0.17, has never ever crashed; and I mean it. The only real reason I think the parent process could potentially crash (not on signal 11) is because the main "accept" loop might not have an eval around it or some such. But I'm pretty sure they took care of that. - Mark
