Hi,
Ok, update 2:
I proved that my system had the perl but (via a test script) as
previously mentioned. Ive therefore downgraded perl to perl 5.8.9. I
still have the same problem with SpamAssassin perl processes crashing.
I´ve take some more logs from spamd with debugging enabled, this is
Hi all,
ok I did some furhter work and when testing (sa-learn --sync) the
bayes db integrity its not good. So basically the problem was caused
by a corrupt bayes DB.
Thanks Andy.
Quoting a.sm...@ukgrid.net:
Hi,
I have a problem on one server that I see several times an hour
this problem logged by spamd
Wed May 5 10:04:43 2010 [88823] info: spamd: handled cleanup of child
pid [90622] due to SIGCHLD: DIED, signal 11 (000b)
And in the main messages file a corresponding error regarding the
Hi,
An update it looks like the problem may well be this Perl bug
that affects Perl 5.10.1 in the FreeBSD ports tree...
http://rt.perl.org/rt3//Public/Bug/Display.html?id=69973
thanks Andy.
I am starting spamd (/usr/local/etc/rc.d/sa-spamd start or spamd -d -
r /var/run/spamd.pid -c -s /var/log/spamd) and then a few seconds
later it is dying without an error.
all I get in /var/log/spamd is:
--
A ship should not ride on a single anchor,
nor life on a single hope
I am starting spamd (/usr/local/etc/rc.d/sa-spamd start or spamd -d -
r /var/run/spamd.pid -c -s /var/log/spamd) and then a few seconds
later it is dying without an error.
[Never mind, spamassassin --lint was dying with a core dump. I removed
the spear-fishing rules and all is back right
On Thursday 13 August 2009 14:13:33 LuKreme wrote:
I am starting spamd (/usr/local/etc/rc.d/sa-spamd start or spamd -d -
r /var/run/spamd.pid -c -s /var/log/spamd) and then a few seconds
later it is dying without an error.
[Never mind, spamassassin --lint was dying with a core dump. I removed
On 13-Aug-2009, at 06:43, Mark Martinec wrote:
On Thursday 13 August 2009 14:13:33 LuKreme wrote:
I am starting spamd (/usr/local/etc/rc.d/sa-spamd start or spamd -d -
r /var/run/spamd.pid -c -s /var/log/spamd) and then a few seconds
later it is dying without an error.
[Never mind,
LuKreme,
I'm considering 3.3, and am currently trying to overcome my aversion
to things labeled 'alpha'.
Understood. It is mainly labeled as alpha because some new things are
not finished (like the new bayesbdb backend to Bayes), and it would
be nice to close some stale problem reports (almost
Spamd times out/ dies and I get the following in the maillog...
[EMAIL PROTECTED]:/var/log# egrep -v
connection|checking|identified|result|salearn|clean|imap|spawned|internal
error maillog /home/ronan/spamd
[EMAIL PROTECTED]:/var/log# cat /home/ronan/spamd
Oct 27 00:08:21 dung
On Tue, Sep 28, 2004 at 11:56:52AM -0700, Justin Mason wrote:
Will Yardley writes:
On Fri, Sep 24, 2004 at 10:22:01AM -0700, Justin Mason wrote:
Will Yardley writes:
Has anyone else seen a problem w/ spamd dying sometimes (after
working for a while)? I have been seeing
Oh - also, sorry for the self-followup...
normal ps output:
root 8978 1 0 17:55 ?00:00:00 /usr/bin/perl -T -w
/usr/local/bin/spamd -d -D
root 8979 8978 0 17:55 ?00:00:00 spamd child
root 8980 8978 0 17:55 ?00:00:00 spamd child
root 8981 8978
Oh - also, sorry for the self-followup...
normal ps output:
root 8978 1 0 17:55 ?00:00:00 /usr/bin/perl
-T -w /usr/local/bin/spamd -d -D
root 8979 8978 0 17:55 ?00:00:00 spamd child
root 8980 8978 0 17:55 ?00:00:00 spamd child
root
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Will Yardley writes:
On Fri, Sep 24, 2004 at 10:22:01AM -0700, Justin Mason wrote:
Will Yardley writes:
Has anyone else seen a problem w/ spamd dying sometimes (after working
for a while)? I have been seeing this in the 3.0 rcs. I'm about
On Tue, Sep 28, 2004 at 11:56:52AM -0700, Justin Mason wrote:
Will Yardley writes:
On Fri, Sep 24, 2004 at 10:22:01AM -0700, Justin Mason wrote:
Will Yardley writes:
Much more detailed information in bug #3667 (bugzilla.spamassassin.org)
I'm almost certain it's a fixed bug.
What
Has anyone else seen a problem w/ spamd dying sometimes (after working
for a while)? I have been seeing this in the 3.0 rcs. I'm about to
upgrade to 3.0 release, but I'm wondering if anyone else has seen this.
Much more detailed information in bug #3667 (bugzilla.spamassassin.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Will Yardley writes:
Has anyone else seen a problem w/ spamd dying sometimes (after working
for a while)? I have been seeing this in the 3.0 rcs. I'm about to
upgrade to 3.0 release, but I'm wondering if anyone else has seen this.
Much more
17 matches
Mail list logo