[spambayes-bugs] [ spambayes-Bugs-966487 ] uncaptured python exception ... object has no attribute 'isC

[SourceForge.net]

Bugs item #966487, was opened at 2004-06-05 00:51
Message generated for change (Comment added) made by anadelonbrin
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=498103&aid=966487&group_id=61702

Category: pop3proxy
Group: Source code - CVS
Status: Open
Resolution: None
Priority: 5
Submitted By: Michal Vitecek (fufsource)
>Assigned to: Tony Meyer (anadelonbrin)
Summary: uncaptured python exception ... object has no attribute 'isC

Initial Comment:
hello,

CVS of spambayes as well as 1.0rc1 crashes on our mailserver 
after running for 1 hour up to 1 day. the bug was reported for the 
1st time (i think) in January (see http://mail.python.
org/pipermail/spambayes-bugs/2004-January/001857.html). the 
version 1.0a7 worked just fine for me (as opposed to Gisli's 
message). we're running python 2.3 on the mailserver.

a snippet of the original message follows:

Gisli Ottarsson gisli.ottarsson at mscsoftware.com:

I have fetchmail sucking e-mail through a spambayes pop3 proxy. I 
am using spambayes-1.0a7 and have tried both python 2.2 and 2.3.  
The computer is running Debian unstable.

This is working very well, except about once every 24 hours 
spambayes quits with this message:

error: uncaptured python exception, closing channel
<__main__.BayesProxyListener listening :1110 at 0x83620d4>
(exceptions.IOError:[Errno 5] Input/output error
[/usr/lib/python2.2/asyncore.py|poll|100]
[/usr/lib/python2.2/asyncore.py|handle_read_event|391]
[/usr/lib/python2.2/site-packages/spambayes/Dibbler.
py|handle_accept|280] [/usr/bin/sb_server.py|__init__|341] 
[/usr/bin/sb_server.py|__init__|183] [/usr/bin/sb_server.
py|__init__|142])
error: uncaptured python exception, closing channel <__main__.
BayesProxy
connected 127.0.0.1:42864 at 0x841acac>
(exceptions.AttributeError:'_socket.socket' object has no attribute
'isClosed' [/usr/lib/python2.2/asyncore.py|poll|113]
[/usr/lib/python2.2/asyncore.py|handle_write_event|404]
[/usr/lib/python2.2/asynchat.py|handle_write|146]
[/usr/lib/python2.2/asynchat.py|initiate_send|208]
[/usr/lib/python2.2/asynchat.py|refill_buffer|189]
[/usr/bin/sb_server.py|close|372]
[/usr/lib/python2.2/asyncore.py|__getattr__|372])

----------------------------------------------------------------------

>Comment By: Tony Meyer (anadelonbrin)
Date: 2004-11-03 17:12

Message:
Logged In: YES 
user_id=552329

I believe this happens when the socket is unexpectedly
closed (at least that is when I see this sort of traceback).

I suspect that the cure here is handling such an event better.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=498103&aid=966487&group_id=61702