You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@spamassassin.apache.org by Chris <cp...@earthlink.net> on 2005/12/11 04:06:27 UTC
Pyzor timing out
This may be OT, but has anyone noticed that pyzor has been timeing out for
the past three days? If so, anyone have any idea as to why?
--
Chris
Registered Linux User 283774 http://counter.li.org
21:05:34 up 7 days, 4:07, 2 users, load average: 1.44, 1.44, 0.82
Mandriva Linux 10.1 Official, kernel 2.6.8.1-12mdk
Re: Pyzor timing out
Posted by Pollywog <li...@shadypond.com>.
On 12/11/2005 07:27 pm, Daryl C. W. O'Shea wrote:
> SickBoy wrote:
> > Pollywog wrote:
> >> I checked another machine that has not been patched and is also running
> >> the same software versions and there were no errors there, which
> >> surprised me, since I had not applied the patch there.
>
> The 'patched errors' only happen in a select few messages. So it's
> plausible that you won't see them on a machine that hasn't been patched.
>
> If you call Pyzor from SpamAssassin you won't see them in versions
> before 3.1.0, even if they happen.
>
> > As far as I'm concerned this issue happens only with the combination of
> > Python 2.4 (I've spotted the first errors after upgrading from 2.3) AND
> > SpamAssassin 3.1.0 line (in the 3.0.x line this kind of error
> > (helper-app error) wasn't even logged).
>
> Yeah, they're not logged in versions before 3.1.0. They do happen in
> versions before then, SpamAssassin just doesn't tell you.
That explains it, I forgot I had not yet upgraded Spamassassin to 3.1 on the
other machine.
8)
Re: Pyzor timing out
Posted by "Daryl C. W. O'Shea" <sp...@dostech.ca>.
SickBoy wrote:
>
> Pollywog wrote:
>
>> I checked another machine that has not been patched and is also running the
>> same software versions and there were no errors there, which surprised me,
>> since I had not applied the patch there.
The 'patched errors' only happen in a select few messages. So it's
plausible that you won't see them on a machine that hasn't been patched.
If you call Pyzor from SpamAssassin you won't see them in versions
before 3.1.0, even if they happen.
> As far as I'm concerned this issue happens only with the combination of
> Python 2.4 (I've spotted the first errors after upgrading from 2.3) AND
> SpamAssassin 3.1.0 line (in the 3.0.x line this kind of error
> (helper-app error) wasn't even logged).
Yeah, they're not logged in versions before 3.1.0. They do happen in
versions before then, SpamAssassin just doesn't tell you.
Re: Pyzor timing out
Posted by SickBoy <si...@blupill.com>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Pollywog wrote:
>
> I checked another machine that has not been patched and is also running the
> same software versions and there were no errors there, which surprised me,
> since I had not applied the patch there.
>
>
> 8)
>
As far as I'm concerned this issue happens only with the combination of
Python 2.4 (I've spotted the first errors after upgrading from 2.3) AND
SpamAssassin 3.1.0 line (in the 3.0.x line this kind of error
(helper-app error) wasn't even logged).
- --
Regards,
SickBoy <sickboy at blupill dot com>
# Encrypted/Signed Mail Preferred.
# Public Key ID: 0x2C6FC5FE (Available on key servers)
# 61A4 EE81 CDA3 52AB 04F3 3F4A CB3B B6D5 2C6F C5FE
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (MingW32)
iD8DBQFDnHdXyzu21Sxvxf4RAqdRAKCKflcc1OP3I4t2dulyg+tesQp+dACgj949
fp9xfZGF5Xsnncff05Byr3o=
=1xno
-----END PGP SIGNATURE-----
Re: Pyzor timing out
Posted by Ed Kasky <ed...@esson.net>.
Pyzor is back up from this end:
$ pyzor ping
66.250.40.33:24441 (200, 'OK')
Ed
. . . . . . . . . . . . . . .
Randomly generated quote:
"Let no one come to you without leaving better and happier."
- Mother Teresa
Re: Pyzor timing out
Posted by Jim Knuth <jk...@jkart.de>.
Heute (am 11.12.2005) schrieb Pollywog (linux@shadypond.com),
> I checked another machine that has not been patched and is also running the
> same software versions and there were no errors there, which surprised me,
> since I had not applied the patch there.
I`ve patched nothing. And I have no errors! Never. I`m looking
for pyzor errors in the log and found: Nothing. *bg*
--
Viele Grüße, Kind regards,
Jim Knuth
jk@jkart.de
ICQ #277289867 - VoIP: +49 (0) 322 212 044 67
Key ID: 0x1F78066F
----------
Zufalls-Zitat
----------
Es ist leichter ein Atom zu zertrümmern, als ein Vorurteil.
(Albert Einstein)
----------
Der Text hat nichts mit dem Empfänger der Mail zu tun
----------
Virus free. Checked by NOD32 Version 1.1317 Build 6429 09.12.2005
Re: Pyzor timing out
Posted by Pollywog <li...@shadypond.com>.
On 12/11/2005 06:46 pm, SickBoy wrote:
>
> In the time of our lil' conversation pyzor got back from dead and it's
> functioning properly now.
>
> The thing I ment was that the pyzor suddenly died few days ago, and
> finnaly got back this afternoon; applying a patch has nothing to do with
> the server response by itself, the patch is for some "unusual" strings
> that can be found in the email (and that caused the error message) in
> process of making a digest of it before checking for matches with the
> pyzor server.
I checked another machine that has not been patched and is also running the
same software versions and there were no errors there, which surprised me,
since I had not applied the patch there.
8)
Re: Pyzor timing out
Posted by Raymond Dijkxhoorn <ra...@prolocation.net>.
Hi!
>> pyzor -d ping
> Mine says this, but I applied the 3 in 1 patch that I learned about in this
> thread:
> sending: 'User: anonymous\nTime: 1134325707\nSig:
> 177d0df77c0b91197da93b41c85c4f5f3d9b823b\n\nOp: ping\nThread: 31207\nPV:
> 2.0\n\n'
> received: 'Thread: 31207\nCode: 200\nDiag: OK\nPV: 2.0\n\n'
> 66.250.40.33:24441 (200, 'OK')
Most likely the problem is fixed on Pyzors servers backend. We had several
machines not beeing able to reach (pyzor ping) the pyzor box. They are now
working again, without patching the engine. So most likely the troubles
others saw also went away.
Bye,
Raymond.
Re: Pyzor timing out
Posted by SickBoy <si...@blupill.com>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Pollywog wrote:
>
> Mine says this, but I applied the 3 in 1 patch that I learned about in this
> thread:
>
>
> sending: 'User: anonymous\nTime: 1134325707\nSig:
> 177d0df77c0b91197da93b41c85c4f5f3d9b823b\n\nOp: ping\nThread: 31207\nPV:
> 2.0\n\n'
> received: 'Thread: 31207\nCode: 200\nDiag: OK\nPV: 2.0\n\n'
> 66.250.40.33:24441 (200, 'OK')
>
>
> 8)
In the time of our lil' conversation pyzor got back from dead and it's
functioning properly now.
The thing I ment was that the pyzor suddenly died few days ago, and
finnaly got back this afternoon; applying a patch has nothing to do with
the server response by itself, the patch is for some "unusual" strings
that can be found in the email (and that caused the error message) in
process of making a digest of it before checking for matches with the
pyzor server.
- --
Regards,
SickBoy <sickboy at blupill dot com>
# Encrypted/Signed Mail Preferred.
# Public Key ID: 0x2C6FC5FE (Available on key servers)
# 61A4 EE81 CDA3 52AB 04F3 3F4A CB3B B6D5 2C6F C5FE
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (MingW32)
iD8DBQFDnHQXyzu21Sxvxf4RAq6eAJ0b/MlEv1iIFnIGTlryF7eykjOAZgCfYRNn
rzeo8QSM6kAlrbXqeHQQ6L0=
=Dw4S
-----END PGP SIGNATURE-----
Re: Pyzor timing out
Posted by Pollywog <li...@shadypond.com>.
On 12/11/2005 11:13 am, SickBoy wrote:
> pyzor -d ping
Mine says this, but I applied the 3 in 1 patch that I learned about in this
thread:
sending: 'User: anonymous\nTime: 1134325707\nSig:
177d0df77c0b91197da93b41c85c4f5f3d9b823b\n\nOp: ping\nThread: 31207\nPV:
2.0\n\n'
received: 'Thread: 31207\nCode: 200\nDiag: OK\nPV: 2.0\n\n'
66.250.40.33:24441 (200, 'OK')
8)
Re: Pyzor timing out
Posted by SickBoy <si...@blupill.com>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Jim Knuth wrote:
> Heute (am 11.12.2005) schrieb Chris,
>
>
>>This may be OT, but has anyone noticed that pyzor has been timeing out for
>>the past three days? If so, anyone have any idea as to why?
>
>
>
> no problems here
>
>
Hmm, are you SURE ? Patching pyzor against runtime errors is one thing,
but still, can U post the output of 'pyzor -d ping' here ?
See what will happen ...
- --
Regards,
SickBoy <sickboy at blupill dot com>
# Encrypted/Signed Mail Preferred.
# Public Key ID: 0x2C6FC5FE (Available on key servers)
# 61A4 EE81 CDA3 52AB 04F3 3F4A CB3B B6D5 2C6F C5FE
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (MingW32)
iD8DBQFDnAnhyzu21Sxvxf4RAulXAJ9vfL7L7bQspCAxHkaN//6mQF0KhQCfcg4Y
UJ50G9R7In0LejGA8eH0yKg=
=ZzFN
-----END PGP SIGNATURE-----
Re: Pyzor timing out
Posted by Jim Knuth <jk...@jkart.de>.
Heute (am 11.12.2005) schrieb Chris,
> This may be OT, but has anyone noticed that pyzor has been timeing out for
> the past three days? If so, anyone have any idea as to why?
no problems here
--
Viele Grüße, Kind regards,
Jim Knuth
jk@jkart.de
ICQ #277289867 - VoIP: +49 (0) 322 212 044 67
Key ID: 0x1F78066F
----------
Zufalls-Zitat
----------
Die Dinge, auf die es im Leben wirklich ankommt,
kann man nicht kaufen.
(William Faulkener)
----------
Der Text hat nichts mit dem Empfänger der Mail zu tun
----------
Virus free. Checked by NOD32 Version 1.1317 Build 6429 09.12.2005
Re: Pyzor timing out
Posted by Pollywog <li...@shadypond.com>.
On 12/11/2005 03:35 am, Chris wrote:
> You can obtain a patch for that here that takes care of that problem:
>
> From http://bugzilla.spamassassin.org/show_bug.cgi?id=4580
>
> To make it simple, I have combined those 3 patches into 1...
> http://www.engelken.net/download/pyzor.patch
>
> Just cd to your python2.x/site-packages/pyzor dir, and patch -p0 on it.
> Example code from a shell script that installs pyzor...
>
> # patch pyzor
> if [ -e "/usr/lib/python2.3/site-packages/pyzor" ]; then
> cd /usr/lib/python2.3/site-packages/pyzor
> patch -p0 < $DIR/patches/pyzor.patch 2>&1 >/dev/null
> fi
>
> The above from the pyzor mailing list.
thanks
8)
Re: Pyzor timing out
Posted by Chris <cp...@earthlink.net>.
On Saturday 10 December 2005 9:20 pm, Pollywog wrote:
> On 12/11/2005 03:06 am, Chris wrote:
> > This may be OT, but has anyone noticed that pyzor has been timeing out
> > for the past three days? If so, anyone have any idea as to why?
>
> I have been seeing this in my logs:
>
> pyzor: check failed: internal error
>
>
> I upgraded Spamassassin to version 3.1 about 3 days ago and thought
> perhaps it was a bug since I had not noticed the error messages in the
> logs before that.
>
>
> 8)
You can obtain a patch for that here that takes care of that problem:
From http://bugzilla.spamassassin.org/show_bug.cgi?id=4580
To make it simple, I have combined those 3 patches into 1...
http://www.engelken.net/download/pyzor.patch
Just cd to your python2.x/site-packages/pyzor dir, and patch -p0 on it.
Example code from a shell script that installs pyzor...
# patch pyzor
if [ -e "/usr/lib/python2.3/site-packages/pyzor" ]; then
cd /usr/lib/python2.3/site-packages/pyzor
patch -p0 < $DIR/patches/pyzor.patch 2>&1 >/dev/null
fi
The above from the pyzor mailing list.
--
Chris
Registered Linux User 283774 http://counter.li.org
21:35:05 up 7 days, 4:37, 2 users, load average: 0.36, 0.77, 0.89
Mandriva Linux 10.1 Official, kernel 2.6.8.1-12mdk
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
"OK, now let's look at four dimensions on the blackboard."
-- Dr. Joy
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Re: Pyzor timing out
Posted by Pollywog <li...@shadypond.com>.
On 12/11/2005 03:06 am, Chris wrote:
> This may be OT, but has anyone noticed that pyzor has been timeing out for
> the past three days? If so, anyone have any idea as to why?
I have been seeing this in my logs:
pyzor: check failed: internal error
I upgraded Spamassassin to version 3.1 about 3 days ago and thought perhaps it
was a bug since I had not noticed the error messages in the logs before that.
8)