Hi All,
I've been running a Synology + Sab + sickbeard + Astra setup for many years and couldn't be happier.
Of late I've been getting an increasing number of errors:
'No details available for recoverable file number 1'
'Download might fail, only x% of required'
'unpacking failed, see log'
'file out of server retention'
1 in about 5 downloads now fail, if I retry they usually fail again, if I use sick to snatch them again they usually work.
Any ideas where I might start my troubleshooting?
Sab version 0.7.19
SB version: Alpha (Master) -- source:
Python version: 2.7.6 (default, may 27 2014) (GCC 4.3.2)
Note: I'll upgrade to the latest versions of these tonight.
Sab + Synology
Forum rules
Help us help you:
Help us help you:
- Are you using the latest stable version of SABnzbd? Downloads page.
- Tell us what system you run SABnzbd on.
- Adhere to the forum rules.
- Do you experience problems during downloading?
Check your connection in Status and Interface settings window.
Use Test Server in Config > Servers.
We will probably ask you to do a test using only basic settings. - Do you experience problems during repair or unpacking?
Enable +Debug logging in the Status and Interface settings window and share the relevant parts of the log here using [ code ] sections.
Re: Sab + Synology
Define "snatch them again".fuzzy_logik wrote: if I use sick to snatch them again they usually work.
Do you let SickBeard get the very same NZB again or an alternative one?
SickBeard happens to be specialized in finding alternatives, something SABnzbd is not.
-
fuzzy_logik
- Newbie

- Posts: 2
- Joined: October 30th, 2015, 3:23 am
Re: Sab + Synology
Hi Shypike, I go into sick and just click 'wanted' again. Puts them back in the queue (not sure if it's from an alternative source).
Re: Sab + Synology
Not enough info to say much about this.
Generally there are two causes:
NZB too young: the post hasn't arrived on your Usenet provider. Then a later try will work.
NZB obsolete: the post has been removed from your provider, in which case an alternative NZB (post) may work.
Generally there are two causes:
NZB too young: the post hasn't arrived on your Usenet provider. Then a later try will work.
NZB obsolete: the post has been removed from your provider, in which case an alternative NZB (post) may work.
