SABnzbd Forums

Hi,

For the past few weeks I have been pulling my hair working out why my files are downloading so slow. I haven't used Unison (OS X) for months, however tonight I decided to download a file using that app and I was able to reach my old download speeds of 7.5-8.5MB/s but recently I haven't been able to get anything more than 800KB/s. I have spent countless hours on the phone with my ISP trying to troubleshoot the issue, I even accused them of blocking the port. I've emailed Astrawebs several times checking and double checking any known network outages.

I then decided after using that Unison app that there is nothing wrong with my Internet connection nor Astrawebs, it is infact Sabnzbd. I have now rolled back to version 0.6 and currently downloading at 8.45MB/s.

Please can this be fixed as this is a major problem, and I have done some searches and it appears I wasn't the only one having this problem.

------------------
TLDR: SABnzbd 0.7.1 & 0.7.2 caused downloads to be painfully slow, rolling back to a previous version such as 0.6 fixes the problem and full speed is restored.

I'm experiencing the same thing. At first I thought it was my ISP, but everything else on my server seems to work fine. Both 0.7.1 and 0.7.2 have been very slow to download and have no indication of activity or pause status. I've tried with a couple of different skins too.

Same Usenet provider?

I am having a strange problem, and might be related. When I start sab, it basically hangs until it finishes all housework. During that time it basically uses 100% cpu and does no dling. At first thought the only top and stop dling flags where set, but already checked them.

I tried to look at the logs, but it went wild logging info an hour after starting (have about 20 MB of logs in about an hour) and lost the first hour . Five hours later, it has only done one file (not even 5 MB)

Try setting random_server_ip off in Config->Special.
Restart after that.

shypike
Thanks, that seems to have done it. However, some versions ago, had to pause sab every day. Now it doesn't commence dl after resuming, even three hours later. After restarting sab, the dl worked fine. The last entry in the log is:


2012-08-02 10:18:00,088::INFO::[downloader:208] Resuming
2012-08-02 10:18:00,089::DEBUG::[__init__:516] PAUSED_ALL inactive

That's what you're supposed to see.
I assume you have a scheduled resume?
Does it happen consitently or was it an incident with a specific NZB?
There is a work around, but it should be not be necessary of course, schedule a restart instead of a resume.

Some versions ago, my connection wasn't too reliable and sab had trouble with that. So I programmed a pause at 10:15 and a resume (what you saw) at 10:18.

Just removed the programmed pause, and it finished the queue. Will try to pay attention wether this happens with certain nzbs or after pausing.

Still not sure what is going on

Sab has stopped again. I moved down some of the top items, but hasn't restarted.

The log has the following:


012-08-12 04:07:11,256::DEBUG::[decoder:143] Server has article <Article: article=id@news.astraweb.com, bytes=198697, partnum=38, art_id=None>
2012-08-12 04:07:11,257::DEBUG::[downloader:228] Delaying
2012-08-12 04:07:14,290::DEBUG::[bpsmeter:246] bps: 306.001146167
2012-08-12 04:07:19,491::DEBUG::[bpsmeter:246] bps: 118.964358455
2012-08-12 04:07:24,685::DEBUG::[bpsmeter:246] bps: 46.2968041426
2012-08-12 04:07:29,934::DEBUG::[bpsmeter:246] bps: 17.8535667435
2012-08-12 04:07:35,290::DEBUG::[bpsmeter:246] bps: 6.76765726574
2012-08-12 04:07:40,343::DEBUG::[bpsmeter:246] bps: 2.69571522119
2012-08-12 04:07:45,458::DEBUG::[bpsmeter:246] bps: 1.06290253421
2012-08-12 04:07:50,664::DEBUG::[bpsmeter:246] bps: 0.412832792674
2012-08-12 04:07:55,675::DEBUG::[bpsmeter:246] bps: 0.165614469994
2012-08-12 04:08:00,882::DEBUG::[bpsmeter:246] bps: 0.0643109219904
2012-08-12 04:08:06,060::DEBUG::[bpsmeter:246] bps: 0.0250927587431

After restarting I got:
2012-08-12 05:54:10,933::INFO::[__init__:994] Restarting because of crashed downloader

Which version are you on now?

should be 0.7.2

Then I would need your log file.
The "crashed downloader" will leave debug info in the log.
You should be on 0.7.3 of course.

Don't have the logs anymore. I don't recall anything else, but probably missed what you wanted to see.

However I just switched to 0.7.3. Have the impression that it might had been a group of nzb that caused that. Today it is working at full bw.

Thanks.

ugokanain wrote:Have the impression that it might had been a group of nzb that caused that.

Even so, should you encounter it again, please report again.
Just emailing the NZB is sufficient.
A Downloader crash can only mean a bug, however obscure it may be.