SABnzbd Forums

I've followed a few docs and got SAB to install and tron on my pi. Everything seems to run ok but now I'm finding problems with the pi connecting to my news server. From the server config the test fails. I can ping the server and the credentials are correct.

2012-09-08 01:21:18,067::INFO::[downloader:375] [email protected]:119: Initiating connection
2012-09-08 01:21:18,067::INFO::[downloader:375] [email protected]:119: Initiating connection
2012-09-08 01:22:18,122::INFO::[newswrapper:223] Failed to connect: (110, 'timed out') [email protected]:119
2012-09-08 01:22:18,122::INFO::[newswrapper:223] Failed to connect: (110, 'timed out') [email protected]:119

I've seen it connect a few times but mostly it can't connect or is slow. Its working fine from another server.

Is this a limitation of the pi - has anyone managed to get it working with decent download speeds?

I have SAB running on my Raspi: SAB downloads at 30 kBps, and/but also get the timed-out-errors.

With its 256MB RAM and it's 700 Mhz ARM CPU, the Raspi is too low-specced for useful, reliable usage.

You could try NZBget or NNTPgrab on your Raspi; they need less resources.

Thanks for the info

Ok - problem sorted.

I think there was 2 issues.
1) I had some weird permissions on the incomplete folder - I fixed them up and it seemed to help.
2) The biggest problem is using a low quality microusb cable. This caused the voltage to be about 4.2V which caused the network to keep dropping. I changed it out to decent cable and now get 4.9V - no more network drops and it runs at full speed. (With SickBeard running in memory as well)

Any tips on stabilising SAB on the Pi? I have successfully downloaded a 123MB file and a 2GB file, however anything larger seems to crash the Pi.

bigdavethehorn wrote:Any tips on stabilising SAB on the Pi? I have successfully downloaded a 123MB file and a 2GB file, however anything larger seems to crash the Pi.

What kind of crash? What's the verbose output of SAB?

And: what does your "free -m" show during the download?

I'm not sure what kind of crash unfortunately, I run SAB on a schedule from midnight until 08:00. When I attempt to view the queue in the morning, I can't access SAB remotely (via http), or the Pi direct via VNC, SSH or keyboard.

The solution appears to be switch it off and on

I'm running Debian Wheezy and SAB, that's about it. I haven't yet adjusted the "8192 kbytes" setting in Wheezy, is it worth a shot?

Ok, I increased the vmin setting from 8192 to 16384 and added smsc95xx.turbo_mode=N in /boot/cmdline.txt

I think it worked, maybe to early to tell just yet, but I managed a couple of large downloads (3GB & 10GB) and the Pi was still responsive in the morning.