I've noticed that sometimes a download will be marked as "complete"
but in the summary you'll see:
So when I check the contents it's all:
Any ideas what's going wrong
1.2.0: Repair fails but dload is marked as "complete" anyway
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: 1.2.0: Repair fails but dload is marked as "complete" an
Do you have, Post process only verified jobs turned on in Config Switches?
If you like our support, check our special newsserver deal or donate at: https://sabnzbd.org/donate
Re: 1.2.0: Repair fails but dload is marked as "complete" an
I've tried with and without "Post process only verified jobs" enabled and still run into the issue.
Re: 1.2.0: Repair fails but dload is marked as "complete" an
Could you send me the NZB at [email protected]?
If you like our support, check our special newsserver deal or donate at: https://sabnzbd.org/donate
Re: 1.2.0: Repair fails but dload is marked as "complete" an
The effect is that they just stay in the "complete" folder of Sab and don't get moved by the renamers of others.
It also indicates the the indexer that it's a successful download so it marks it as such too.
It also indicates the the indexer that it's a successful download so it marks it as such too.
Re: 1.2.0: Repair fails but dload is marked as "complete" an
Oke, but I will need the NZB to test what's going on!
If you like our support, check our special newsserver deal or donate at: https://sabnzbd.org/donate
Re: 1.2.0: Repair fails but dload is marked as "complete" an
Problem identified from the logs:
Using a version of par2cmdline newer than 0.6.14 which doesn't work because it won't scan files 'out of basepath'.
Using a version of par2cmdline newer than 0.6.14 which doesn't work because it won't scan files 'out of basepath'.
If you like our support, check our special newsserver deal or donate at: https://sabnzbd.org/donate
Re: 1.2.0: Repair fails but dload is marked as "complete" an
The par2cmdline on the QNAP is 0.6.14. I moved the Downloads folder back into the basepath at SAB_CONFIG/Downloads and the issue still happens.
Re: 1.2.0: Repair fails but dload is marked as "complete" an
Unfortunately par2cmdline is very picky about basepath, not even really sure what it considers basepath.
We really never had problems with 0.6.14, it's shipped with the Linux version of Sab for this reason. Very strange.
But since we want to support future versions of par2cmdline I better just add detection for the -B parameter, not too hard.
Will add it for 1.2.1.
We really never had problems with 0.6.14, it's shipped with the Linux version of Sab for this reason. Very strange.
But since we want to support future versions of par2cmdline I better just add detection for the -B parameter, not too hard.
Will add it for 1.2.1.
If you like our support, check our special newsserver deal or donate at: https://sabnzbd.org/donate
Re: 1.2.0: Repair fails but dload is marked as "complete" an
I sent new logs which I don't believe have the "out of basepath" error (after I moved the Downloads folder back within the package's base path).
From the Entware wiki it looks like it's captured at least 2 releases of par2cmdline.
From March:
par2cmdline 0.6.14-20160327-1
and from June:
par2cmdline 0.6.14-20160630-1
I'm using the one from June at the moment.
With the Downloads folder moved back within the Sab package and the "out of basepath" error is no longer happening do you have any other ideas as to what the issue could be?
Oops! It looks like I still have the "out of basepath" error.
Is there something I can do in the meantime as a workaround?
From the Entware wiki it looks like it's captured at least 2 releases of par2cmdline.
From March:
par2cmdline 0.6.14-20160327-1
and from June:
par2cmdline 0.6.14-20160630-1
I'm using the one from June at the moment.
With the Downloads folder moved back within the Sab package and the "out of basepath" error is no longer happening do you have any other ideas as to what the issue could be?
Oops! It looks like I still have the "out of basepath" error.
Is there something I can do in the meantime as a workaround?
Last edited by nzbjamz on January 22nd, 2017, 11:37 pm, edited 4 times in total.
Re: 1.2.0: Repair fails but dload is marked as "complete" an
Hmm, can you install any version? Maybe 0.6.13?
Because 0.6.14 came out in 2015, so surprised it says any 2016 dates on the wiki.
Could be they use the latest develop version which still is tagged as 0.6.14 since they never released a newer one.
Because 0.6.14 came out in 2015, so surprised it says any 2016 dates on the wiki.
Could be they use the latest develop version which still is tagged as 0.6.14 since they never released a newer one.
If you like our support, check our special newsserver deal or donate at: https://sabnzbd.org/donate
Re: 1.2.0: Repair fails but dload is marked as "complete" an
I'll look into it.Hmm, can you install any version? Maybe 0.6.13?
I bet that's it.Could be they use the latest develop version which still is tagged as 0.6.14 since they never released a newer one.
Update:
I manually applied your patch sabnzbd/commit/216d051 and it has resolved the issue!
Last edited by nzbjamz on January 23rd, 2017, 12:08 am, edited 1 time in total.
Re: 1.2.0: Repair fails but dload is marked as "complete" an
Great!
If you like our support, check our special newsserver deal or donate at: https://sabnzbd.org/donate