Page 1 of 1

[0.7.0b5] traceback after downloader timeout?

Posted: May 14th, 2012, 9:25 am
by jcfp
With todays downloads, there were some timeouts during downloading, probably as a result of issue with my isp. This caused the following traceback to show up a couple of times:
Exception in thread Thread-3:
Traceback (most recent call last):
File "/usr/lib/python2.7/threading.py", line 552, in __bootstrap_inner
self.run()
File "/usr/share/sabnzbdplus/sabnzbd/downloader.py", line 308, in run
if nw.nntp.error_msg or (nw.timeout and time.time() > nw.timeout):
AttributeError: 'NoneType' object has no attribute 'error_msg'
Everything seemed to continue normally otherwise.

Re: [0.7.0b5] traceback after downloader timeout?

Posted: May 14th, 2012, 2:28 pm
by shypike
Hmmm, sloppy programming.
Or the result of a race condition. I'll look into it.
The exception itself is easy to work around.
Was this an "optional" server?

Re: [0.7.0b5] traceback after downloader timeout?

Posted: May 14th, 2012, 3:26 pm
by jcfp
shypike wrote:Was this an "optional" server?
Yes, must have been since all servers are set optional in my install.

Re: [0.7.0b5] traceback after downloader timeout?

Posted: May 15th, 2012, 5:06 am
by shypike
For optional I now have a hunch about what can go wrong, only so far I haven't been able to reproduce the scenario.
I will fix the crashing code anyway.

Re: [0.7.0b5] traceback after downloader timeout?

Posted: May 15th, 2012, 8:07 am
by jcfp
Probably not easy to reproduce indeed. Some background info: turns out my provider thought I had been uploading "excessive" amounts of data, and figured it would be a good "punishment" to limit my upstream to 128 kbit/s (down from 100 mbit/s). That resulted in a sab install setup for high speed downloading now being insanely cut off by limited upload bandwidth, and even then this traceback happened only a few times after hours of downloading.