Page 1 of 1
Backup Server not working since update to 0.7.12
Posted: May 30th, 2013, 2:36 am
by stillhopeful
Hi,
I am on a Mac (10.8.3) and cannot get my backup server to automatically step in when the downloads are out of the primary server's retention. If the download in question is beyond the primary server's retention then it just stalls. However, I can get the stalled downloads to start up again if I disable my primary server. I did not face this problem prior to the 0.7.12 update. Any help would be appreciated. Thanks.
Re: Backup Server not working since update to 0.7.12
Posted: May 30th, 2013, 10:55 am
by shypike
Which version were you coming from?
Not from 0.7.11 I think.
Re: Backup Server not working since update to 0.7.12
Posted: May 30th, 2013, 12:18 pm
by stillhopeful
I was on 0.7.11.
Re: Backup Server not working since update to 0.7.12
Posted: May 30th, 2013, 3:18 pm
by shypike
I'm not claiming there's no problem, but it hasn't been introduced by 0.7.12.
At least I see no way it can be.
The quickest check is to re-install 0.7.11, just install it right over 0.7.12, no issue with that.
It does look like your backup server isn't being nice and not admitting that it misses articles.
What's you "Retry" setting in Config->Switches?
And what is the server timeout in Config->Servers?
Re: Backup Server not working since update to 0.7.12
Posted: May 31st, 2013, 12:12 am
by stillhopeful
Here are the settings you asked for:
Retry in Config->Switches
Maximum retries: 3
Everything else is unchecked except for "Disconnect on Empty Queue"
The server timeout in Config->Servers is 120 seconds for all three servers including the primary, backup and a usually disabled server that I use rarely.
Thanks for looking into this and for providing and maintaining such a stellar product :-)
Re: Backup Server not working since update to 0.7.12
Posted: May 31st, 2013, 2:08 am
by shypike
3 * 120 seconds, means that for each missing article (assuming the server doesn't answer) it takes
SABnzbd 6 minutes to find out.
Reducing the timeout to a more usual value, like 45, will help a bit.
The basic problem still seems to be the server.
Personally I see this kind of behavior often when I enable Astraweb.
Of course, it could also be a problem in SABnzbd, but so far I don't have strong clues for that.