Not trying to repair with PAR anymore
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: Not trying to repair with PAR anymore
Are there more lines after that last one you posted about par2_repair?
Maybe 10 more?
Maybe 10 more?
If you like our support, check our special newsserver deal or donate at: https://sabnzbd.org/donate
-
- Newbie
- Posts: 47
- Joined: April 24th, 2017, 8:51 am
Re: Not trying to repair with PAR anymore
Hey, the notification is working now
okay, here are a few more lines after the last ones that I posted:
2017-04-26 19:34:24,765::DEBUG::[notifier:112] Sending registration to localhost:23053
2017-04-26 19:34:24,780::DEBUG::[notifier:102] Checking icon
2017-04-26 19:34:24,780::DEBUG::[notifier:219] To : localhost:23053 <<class 'gntp.GNTPRegister'>>
2017-04-26 19:34:25,280::DEBUG::[misc:1270] Read these passwords from file: ['ghost-of-usenet', 'Usenetrevolution.info', 'DANKEwww.town.ag', 'UsenetRevolution', 'SerieN_@_www.town.ag', 'usenet-4all.info', 'Kotzmeister', '<HASH>069ee58', '<HASH>04c0046', '<HASH>1de7b75', '<HASH>293cc16', '<HASH>e9aeae2', '<HASH>9fe4b6b', '<HASH>e137244', '<HASH>0beca63', '<HASH>b83f801', '<HASH>1d27e18', '<HASH>9357678', '<HASH>2968121', '<HASH>2858cb1', '<HASH>bef0365', '<HASH>8b65fbc', '<HASH>39f1e77']
2017-04-26 19:34:25,280::INFO::[misc:1273] Read 23 passwords from file G:\Usenet\Downloads\Passwords\Passwords.txt
2017-04-26 19:34:25,280::INFO::[postproc:583] Cleaning up Prince-Rome-20Ten (keep_basic=True)
2017-04-26 19:34:25,296::INFO::[postproc:87] Saving postproc queue
2017-04-26 19:34:25,296::INFO::[__init__:971] Saving data for postproc2.sab in E:\Dokumente\admin\postproc2.sab
2017-04-26 19:34:25,296::INFO::[downloader:300] Post-processing finished, resuming download
2017-04-26 19:34:25,608::INFO::[downloader:789] Thread [email protected]: forcing disconnect
2017-04-26 19:34:25,717::INFO::[downloader:789] Thread [email protected]: forcing disconnect
There are many pages more if you need them
As SAB isn´t even trying to repair the files, could it be possible, that it just doesn´t know the path to quickpar, that it has forgotten it when I was installing version 2.0 over the old version? So maybe there is a way that I can select the right path or flip a switch? But please remember, that I have the same problem on my Synology NAS and I am not really experienced with Linux...
okay, here are a few more lines after the last ones that I posted:
2017-04-26 19:34:24,765::DEBUG::[notifier:112] Sending registration to localhost:23053
2017-04-26 19:34:24,780::DEBUG::[notifier:102] Checking icon
2017-04-26 19:34:24,780::DEBUG::[notifier:219] To : localhost:23053 <<class 'gntp.GNTPRegister'>>
2017-04-26 19:34:25,280::DEBUG::[misc:1270] Read these passwords from file: ['ghost-of-usenet', 'Usenetrevolution.info', 'DANKEwww.town.ag', 'UsenetRevolution', 'SerieN_@_www.town.ag', 'usenet-4all.info', 'Kotzmeister', '<HASH>069ee58', '<HASH>04c0046', '<HASH>1de7b75', '<HASH>293cc16', '<HASH>e9aeae2', '<HASH>9fe4b6b', '<HASH>e137244', '<HASH>0beca63', '<HASH>b83f801', '<HASH>1d27e18', '<HASH>9357678', '<HASH>2968121', '<HASH>2858cb1', '<HASH>bef0365', '<HASH>8b65fbc', '<HASH>39f1e77']
2017-04-26 19:34:25,280::INFO::[misc:1273] Read 23 passwords from file G:\Usenet\Downloads\Passwords\Passwords.txt
2017-04-26 19:34:25,280::INFO::[postproc:583] Cleaning up Prince-Rome-20Ten (keep_basic=True)
2017-04-26 19:34:25,296::INFO::[postproc:87] Saving postproc queue
2017-04-26 19:34:25,296::INFO::[__init__:971] Saving data for postproc2.sab in E:\Dokumente\admin\postproc2.sab
2017-04-26 19:34:25,296::INFO::[downloader:300] Post-processing finished, resuming download
2017-04-26 19:34:25,608::INFO::[downloader:789] Thread [email protected]: forcing disconnect
2017-04-26 19:34:25,717::INFO::[downloader:789] Thread [email protected]: forcing disconnect
There are many pages more if you need them
As SAB isn´t even trying to repair the files, could it be possible, that it just doesn´t know the path to quickpar, that it has forgotten it when I was installing version 2.0 over the old version? So maybe there is a way that I can select the right path or flip a switch? But please remember, that I have the same problem on my Synology NAS and I am not really experienced with Linux...
Re: Not trying to repair with PAR anymore
Could jou maybe send one of the failing NZBs to [email protected]?
If you like our support, check our special newsserver deal or donate at: https://sabnzbd.org/donate
-
- Newbie
- Posts: 47
- Joined: April 24th, 2017, 8:51 am
Re: Not trying to repair with PAR anymore
Yes of course. Mail is done.
-
- Newbie
- Posts: 47
- Joined: April 24th, 2017, 8:51 am
Re: Not trying to repair with PAR anymore
Did you receive my email with the nzb yesterday?
Re: Not trying to repair with PAR anymore
Safihre's answers can take some time at the moment because of his other activities.desperado591 wrote:Did you receive my email with the nzb yesterday?
-
- Newbie
- Posts: 47
- Joined: April 24th, 2017, 8:51 am
Re: Not trying to repair with PAR anymore
ok no problem. I am thankfull for all help and did not want to urge somebody
-
- Newbie
- Posts: 47
- Joined: April 24th, 2017, 8:51 am
Re: Not trying to repair with PAR anymore
Anything new about that topic?
Re: Not trying to repair with PAR anymore
Wait until May 18, please ... the Main Man will be back online by then.desperado591 wrote:Anything new about that topic?
Re: Not trying to repair with PAR anymore
Almost back online! I have the email, but I broke the keyboard of my laptop, fixing that now to get back to coding.
If you like our support, check our special newsserver deal or donate at: https://sabnzbd.org/donate
-
- Newbie
- Posts: 47
- Joined: April 24th, 2017, 8:51 am
Re: Not trying to repair with PAR anymore
Okay, don´t hurry and take your time :-)
Re: Not trying to repair with PAR anymore
Oke I tried the NZB in multiple ways, but cannot seem to get it to fail.
Could you turn on Debug logging, download it again and then send me the whole log via email?
Could you turn on Debug logging, download it again and then send me the whole log via email?
If you like our support, check our special newsserver deal or donate at: https://sabnzbd.org/donate
-
- Newbie
- Posts: 47
- Joined: April 24th, 2017, 8:51 am
Re: Not trying to repair with PAR anymore
As requested I have sent you the logfile via email.
Meanwhile my SAB on the Synology NAS is working again as it should, after I have updated from DSM 5 to DSM 6 today. I tried to download the example nzb that I sent you already via email and it repaired it as in the good old days.
So now it is only my Windows PC that is struggeling (as you can see in the log)
Meanwhile my SAB on the Synology NAS is working again as it should, after I have updated from DSM 5 to DSM 6 today. I tried to download the example nzb that I sent you already via email and it repaired it as in the good old days.
So now it is only my Windows PC that is struggeling (as you can see in the log)
Re: Not trying to repair with PAR anymore
We figured out the problem to be that par2.exe doesn't work on Windows XP, which desperado591 is using.
Fixed by disabling Par2 Multicore, the single core version does work.
Fixed by disabling Par2 Multicore, the single core version does work.
If you like our support, check our special newsserver deal or donate at: https://sabnzbd.org/donate