SABnzbd Forums

Thank you for the software. I'm running 0.6.14 under a hosted linux server. I have configured 2 servers, both Astraweb (ssl-eu.astraweb.com and ssl.astraweb.com) and on Port 563. TheTest Server buttons show they are working fine

I have tried 2 different, new (not expired) nzb files and both never seem to start. The first one just stes there, with a rollover status of "Downloading", but nothing ever comes down. The 2nd is waiting. I swapped them, but no change.

Status > Connections lists both Servers, but 0 connections.

The error log only has one minor one (?) about PAR2 binary not found.

Do I need to 'start' the individual downloads somehow? Or connect to the server(s)?

The same nzb files work fine on Windows - on a different Usenet client - with the same Astraweb server and SSL credentials. Puzzling...it's like there's something fundamentally wrong. Thanks.

MIssing par2 is not a minor problem. It means you lose 50% of SABnzbd functionality,
because you cannot verify/repair downloads and no further post-processing will occur.
But this has nothing to do with not downloading at all.
There is an overall pause button. Assuming you are using the default Plush skin,
the pause button is at the top right and it should look like two small yellow vertical bars.
Each item has it's own paused/active state button: they should look like right pointing arrows.
Further: server definitions should have at least 1 connection and they should be "enabled".
Did you enter retention rates? Remove those for now.

Thanks for the quick reply. It was sloppy wording, I meant it was minor in that I thought it wasn't relevant to the main problem...

Anyway, I removed the retention time and it reverted to "0" on both servers.

The first server has a tick beside both Enable and SSL
Second has same with Backup also ticked

Restarted with -c option and added new nzb file. Same result...download won't start

It is meant to autostart when you add the .nzb file or is there another step? I upload the .nzb and it appears in the Queue, but just sits there. I've tried different values under the far right option ("Processing, Download etc") But they don't seem to change things.

Thanks again

Does it work without SSL?
Anything in the scheduler?
Toggling pause/resume?
What's in the last part of the logfile? (Status page).
Which OS is it exactly?
Does the hosted system allow outgoing connections on the requested ports?

shypike wrote:Does it work without SSL?
Anything in the scheduler?
Toggling pause/resume?
What's in the last part of the logfile? (Status page).
Which OS is it exactly?
Does the hosted system allow outgoing connections on the requested ports?

Removed SSL and restarted on server. No change.

Pause/resume; no change

Latest warning: 'ERROR: par2 binary... NOT found!'

Before going on, the hosting company doesn't support sabnzbd but provides these general instructions to start it: Obviously we change the directory name to match, but do these look okay to you?

I notice that taking the option on the web client to Shutdown does NOT kill the Jobs started by the above command. The browser screen message says "SABnzbd-0.6.14 shutdown finished"

Thanks

I would do this:

stop SABnzbd
rename sabnzbd.ini (in ~/.sabnzbd/) to something else
start SABnzbd again; it should start the wizard.
Then fill out only one server: news.astraweb.com, with a plain connection with no SSL and just 1 thread

Then check if you can download a nzb...

sander wrote:I would do this:

...

Thanks, did all of that. Same result; on-mouse-over has green "Status: Downloading" popup. But nothing is really downloading.

Error log has nothing new, just the one about "par2 binary... NOT found!"

Can I ask : do I need to 'connect' to the Usernet server from the web page? It is showing No Connections. It's like something fundamental isn't kicking off.

Tried a 2nd nzb, same result. May see if there's an Linux system logs that are catching something.

Have you looked at SABnzbd's own log? It's under Satus -> Latest Warning -> Logging.

sander wrote:Have you looked at SABnzbd's own log? It's under Satus -> Latest Warning -> Logging.

Yep, have been. Only one flagged as an Error as mentioned above. PAR2-related.