Version: 0.6.5
OS: Synology DSM 3.1
Install-type: souce
Are you using IPV6? no
Is the issue reproducible? no
Hi,
I have a problem with the latest version of SABNzbd concerning the extracting. The problem does not occur with all downloads (hard to reproduce) but even though the download has been completed successfully (no missing articles), SABNzbd fails to extract it. It just indicates as "failed" without further remarks of comments...
I can extract it via the command line using unrar without problems.
Any suggestions ? I didn't seem to be having the same problem with previous versions of SABNzbd
I'm using python 2.5 at the moment
Regards
Extracting fails even when the files are ok
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.
-
DirtyWizard
- Newbie

- Posts: 8
- Joined: June 30th, 2011, 7:09 am
Re: Extracting fails even when the files are ok
You'll need to set logging level to "Debug"
and examine the logs right after such a problem occurs.
Look for the unrar command end check for error messages in its vicinity.
and examine the logs right after such a problem occurs.
Look for the unrar command end check for error messages in its vicinity.
-
DirtyWizard
- Newbie

- Posts: 8
- Joined: June 30th, 2011, 7:09 am
Re: Extracting fails even when the files are ok
Thanks,
Here are the logs (I've replaced names and paths)
2011-06-30 13:55:46,713::INFO::[__init__:817] /$$PATH$$/__ADMIN__/SABnzbd_nzo__Kvca4 removed
2011-06-30 13:55:46,714::INFO::[nzbqueue:167] Saving queue
2011-06-30 13:55:46,715::INFO::[__init__:828] Saving data for queue9.sab in /volume1/@appstore/SABnzbd/admin/queue9.sab
2011-06-30 13:55:46,744::INFO::[postproc:83] Saving postproc queue
2011-06-30 13:55:46,746::INFO::[__init__:828] Saving data for postproc1.sab in /volume1/@appstore/SABnzbd/admin/postproc1.sab
2011-06-30 13:55:46,754::INFO::[postproc:235] Starting PostProcessing on $$HIDDEN$$ => Repair:True, Unpack:True, Delete:True, Script:None, Cat:movies
2011-06-30 13:55:46,755::INFO::[postproc:475] Par2 check starting on $$HIDDEN$$
2011-06-30 13:55:46,756::INFO::[postproc:490] Running repair on set $$HIDDEN$$
2011-06-30 13:55:46,770::INFO::[newsunpack:766] Scanning "$$PATH$$/$$HIDDEN$$.vol000+02.par2"
2011-06-30 13:56:22,996::INFO::[newsunpack:948] Main packet not found...
2011-06-30 13:56:22,997::INFO::[newsunpack:952] []
2011-06-30 13:56:23,050::INFO::[newsunpack:781] Par verify failed on $$PATH$$/$$HIDDEN$$.vol000+02.par2!
2011-06-30 13:56:23,051::INFO::[postproc:505] Par2 check finished on $$HIDDEN$$
2011-06-30 13:56:32,012::INFO::[emailer:123] Notification e-mail succesfully sent
2011-06-30 13:56:32,016::INFO::[postproc:603] Removing unwanted file $$PATH$$/$$HIDDEN$$.sfv
2011-06-30 13:56:32,269::INFO::[postproc:448] Cleaning up $$HIDDEN$$ (keep_basic=True)
2011-06-30 13:56:32,284::INFO::[postproc:83] Saving postproc queue
2011-06-30 13:56:32,285::INFO::[__init__:828] Saving data for postproc1.sab in /volume1/@appstore/SABnzbd/admin/postproc1.sab
2011-06-30 13:56:32,288::INFO::[downloader:229] Post-processing finished, resuming download
In my opinion, it is probably the [newsunpack:952] [] that makes it fail..
Or was it a faulty NZB ?
Here are the logs (I've replaced names and paths)
2011-06-30 13:55:46,713::INFO::[__init__:817] /$$PATH$$/__ADMIN__/SABnzbd_nzo__Kvca4 removed
2011-06-30 13:55:46,714::INFO::[nzbqueue:167] Saving queue
2011-06-30 13:55:46,715::INFO::[__init__:828] Saving data for queue9.sab in /volume1/@appstore/SABnzbd/admin/queue9.sab
2011-06-30 13:55:46,744::INFO::[postproc:83] Saving postproc queue
2011-06-30 13:55:46,746::INFO::[__init__:828] Saving data for postproc1.sab in /volume1/@appstore/SABnzbd/admin/postproc1.sab
2011-06-30 13:55:46,754::INFO::[postproc:235] Starting PostProcessing on $$HIDDEN$$ => Repair:True, Unpack:True, Delete:True, Script:None, Cat:movies
2011-06-30 13:55:46,755::INFO::[postproc:475] Par2 check starting on $$HIDDEN$$
2011-06-30 13:55:46,756::INFO::[postproc:490] Running repair on set $$HIDDEN$$
2011-06-30 13:55:46,770::INFO::[newsunpack:766] Scanning "$$PATH$$/$$HIDDEN$$.vol000+02.par2"
2011-06-30 13:56:22,996::INFO::[newsunpack:948] Main packet not found...
2011-06-30 13:56:22,997::INFO::[newsunpack:952] []
2011-06-30 13:56:23,050::INFO::[newsunpack:781] Par verify failed on $$PATH$$/$$HIDDEN$$.vol000+02.par2!
2011-06-30 13:56:23,051::INFO::[postproc:505] Par2 check finished on $$HIDDEN$$
2011-06-30 13:56:32,012::INFO::[emailer:123] Notification e-mail succesfully sent
2011-06-30 13:56:32,016::INFO::[postproc:603] Removing unwanted file $$PATH$$/$$HIDDEN$$.sfv
2011-06-30 13:56:32,269::INFO::[postproc:448] Cleaning up $$HIDDEN$$ (keep_basic=True)
2011-06-30 13:56:32,284::INFO::[postproc:83] Saving postproc queue
2011-06-30 13:56:32,285::INFO::[__init__:828] Saving data for postproc1.sab in /volume1/@appstore/SABnzbd/admin/postproc1.sab
2011-06-30 13:56:32,288::INFO::[downloader:229] Post-processing finished, resuming download
In my opinion, it is probably the [newsunpack:952] [] that makes it fail..
Or was it a faulty NZB ?
Re: Extracting fails even when the files are ok
The tell-tale line is 948: "Main packet not found".
This is based on output coming from the par2 program.
It means that the par2 program cannot find usable info in the par2 file it was offered by SABnzbd.
The next line means that no extra par2 files are available.
Can you email the uncensored logging and the NZB file to bugs at sabnzbd.org ?
(please add the URL of this message).
This is based on output coming from the par2 program.
It means that the par2 program cannot find usable info in the par2 file it was offered by SABnzbd.
The next line means that no extra par2 files are available.
Can you email the uncensored logging and the NZB file to bugs at sabnzbd.org ?
(please add the URL of this message).
-
DirtyWizard
- Newbie

- Posts: 8
- Joined: June 30th, 2011, 7:09 am
Re: Extracting fails even when the files are ok
The upload sucks.
The par2 files are simply useless.
You were just lucky that all RAR segments downloaded without errors,
otherwise unrar would have stopped on a CRC error.
The only thing I can do is improve the error message (because currently there is none).
This is the output of a par2.exe run from a command prompt:
The par2 files are simply useless.
You were just lucky that all RAR segments downloaded without errors,
otherwise unrar would have stopped on a CRC error.
The only thing I can do is improve the error message (because currently there is none).
This is the output of a par2.exe run from a command prompt:
Code: Select all
Loading "jobname.par2".
No new packets found
Loading "jobname.vol000+02.par2".
Loading "jobname.vol002+04.par2".
No new packets found
Loading "jobname.vol006+08.par2".
No new packets found
Loading "jobname.vol014+16.par2".
No new packets found
Loading "jobname.vol030+32.par2".
No new packets found
Loading "jobname.vol062+64.par2".
No new packets found
Loading "jobname.vol126+72.par2".
No new packets found
No new packets found
Loading "jobname.par2".
No new packets found
Loading "jobname.vol000+02.par2".
No new packets found
Loading "jobname.vol002+04.par2".
No new packets found
Loading "jobname.vol006+08.par2".
No new packets found
Loading "jobname.vol014+16.par2".
No new packets found
Loading "jobname.vol030+32.par2".
No new packets found
Loading "jobname.vol062+64.par2".
No new packets found
Loading "jobname.vol126+72.par2".
No new packets found
Main packet not found.
-
DirtyWizard
- Newbie

- Posts: 8
- Joined: June 30th, 2011, 7:09 am
Re: Extracting fails even when the files are ok
Oke, thank you very much for the quick debugging !
Regards
Regards
-
DirtyWizard
- Newbie

- Posts: 8
- Joined: June 30th, 2011, 7:09 am
Re: Extracting fails even when the files are ok
I was just thinking (I have totally no clue whether this is possible or not with NZB downloads).. maybe you can add one phase after a failed PAR2 verification to use the SFV (in available) to verify the correctness of the files. If this latter succeeds, you can proceed with the extraction or am I missing something here ?
Re: Extracting fails even when the files are ok
SFV checking is already an option and will be used if no par2 files are available at all.
I'm not going to spend a lot of effort to handle very exceptional cases like this.
I'm not going to spend a lot of effort to handle very exceptional cases like this.
-
DirtyWizard
- Newbie

- Posts: 8
- Joined: June 30th, 2011, 7:09 am
Re: Extracting fails even when the files are ok
Oke, thanks for the help already
