[Spambayes] 'Connection timed out' problems

Richie Hindle richie at entrian.com
Thu Oct 16 18:24:51 EDT 2003


[Martin]
> The one problem I've had, 
> about three times now, has been on a timeout to my ISP's pop server.
> [...]
> error: uncaptured python exception, closing channel 
> <__main__.ServerLineReader connected at 0x418079ac> (socket.error:(110, 
> 'Connection timed out') [/usr/lib/python2.3/asynchat.py|handle_read|88] 
> [/usr/lib/python2.3/asyncore.py|recv|353])
> Traceback (most recent call last):
>   File "/usr/bin/sb_server.py", line 829, in ?
>     run()
> [...]
>   File "/usr/lib/python2.3/asyncore.py", line 108, in poll
>     r, w, e = select.select(r, w, e, timeout)

That's a strange traceback - the initial exception message reports the
location of the exception as "asyncore.py|recv|353" (ie. line 353 of
asyncore.py in the function 'recv') but the last line of the traceback
points to line 108, in the function 'poll'.  Sorry to ask what is probably
a dumb question, but are you sure that's the entire traceback?  And were
those two sections (the "asyncore.py|recv|353" message and the traceback)
printed at the same time?

-- 
Richie Hindle
richie at entrian.com




More information about the Spambayes mailing list