I ran into a thing yesterday where right up to the very last second the download seemed to be going swimmingly (the release was maybe three years old), and indeed all the files and the par2 volumes seemed to be there later in the "incomplete" folder, but there seemed no way to repair the download. "Retry" with the original .nzb did nothing either.
Now these file names were crazy long. Could that have something to do with why unpacking/repair failed?
Thanks for any enlightenment.
Is it possible for extra-long filenames of a release to cause extraction/repair to "choke"?
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: Is it possible for extra-long filenames of a release to cause extraction/repair to "choke"?
Yes, maybe / possibly.
SABnzbd has counter measures: SAB will shorten a name to that it all works well. But maybe you've found another edge case. So share logging and the .NZB.
SABnzbd has counter measures: SAB will shorten a name to that it all works well. But maybe you've found another edge case. So share logging and the .NZB.
Re: Is it possible for extra-long filenames of a release to cause extraction/repair to "choke"?
It really depends which platform you are on. Windows? Linux?
Where is the storage?
Where is the storage?
If you like our support, check our special newsserver deal or donate at: https://sabnzbd.org/donate