Bug 4580 - warn: pyzor: check failed: internal error
Summary: warn: pyzor: check failed: internal error
Status: RESOLVED INVALID
Alias: None
Product: Spamassassin
Classification: Unclassified
Component: Plugins (show other bugs)
Version: SVN Trunk (Latest Devel Version)
Hardware: PC FreeBSD
: P5 normal
Target Milestone: Undefined
Assignee: SpamAssassin Developer Mailing List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-09-13 12:57 UTC by Andy Jezierski
Modified: 2008-11-24 06:48 UTC (History)
2 users (show)


Attachment Type Modified Status Actions Submitter/CLA Status
Sample errors from debug log. text/plain None Andy Jezierski [NoCLA]
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Andy Jezierski 2005-09-13 12:57:48 UTC 
Error pops up every now and then, turned on debug and found a few traceback 
errors from pyzor in the log file. Samples from three different messages 
attached.
Comment 1 Andy Jezierski 2005-09-13 12:58:40 UTC 
Created attachment 3135 [details]
Sample errors from debug log.
Comment 2 Martin Blapp 2005-09-13 16:26:50 UTC 
Hi,

Have a look at:

http://antispam.imp.ch/08-opensource.html?lng=0

It will fix your pyzor problems.

Martin
Comment 3 Petr KLOSKO 2005-09-15 13:00:51 UTC 
I've this same problem @slack10.1, python 2.4.1 , SA  3.1.0 , pyzor 0.4.0
After /usr/bin/ptyhon --homedir /python check < /tmp/testmail

Ho can I path my pyzor installation ?

THX
Comment 4 Andy Jezierski 2005-09-15 13:09:15 UTC 
Yep, this seems to be a Pyzor error and not SA.  Applied the three patches in 
the link provided by Martin and it seems like the errors have been corrected.
Comment 5 Petr KLOSKO 2005-09-18 09:50:24 UTC 
Yes, it seems like pyzor error, but on lastet version (3.0.4 ?) was everything OK.
After pyzor patch :
/usr/bin/pyzor --homedir=CONFIG discover
/usr/bin/pyzor --homedir=CONFIG ping ........ =  OK
/usr/bin/pyzor --homedir=CONFIG check < textmail.txt  ...... = NOTHING 

In SA.log spamassassin -D < testmail.txt :
...
dbg: pyzor : pyzor is available
dbg: pyzor : opening pipe : /usr/bin/pyzor --homedir=CONFIG < /tmp/sa.xxxxxxx
dbg: pyzor : [PID] finished: exit=0x0100
dbg: pyzor : check failed : no response
...
Comment 6 Daryl C. W. O'Shea 2005-09-27 17:14:06 UTC 
This isn't a SpamAssassin error.  We're just now reporting the Pyzor error.

The patches in comment #2 are reported to fix the Pyzor errors.
Comment 7 Borja Pacheco 2005-10-13 05:12:06 UTC 
(In reply to comment #2)
> Hi,
> 
> Have a look at:
> 
> http://antispam.imp.ch/08-opensource.html?lng=0
> 
> It will fix your pyzor problems.
> 
> Martin


Dear Martin,

I've patched my pyzor with all these patches, and I can't get spamassassin works
again with pyzor (it all the time says: 
Oct 13 14:04:50 spamd[751]: internal error
Oct 13 14:04:50 spamd[751]: pyzor: check failed: internal error)

I've tested pyzor standalone (using ping and check) and it works.

Any suggestion??
Comment 8 Jeremy Davila 2008-11-20 13:37:28 UTC 
How exactly do you apply the patches. I am using Fedora Core 5. Any help will be greatly appreciated.
Comment 9 Tom Schulz 2008-11-24 06:48:14 UTC 
If you have the patch in a file you can use the patch utility. I use the command

patch -p0 -b -Vt < patchfile

Where patchfile is the path to the patch file.  Type 'man patch' to see what
those switches do.