> Hello
>
> yesterday i've done some nasty stuff. i've upgraded my
> perfect working sa 2.64 to 3.0.0-r1.
> now i have some problems with dcc and pyzor.
> all connections timed out after 10 seconds and i don't know
> why. everything works fine befor my upgrade.
>
> my system is a gentoo linux with postfix-2.1,
> amavisd-new-20030616_p9, sa-3.0.0-r1, dcc-1.2.54 and pyzor-0.4.0
>
> the first run of "amavisd debug-sa" works also great but at
> every following message that is scanned by spamassassin dcc
> and pyzor won't work.
>
> debug: Pyzor is available: /usr/bin/pyzor
> debug: entering helper-app run mode
> debug: setuid: helper proc 8014: ruid=101 euid=101
> debug: Pyzor: got response: 217.160.253.84:24441 (200,
> 'OK') 0 0
> debug: leaving helper-app run mode
> debug: DCCifd is not available: no r/w dccifd socket found.
> debug: DCC is available: /usr/bin/dccproc
> debug: entering helper-app run mode
> debug: setuid: helper proc 8015: ruid=101 euid=101
> debug: leaving helper-app run mode
> debug: DCC -> check timed out after 10 secs.
>
> is this a known problem or only at my site?
>
> thanks
> oliver hoffmann
>
> ps: please excuse my poor english. the last time i used it
> was round about 2002
>
On the amavisd list a solution was posted that worked for me.
See the following message:
============================================================================
On Wed, Sep 22, 2004 at 03:42:46PM -0700, Bill Landry wrote:
> > I just upgraded to 3.0 which seems to working. The 2.64 was from an rpm
> > which and I believe had bad rule files in it the amavisd debug-sa was
> > complaining about the rule files belonging to 2.60
> >
> > Now 3.0 starts up and nicly finds pyzor and razor and no complaints
> > about the rule files.
>
> SA 3.0 will start up nicely, and find pyzor, but will timeout on all pyzor
> queries after startup, unless you use the work-around posted to SA
bugzilla
> ID 3649. You would need to recompile and reinstall SA after making the
> change. So, unless you create your own RPM from source, you may have to
> uninstall the RPM and install from tar.gz.
DCC (dccproc) has the same problem (dccifd works fine):
debug: DCCifd is not available: no r/w dccifd socket found.
debug: DCC is available: /usr/local/bin/dccproc
DCC -> check failed: Died at
/usr/local/lib/perl5/site_perl/5.8.5/Mail/SpamAssas
sin/Dns.pm line 802.
debug: DCCifd is not available: no r/w dccifd socket found.
debug: DCC is available: /usr/local/bin/dccproc
debug: DCCifd is not available: no r/w dccifd socket found.
debug: DCC is available: /usr/local/bin/dccproc
debug: DCC -> check timed out after 10 secs.
debug: DCC -> check timed out after 10 secs.
debug: DCCifd is not available: no r/w dccifd socket found.
debug: DCC is available: /usr/local/bin/dccproc
debug: DCC -> check timed out after 10 secs.
This shows up as 'missing message body; fatal error' without debugging
on - which appears to be caused by the underlying timeout.
Patching '/usr/local/lib/perl5/site_perl/5.8.5/Mail/SpamAssassin/Dns.pm'
same as pyzor fix applies to dccproc (sub dcc_lookup):
--- Dns.pm.ORIG Wed Sep 22 13:24:09 2004
+++ Dns.pm Wed Sep 22 13:24:56 2004
@@ -789,9 +789,9 @@
dbg("DCC command: ".join(' ', $path, "-H", $opts, "< '$tmpf'",
"2>&1"),'dcc',-1);
- # my $pid = open(DCC, join(' ', $path, "-H", $opts, "< '$tmpf'",
"2>&1", '|')) || die "$!\n";
- my $pid = Mail::SpamAssassin::Util::helper_app_pipe_open(*DCC,
- $tmpf, 1, $path, "-H", split(' ', $opts));
+ my $pid = open(DCC, join(' ', $path, "-H", $opts, "< '$tmpf'", "2>&1",
'|')) || die "$!\n";
+ #my $pid = Mail::SpamAssassin::Util::helper_app_pipe_open(*DCC,
+ # $tmpf, 1, $path, "-H", split(' ', $opts));
$pid or die "$!\n";
my @null = <DCC>;
--
DELTA - Don't Ever Leave The Airport.
Mike Hall,
System Admin - Rock Island Communications <[EMAIL PROTECTED]>
System Admin - riverside.org, ssdd.org <[EMAIL PROTECTED]>
============================================================================
Hope this helps,
Erik
