Hi, sorry for taking *forever* to reply. I had pretty much forgotten
about this.
Well, pretty much, the 'internal error' is just spamd's way of saying
that something went wrong. In this case a debug ('spamassassin -D
–lint' or something like it) would be really useful to me.
Here's what lint has to say on the issue:
[12662] dbg: plugin: registering glue method for check_pyzor
(Mail::SpamAssassin::Plugin::Pyzor=HASH(0x94237e0))
[12662] dbg: util: current PATH is:
/usr/local/bin:/usr/bin:/bin:/usr/games
[12662] dbg: util: executable for pyzor was found at /usr/bin/pyzor
[12662] dbg: pyzor: pyzor is available: /usr/bin/pyzor
[12662] dbg: info: entering helper-app run mode
[12662] dbg: pyzor: opening pipe: /usr/bin/pyzor check <
/tmp/.spamassassin12662gJfoeetmp
[12695] dbg: util: setuid: ruid=89 euid=89
[12662] dbg: pyzor: killed stale helper [12695]
[12662] dbg: pyzor: [12695] terminated: exit=0x000f
[12662] dbg: info: leaving helper-app run mode
[12662] dbg: pyzor: check timed out after 5 seconds
Note however that it does not fail every time - sometimes it doesn't.
This was run directly after the previous command, same user, no changes
whatsoever:
[22677] dbg: plugin: registering glue method for check_pyzor
(Mail::SpamAssassin::Plugin::Pyzor=HASH(0x94237e0))
[22677] dbg: util: current PATH is:
/usr/local/bin:/usr/bin:/bin:/usr/games
[22677] dbg: util: executable for pyzor was found at /usr/bin/pyzor
[22677] dbg: pyzor: pyzor is available: /usr/bin/pyzor
[22677] dbg: info: entering helper-app run mode
[22677] dbg: pyzor: opening pipe: /usr/bin/pyzor check <
/tmp/.spamassassin22677e7FBSStmp
[22731] dbg: util: setuid: ruid=89 euid=89
[22677] dbg: pyzor: [22731] finished: exit=0x0100
[22677] dbg: pyzor: got response: 66.250.40.33:24441_(200, 'OK')_0_0
[22677] dbg: info: leaving helper-app run mode
SA's log just keeps barfing out internal errors, and Pyzor is still not
actually detecting anything.
Although I know of another cause (besides the one that I fixed in -6)
that could cause an internal error. Per [1] it seems that an error
(this is with -D --lint) such as
[26906] dbg: pyzor: got response: Traceback (most recent call
last):\n File "/usr/bin/pyzor", line 4, in ?\n
pyzor.client.run()\n File
"/usr/lib/python2.4/site-packages/pyzor/client.py", line 934, in
run\n ExecCall().run()\n File
"/usr/lib/python2.4/site-packages/pyzor/client.py", line 169, in
run\n os.mkdir(homedir)\nOSError: [Errno 20] Not a directory:
'/dev/null/.pyzor'
[26906] dbg: info: leaving helper-app run mode
[26906] warn: pyzor: check failed: internal error
could happen. I'm not convinced that this is a pyzor flaw as it has
to do with pyzor not getting a valid home directory, which, to store
servers and configs, it pretty much needs. If this is the case, I
think that you should run SA under a user that has a home directory,
though I could be convinced otherwise.
Anyways, this is all mute if the home directory issue is not really
your problem. If you could get back to me with a debug log or some
more information that would be most helpful.
AFAIK Pyzor should have a home directory (the user running Pyzor
certainly has, anyway), and this error doesn't seem similar to what I'm
seeing in my lint.
FWIW it seems the last spam mails I have that were actually detected by
Pyzor are from 2004-11-12, so if there was any new version released
around that day or something..
Running Pyzor directly also gives the same result:
$ pyzor check <
1147130486.M705139P28083V0000000000000807I010E3C8B_0.betty\,S\=37225\:2\,S
66.250.40.33:24441 TimeoutError:
And again a few seconds later:
$ pyzor check <
1147130486.M705139P28083V0000000000000807I010E3C8B_0.betty\,S\=37225\:2\,S
66.250.40.33:24441 (200, 'OK') 0 0
All other Pyzor commands (ping, discover etc.) seem to work fine.
Any clues would be appreciated, and if there's anything more you want
me to check, I'll try to take slightly less time than I did now. :)
Thanks!
--
-==- -=- -==-
Christer Mjellem Strand yitzhaq
Systems Administrator www.yitzhaq.net
GSM +47 922 000 12 www.countzero.no
-==- -=- -==-
