On 10/6/2011 1:37 PM, John Hinton wrote:> Had anybody been successful in getting Pyzor to run on CentOS 6 64bit? I
> have it running fine on CentOS 6 32 bit, and I 'think' I did
identical
> installs. But, from the command line I keep getting
>
> Oct 6 13:36:00.659 [16065] dbg: pyzor: network tests on, attempting Pyzor
> Oct 6 13:36:06.205 [16065] dbg: pyzor: pyzor is available: /usr/bin/pyzor
> Oct 6 13:36:06.206 [16065] dbg: pyzor: opening pipe: /usr/bin/pyzor
> check< /tmp/.spamassassin160655GZkVEtmp
> Oct 6 13:36:06.281 [16065] dbg: pyzor: [16168] finished: exit 1
> Oct 6 13:36:06.282 [16065] dbg: pyzor: check failed: no response
>
> And, yes the firewall port is open and I can ping pyzor.
>
> Been Googling this for hours now.... lots of returns without any helpful
> info. And 'odd' that it is running fine on 32 bit. And of course,
the 32
> bit install is for internal use while the 64 bit system needs to go live
> to the public really fast!
>
OK, so I'm an idiot!!! arrgh! I started comparing every file and every
directory for all of the anti-spam stuff and guess what I found? On the
64bit system sample-spam.txt had 0 bytes. Well, I suppose everything was
working just as it should have been. That file on the 32 bit system has
a date of March 16 2010, so I didn't put that text in there. Anyway,
after adding in the spam text on the 64 bit system... it all works.
Why is it so often that the most obvious is the hardest to find? And
why is this a 0 byte file instead of just not being there at all?
On the 32bit system, spamassassin was installed from base.
On the 64bit system, spamassassin was installed from anaconda during
full server installation.
--
John Hinton
877-777-1407 ext 502
http://www.ew3d.com
Comprehensive Online Solutions