Re: Pyzor problem
On Thursday 30 September 2010 06:57:15 Gerald Turner wrote: Hans-Werner Friedemann h-w.friedem...@vds-herzberg.de writes: Hi @ all what´s the matter with pyzor if I get the following hint by starting spamd? Wed Sep 29 11:23:29 2010 [5176] info: zoom: able to use 675/1223 'body_0' compiled rules (55.192%) Wed Sep 29 11:23:39 2010 [5176] info: pyzor: [5182] error: TERMINATED, signal 15 (000f) I've been investigating this problem as well, I believe it is a timeout error. People have been discussing the timeout issue on the pyzor mailing list for months, with no resolution: http://sourceforge.net/mailarchive/forum.php?thread_name=4C07B30A.8080300%4 0spamexperts.comforum_name=pyzor-users Yes, it is a timeout error. If you examine timestamps you can see that exactly 10 seconds passed since the previous log entry. Signal 15 is a TERMination signal sent from spamd (or amavisd) to the pyzor subprocess. The pyzor timeout is configurable through the pyzor_timeout setting. Mark
RE: pyzor problem.
Rose, Bobby wrote: I thought that was the purpose of the pyzor discover command? Who maintains 82.94.255.100 as it doesn't get listed with pyzor discover. The alternative server aparently never got added to the discovery service so the discover command will reset the contents to the original server. I completely disabled Pyzor because even when the alternative server is used, we experience too much delay from it. Razor and DCC are much faster here and scoring is good enough already. Rob
Re: pyzor problem.
We noticed pyzor latency/timeouts last week and had to disable it. User for SpamAssassin Mail List wrote: Hello, I've noticed a big jump in spam here and looking through logs it looks like my system is not getting pyzor to respond. When I do a spamassassin --lint -D I show: debug: Pyzor is available: /usr/bin/pyzor debug: Pyzor: got response: 66.250.40.33:24441 TimeoutError: debug: Pyzor: couldn't grok response 66.250.40.33:24441TimeoutError: Has something changed with pyzor as of late ? Anyone have any clues? Thanks, Ken -- Joel Nimety Perimeter eSecurity Product Architect, Email Defense 203.541.3416 [EMAIL PROTECTED] http://www.perimeterusa.com -- The sender of this email subscribes to Perimeter eSecurity's email anti-virus service. This email has been scanned for malicious code and is believed to be virus free. For more information on email security please visit: http://www.perimeterusa.com/email-defense-content.html This communication is confidential, intended only for the named recipient(s) above and may contain trade secrets or other information that is exempt from disclosure under applicable law. Any use, dissemination, distribution or copying of this communication by anyone other than the named recipient(s) is strictly prohibited. If you have received this communication in error, please delete the email and immediately notify our Command Center at 203-541-3444. Thanks
Re: pyzor problem.
We noticed pyzor latency/timeouts last week and had to disable it. User for SpamAssassin Mail List wrote: Hello, I've noticed a big jump in spam here and looking through logs it looks like my system is not getting pyzor to respond. When I do a spamassassin --lint -D I show: debug: Pyzor is available: /usr/bin/pyzor debug: Pyzor: got response: 66.250.40.33:24441 TimeoutError: debug: Pyzor: couldn't grok response 66.250.40.33:24441 TimeoutError: Has something changed with pyzor as of late ? Anyone have any clues? Thanks, Ken -- Joel Nimety I think the main server has been overloaded for a couple years now. Find .../.pyzor/servers file and replace 66.250.40.33:24441 with 82.94.255.100:24441 It should help. Gary V _ http://newlivehotmail.com
Re: pyzor problem.
On Mon, 30 Jul 2007, Gary V wrote:
We noticed pyzor latency/timeouts last week and had to disable it.
User for SpamAssassin Mail List wrote:
Hello,
I've noticed a big jump in spam here and looking through logs it looks
like my system is not getting pyzor to respond.
When I do a spamassassin --lint -D
I show:
debug: Pyzor is available: /usr/bin/pyzor
debug: Pyzor: got response: 66.250.40.33:24441 TimeoutError:
debug: Pyzor: couldn't grok response 66.250.40.33:24441
TimeoutError:
Has something changed with pyzor as of late ?
Anyone have any clues?
Thanks,
Ken
--
Joel Nimety
I think the main server has been overloaded for a couple years now. Find
.../.pyzor/servers file and replace 66.250.40.33:24441 with
82.94.255.100:24441
It should help.
Gary V
Gary,
That server 82.94.255.100:24441 solved the problem. The next problem was
how to change that IP address in the ~/.pyzor/servers files for all the
customers. So I put together a script to do just that. Here is that script
in case others want to do the same thing.
Thanks,
Ken
You must put in a servers file in the /etc/skel/.pyzor directory with
82.94.255.100:24441 in the servers file.
Script follows:
#! /bin/sh
#
#This script changes the pyzor server in each users home directory to
#the server that is listed in /etc/skel/.pyzor/servers .
#This became a problem when the primary server stopped
#responding. - knr - 7-07
#
#
#
USERNAME=
cd /home
for USERNAME in `ls -d *`;
do
if [ -d /home/${USERNAME}/.pyzor ]; then
if [ -f /home/${USERNAME}/.pyzor/servers ]; then
cp /etc/skel/.pyzor/servers /home/${USERNAME}/.pyzor/servers;
chown ${USERNAME}:users /home/${USERNAME}/.pyzor/servers;
fi
fi
done
RE: pyzor problem.
I thought that was the purpose of the pyzor discover command? Who
maintains 82.94.255.100 as it doesn't get listed with pyzor discover.
-Original Message-
From: User for SpamAssassin Mail List [mailto:[EMAIL PROTECTED]
Sent: Monday, July 30, 2007 6:56 PM
To: Gary V
Cc: users@spamassassin.apache.org
Subject: Re: pyzor problem.
On Mon, 30 Jul 2007, Gary V wrote:
We noticed pyzor latency/timeouts last week and had to disable it.
User for SpamAssassin Mail List wrote:
Hello,
I've noticed a big jump in spam here and looking through logs it
looks like my system is not getting pyzor to respond.
When I do a spamassassin --lint -D
I show:
debug: Pyzor is available: /usr/bin/pyzor
debug: Pyzor: got response: 66.250.40.33:24441 TimeoutError:
debug: Pyzor: couldn't grok response 66.250.40.33:24441
TimeoutError:
Has something changed with pyzor as of late ?
Anyone have any clues?
Thanks,
Ken
--
Joel Nimety
I think the main server has been overloaded for a couple years now.
Find .../.pyzor/servers file and replace 66.250.40.33:24441 with
82.94.255.100:24441
It should help.
Gary V
Gary,
That server 82.94.255.100:24441 solved the problem. The next problem
was how to change that IP address in the ~/.pyzor/servers files for all
the customers. So I put together a script to do just that. Here is that
script in case others want to do the same thing.
Thanks,
Ken
You must put in a servers file in the /etc/skel/.pyzor directory with
82.94.255.100:24441 in the servers file.
Script follows:
#! /bin/sh
#
#This script changes the pyzor server in each users home directory
to
#the server that is listed in /etc/skel/.pyzor/servers .
#This became a problem when the primary server stopped
#responding. - knr - 7-07
#
#
#
USERNAME=
cd /home
for USERNAME in `ls -d *`;
do
if [ -d /home/${USERNAME}/.pyzor ]; then
if [ -f /home/${USERNAME}/.pyzor/servers ]; then
cp /etc/skel/.pyzor/servers
/home/${USERNAME}/.pyzor/servers;
chown ${USERNAME}:users
/home/${USERNAME}/.pyzor/servers;
fi
fi
done
RE: pyzor problem.
I thought that was the purpose of the pyzor discover command? Who maintains 82.94.255.100 as it doesn't get listed with pyzor discover. http://marc.info/?l=spamassassin-usersm=117911370318308 _ http://liveearth.msn.com
Re: Pyzor problem
Mark wrote: In Pyzor.pm, internal error is actually a mask for the infamous error: Traceback (most recent call last): ... Yeah, there are certain types of input that Pyzor chokes on, like messages with bogus character encodings. Unfortunately, development stopped before it was fixed to gracefully handle these conditions, and no one seems to have picked it up to patch it. -- Kelson Vibber SpeedGate Communications www.speed.net
