[spambayes-bugs] [ spambayes-Support Requests-1181166 ]
SpamBayesService#.log fills up entire disk
SourceForge.net
noreply at sourceforge.net
Tue Apr 12 03:18:54 CEST 2005
Support Requests item #1181166, was opened at 2005-04-12 13:00
Message generated for change (Comment added) made by anadelonbrin
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=498104&aid=1181166&group_id=61702
Category: None
Group: None
>Status: Closed
Priority: 5
Submitted By: xvs (xvs)
>Assigned to: Tony Meyer (anadelonbrin)
Summary: SpamBayesService#.log fills up entire disk
Initial Comment:
Spambayes Version 1.0.3:
SpamBayesService#.log fills up the entire disk with
lines saying "warning: unhandled exception"
This may or may not be related to times when it cannot
connect to the mail server, because I also sometimes
see messages like:
Can't connect to pop.myserver.com110: (11001,
'getaddrinfo failed')
I also see some of these:
Traceback (most recent call last):
File "sb_server.pyc", line 513, in onRetr
File "spambayes\FileCorpus.pyc", line 137, in addMessage
File "spambayes\FileCorpus.pyc", line 244, in store
IOError: [Errno 28] No space left on device
error: uncaptured python exception, closing channel
<spambayes.Dibbler._HTTPHandler connected at 0x105d3c8>
(socket.error:(10053, 'Software caused connection
abort') [asynchat.pyc|initiate_send|219]
[asyncore.pyc|send|332])
error: uncaptured python exception, closing channel
<spambayes.Dibbler._HTTPHandler connected at 0x105d3c8>
(socket.error:(9, 'Bad file descriptor')
[asynchat.pyc|initiate_send|219]
[asyncore.pyc|send|332] [socket.pyc|_dummy|144])
And another unrelated point: when trying to Train I
sometimes get a crash and traceback such as:
500 Server error
Traceback (most recent call last):
File "spambayes\Dibbler.pyc", line 470, in
found_terminator
File "spambayes\ProxyUI.pyc", line 396, in onReview
File "spambayes\Corpus.pyc", line 214, in takeMessage
File "spambayes\FileCorpus.pyc", line 140, in addMessage
File "spambayes\Corpus.pyc", line 134, in addMessage
File "spambayes\storage.pyc", line 617, in onAddMessage
File "spambayes\storage.pyc", line 625, in train
File "spambayes\classifier.pyc", line 273, in learn
File "spambayes\classifier.pyc", line 374, in _add_msg
File "sets.pyc", line 429, in __init__
File "sets.pyc", line 383, in _update
File "spambayes\classifier.pyc", line 794, in
_add_slurped
File "spambayes\classifier.pyc", line 559, in
_generate_slurp
File "spambayes\classifier.pyc", line 717, in slurp
File "urllib2.pyc", line 130, in urlopen
File "urllib2.pyc", line 358, in open
File "urllib2.pyc", line 376, in _open
File "urllib2.pyc", line 337, in _call_chain
File "urllib2.pyc", line 1021, in http_open
File "urllib2.pyc", line 980, in do_open
File "httplib.pyc", line 582, in __init__
File "httplib.pyc", line 594, in _set_hostport
InvalidURL: nonnumeric port: ''
Retrying the training sometimes then works.
----------------------------------------------------------------------
>Comment By: Tony Meyer (anadelonbrin)
Date: 2005-04-12 13:18
Message:
Logged In: YES
user_id=552329
The problem with the log file filling up is fixed in 1.0.4
(and yes, it is when you cannot connect to the mail server).
Please upgrade to that.
The problem when training (the nonnumeric port one) is
unrelated and is probably a bug with the slurping
experimental options. If you could open a new report with a
message attached that causes the problem next time it
happens, that would be great.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=498104&aid=1181166&group_id=61702
More information about the Spambayes-bugs
mailing list