1 |
A few days I 'updated world' and spamassassin 3.04 was replaced by |
2 |
spamassassin 3.1 - after a few minutes spent migrating my configuration |
3 |
(to enable Razor,Pyzor and DCC) all seemed to be working well... but |
4 |
then, after running fine for a day or two, the spamd daemon stopped |
5 |
responding and started writing an error about "syswrite(7) to the system |
6 |
log every few seconds: |
7 |
|
8 |
-- |
9 |
Nov 24 00:31:12 gifu postfix/qmgr[3563]: 9ADC2137F91: removed |
10 |
Nov 24 00:31:12 gifu spamd[26279]: prefork: child states: BBBII |
11 |
Nov 24 00:31:14 gifu postfix/smtpd[24866]: disconnect from |
12 |
localhost[127.0.0.1] |
13 |
Nov 24 00:32:40 gifu spamd[26279]: prefork: syswrite(7) failed, |
14 |
retrying... at / |
15 |
usr/lib/perl5/vendor_perl/5.8.6/Mail/SpamAssassin/SpamdForkScaling.pm |
16 |
line 554. |
17 |
Nov 24 00:32:45 gifu spamd[26279]: prefork: syswrite(7) failed, |
18 |
retrying... at / |
19 |
usr/lib/perl5/vendor_perl/5.8.6/Mail/SpamAssassin/SpamdForkScaling.pm |
20 |
line 554. |
21 |
-- |
22 |
|
23 |
Subsequently mail was (as far as I can tell) delivered without tagging |
24 |
messages. When I restart spamasssassin (i.e. /etc/init.d/spamd restart) |
25 |
the problem disappears - at least temporarily This is not a one-off |
26 |
occurrence - but I do not know what triggers the failure. On this |
27 |
occasion spamassasssin failed reporting syswrite(7) last time it |
28 |
reported syswrite(8) but otherwise behaviour was similar. The time at |
29 |
which the failure occurred does not seem to be relevant as while this |
30 |
time it was at just past midnight, previously it failed at 15:30. |
31 |
|
32 |
Does anyone else have this problem with Spamassassin 3.1? |
33 |
|
34 |
-- |
35 |
gentoo-user@g.o mailing list |