From: "Steve [Gentoo]" <gentoo_steve@shic.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Spamassassin 3.1 now fails...
Date: Thu, 24 Nov 2005 10:19:18 +0000 [thread overview]
Message-ID: <438593A6.3070802@shic.co.uk> (raw)
A few days I 'updated world' and spamassassin 3.04 was replaced by
spamassassin 3.1 - after a few minutes spent migrating my configuration
(to enable Razor,Pyzor and DCC) all seemed to be working well... but
then, after running fine for a day or two, the spamd daemon stopped
responding and started writing an error about "syswrite(7) to the system
log every few seconds:
--
Nov 24 00:31:12 gifu postfix/qmgr[3563]: 9ADC2137F91: removed
Nov 24 00:31:12 gifu spamd[26279]: prefork: child states: BBBII
Nov 24 00:31:14 gifu postfix/smtpd[24866]: disconnect from
localhost[127.0.0.1]
Nov 24 00:32:40 gifu spamd[26279]: prefork: syswrite(7) failed,
retrying... at /
usr/lib/perl5/vendor_perl/5.8.6/Mail/SpamAssassin/SpamdForkScaling.pm
line 554.
Nov 24 00:32:45 gifu spamd[26279]: prefork: syswrite(7) failed,
retrying... at /
usr/lib/perl5/vendor_perl/5.8.6/Mail/SpamAssassin/SpamdForkScaling.pm
line 554.
--
Subsequently mail was (as far as I can tell) delivered without tagging
messages. When I restart spamasssassin (i.e. /etc/init.d/spamd restart)
the problem disappears - at least temporarily This is not a one-off
occurrence - but I do not know what triggers the failure. On this
occasion spamassasssin failed reporting syswrite(7) last time it
reported syswrite(8) but otherwise behaviour was similar. The time at
which the failure occurred does not seem to be relevant as while this
time it was at just past midnight, previously it failed at 15:30.
Does anyone else have this problem with Spamassassin 3.1?
--
gentoo-user@gentoo.org mailing list
reply other threads:[~2005-11-24 10:25 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=438593A6.3070802@shic.co.uk \
--to=gentoo_steve@shic.co.uk \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox