SABnzbd causing system slowness & hanging

[jaysel]

I am a long time user of SABnzbd, but recently noticed that my MediaServer was struggling with it, and it has caused the system to hang on a number of occasions.
My server runs a Quad Core Q6600 with 4Gb of RAM, so is powerful enough.
I have run malware checks, anti-virus, memory & cpu tests - all of which come up fine.
After a reboot, SAB works fine for a few hours, then everything starts to slow down. If I don't have SAB running - I do not get the issue.
Plex menus run really slow - but once a movie is playing, all is fine
I do notice a lot of disk activity going on at time - yet nothing appears to be downloading.

I have MS Security Essentials running - so there should not be any issues there.

Does anyone know what I can do to check, or to narrow down what is causing the issue ?
It may not be SAB - but its looking that way

[shypike]

Sufficient hardware indeed.
Did you set an article cache (set to 2M)?
Can you check which process uses a lot of CPU?
Keep in mind that on Windows any process can hog the disk channel,
resulting in a slow down of the system.
Par2 and unrar are quite capable of this.
(So is SABnzbd without an article cache.)

[jaysel]

Thanks Shypike.
Yes Article Cache is set for 200M.
Before going mad with debugging, I'm going to do a fresh install of Sab. It's probably something silly, that's causing the issue. It's been fine for the last 4-5 years. Lol
I'll let you know

[jaysel]

Hi Shypike,
Looks like the issue has resolved itself after a reinstall.
However, I now have another issue.
After the install, I copied the ini file over.
However, I do not seem to get any history, even though the movies have downloaded.
I have checked the logs, and found these errors, that maybe poignant:

08-30 12:08:06INFO[hpotato.core.plugins.base] Opening url: get http://jaysel.dyndns.org:8080/api?outpu ... mode=queue, data: []
08-30 12:08:27ERROR[.core.downloaders.sabnzbd] Failed getting queue: Traceback (most recent call last):
File "C:\Users\jay\AppData\Roaming\CouchPotato\application\appdata\CouchPotato-2.5.2.win32\couchpotato\core\downloaders\sabnzbd.py", line 98, in getAllDownloadStatus
ConnectionError: HTTPConnectionPool(host='jaysel.dyndns.org', port=8080): Max retries exceeded with url: /api?output=json&apikey=xxx&mode=queue (Caused by <class 'socket.error'>: [Errno 10060] A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond)
08-30 12:08:27ERROR[tato.core.plugins.renamer] Both the "To" and "From" folder have to exist.

[jaysel]

Sorry - ignore the above - its a CP log

[mcdaddie]

I too am having a problem with SAB. For the last 3 years my average download speed was about 3 MB/S. My ISP improved my download speed from 35 MB to 100 MB recently. At that time my average SAB download speed was about 12 MB/s. However the last few days my SAB speed has dropped to about 1 MB/s. I rechecked my internet speed from ISP and still around 100 MB/s. I have made NO changes to my system. Are there any ideas on what might have happened. Thx

[mcdaddie]

After looking back at history and readying other forums, I feel the slowness came about at the last upgrade earlier this month.

[shypike]

Which exact upgrade caused it?
There haven't been changes to the basic download part for quite some time.

[mcdaddie]

It may be an ISP problem. I just read another post that a Time Warner user is having the same problem in a different part of the country.

[jaysel]

Hi Shypike
I resolved my problem. After the reinstall of SABnzbd, all ran ok. Not sure what the problem was, but I fear something became corrupted. I noticed from the System Event logs that the server had been up & down like a whores drawers the night before, due to a power cut. I think this somehow got SABnzbd a bit confused.

The second issue I had was user error!
I inadvertently changed a setting that caused SABnzbd to not keep the history. DOH!
Thanks for the speedy reply - as always

[shypike]

Good that it works again.