pyzor-users

Errors after upgrade

[Chris <cpo...@em...>]

System is Ubuntu 14.04 LTS. This morning I upgraded to the newest
version of Pyzor using this command as shown on the webpage:

pip install --upgrade pyzor

Since then I've been seeing this in my syslog:
Aug 31 10:02:43 localhost spamd[2645]: pyzor: check failed: internal
error, python traceback seen in response

Aug 31 10:07:02 localhost spamd[2645]: pyzor: check failed: internal
error, python traceback seen in response

Aug 31 10:35:38 localhost spamd[2645]: pyzor: check failed: internal
error, python traceback seen in response

I've attached the .pip.log from the install which I did as user. There
seemed to be some errors that were shown in red so I did a sudo pip
install --upgrade pyzor also. I notice now that there is also a .pyzor
folder in / as well as the original one that is in ~/.pyzor.

Thanks for any advice or even a 2x4 upside the head.

Chris


-- 
Chris
31.11°N 97.89°W (Elev. 1092 ft)
11:55:42 up 13:59, 1 user, load average: 0.32, 0.36, 0.29
Ubuntu 14.04 LTS, kernel 3.13.0-35-generic

Re: Errors after upgrade

[Tony M. <to...@sp...>]

> Since then I've been seeing this in my syslog:
> Aug 31 10:02:43 localhost spamd[2645]: pyzor: check failed: internal
> error, python traceback seen in response

It’d be very useful to know what the error is.  Trying running pyzor by itself, rather than through SpamAssassin, e.g.:

$ pyzor ping
public.pyzor.org:24441	(200, 'OK')
$ pyzor check
Subject: Hello world!

Test
public.pyzor.org:24441	(200, 'OK')	219150	12833

You’ll presumably not get those responses, and get an error instead.

Re: Errors after upgrade

[Chris <cpo...@em...>]

On Tue, 2014-09-02 at 23:32 +1200, Tony Meyer wrote:
> > Since then I've been seeing this in my syslog:
> > Aug 31 10:02:43 localhost spamd[2645]: pyzor: check failed: internal
> > error, python traceback seen in response
> 
> It’d be very useful to know what the error is.  Trying running pyzor by itself, rather than through SpamAssassin, e.g.:
> 
> $ pyzor ping
> public.pyzor.org:24441	(200, 'OK')
> $ pyzor check
> Subject: Hello world!
> 
> Test
> public.pyzor.org:24441	(200, 'OK')	219150	12833
> 
> You’ll presumably not get those responses, and get an error instead.

Pyzor ping works fine:

chris@localhost:~$ pyzor ping
public.pyzor.org:24441	(200, 'OK')

Pyzor check however just nets me a blinking cursor until I interrupt the
process with Ctrl-C which gives me:

chris@localhost:~$ pyzor check
^CTraceback (most recent call last):
  File "/usr/local/bin/pyzor", line 336, in <module>
    main()
  File "/usr/local/bin/pyzor", line 141, in main
    if not dispatch(client, servers, config):
  File "/usr/local/bin/pyzor", line 217, in check
    for digested in get_input_handler(style):
  File "/usr/local/bin/pyzor", line 159, in get_input_handler
    msg = email.message_from_file(sys.stdin)
  File "/usr/lib/python2.7/email/__init__.py", line 66, in
message_from_file
    return Parser(*args, **kws).parse(fp)
  File "/usr/lib/python2.7/email/parser.py", line 68, in parse
    data = fp.read(8192)
KeyboardInterrupt
 gives me:

but it's probably there because of the interrupted process.

-- 
Chris
31.11°N 97.89°W (Elev. 1092 ft)
07:25:54 up 2 days, 9:29, 3 users, load average: 0.17, 0.10, 0.07
Ubuntu 14.04 LTS, kernel 3.13.0-35-generic

Re: Errors after upgrade (Solved)

[Chris <cpo...@em...>]

On Tue, 2014-09-02 at 07:31 -0500, Chris wrote:
> On Tue, 2014-09-02 at 23:32 +1200, Tony Meyer wrote:
> > > Since then I've been seeing this in my syslog:
> > > Aug 31 10:02:43 localhost spamd[2645]: pyzor: check failed: internal
> > > error, python traceback seen in response
> > 
> > It’d be very useful to know what the error is.  Trying running pyzor by itself, rather than through SpamAssassin, e.g.:
> > 
> > $ pyzor ping
> > public.pyzor.org:24441	(200, 'OK')
> > $ pyzor check
> > Subject: Hello world!
> > 
> > Test
> > public.pyzor.org:24441	(200, 'OK')	219150	12833
> > 
> > You’ll presumably not get those responses, and get an error instead.
> 
> Pyzor ping works fine:
> 
> chris@localhost:~$ pyzor ping
> public.pyzor.org:24441	(200, 'OK')
> 
> Pyzor check however just nets me a blinking cursor until I interrupt the
> process with Ctrl-C which gives me:
> 
> chris@localhost:~$ pyzor check
> ^CTraceback (most recent call last):
>   File "/usr/local/bin/pyzor", line 336, in <module>
>     main()
>   File "/usr/local/bin/pyzor", line 141, in main
>     if not dispatch(client, servers, config):
>   File "/usr/local/bin/pyzor", line 217, in check
>     for digested in get_input_handler(style):
>   File "/usr/local/bin/pyzor", line 159, in get_input_handler
>     msg = email.message_from_file(sys.stdin)
>   File "/usr/lib/python2.7/email/__init__.py", line 66, in
> message_from_file
>     return Parser(*args, **kws).parse(fp)
>   File "/usr/lib/python2.7/email/parser.py", line 68, in parse
>     data = fp.read(8192)
> KeyboardInterrupt
>  gives me:
> 
> but it's probably there because of the interrupted process.
> 
Through several suggestions from private email and on the SA list I have
it working again. I added a few lines to my /etc/mail/spamassassin
local.cf:

ifplugin Mail::SpamAssassin::Plugin::Pyzor
pyzor_path /usr/local/bin/pyzor
pyzor_options --homedir /etc/mail/spamassassin/.pyzor
endif

and copied the .pyzor folder over from my home. Restarted SA and pyzor
seems to be working now.

Chris


-- 
Chris
31.11°N 97.89°W (Elev. 1092 ft)
15:59:53 up 2 days, 18:03, 1 user, load average: 0.33, 0.22, 0.17
Ubuntu 14.04 LTS, kernel 3.13.0-35-generic