Page 1 of 2
Version 2.2.0
Posted: August 18th, 2017, 9:50 am
by Confused_too
Hi me again :]
Little problem with the updated tool.
I queue the 22 episodes of a certain series. They are in independent nzbs this time.
It downloads fine to the end of the queue except for eps 4 and 11 which stay downloaded but still in the queue. No warnings no errors.
I check the incomplete folder and run the par file by hand.
In the case of ep 4 quickpar says r10 is incomplete and I need 1 more block which I don't have. But when I go to the complete folder, there it is the ep unpacked, right size but wrong crc.
In the case of file 11, it is unpacked right size right crc. I have no idea what's the problem with ep 11.
On the positive side the unpacking of multiple files in the same nzb is going a lot faster now . Thanks!
Re: Version 2.2.0
Posted: August 18th, 2017, 9:52 am
by safihre
Can you check which files are still left for these jobs? By clicking on the folder-icon when you hover over the job.
Do they continue when you pause and unpause the separate download?
How many servers do you have?
What OS are you on?
Re: Version 2.2.0
Posted: August 18th, 2017, 10:02 am
by Confused_too
That was fast
K I checked and it hadn't downloaded any of the par files except the small one.
I paused and unpaused and that did the trick. All the files are now unpacked and fine.
I have 2 servers but it didn't need to use the second one.
Windows 10
Re: Version 2.2.0
Posted: August 18th, 2017, 10:06 am
by safihre
Yeah we have 2.2.0 just out so want to be on top of things, especially since other users report this problem too.
Are you on macOS or Windows by any chance?
Re: Version 2.2.0
Posted: August 18th, 2017, 10:07 am
by safihre
Alright, could you instead install this version:
https://github.com/sabnzbd/sabbuild/rel ... ti-stall-1
It has implemented an anti-stall method, which checks every 90 seconds if something is wrong.
Could you use this and in case it stalls ever again, report it?
Re: Version 2.2.0
Posted: August 18th, 2017, 10:20 am
by Confused_too
k sure
Re: Version 2.2.0
Posted: August 19th, 2017, 8:08 am
by safihre
I released a new version, 2.2.1RC1 with only the small change that should make sure it does not get stuck.
Could you try this one so I know to release it to the big public in a few days?
https://sabnzbd.org/downloads.html
Re: Version 2.2.0
Posted: August 19th, 2017, 9:09 am
by Confused_too
Oh
K
The one I got yesterday with your link was named 2.3.0 [8aa57bf] and so far it's working fine.
K I'll try 2.2.1
Thanks
Re: Version 2.2.0
Posted: August 19th, 2017, 4:07 pm
by Confused_too
K little update for 2.2.1:
All the files I've downloaded today contained only rars, no par files or sfv.
Out of around 30 nzbs, 5 times i've got a "Aborted, cannot be completed - 1 article were malformed" Download stops for the file and it goes to "history"
Status Failed
Size 2.0 GB
Category tv
PathC:\Users\...\incomplete\....S06E01.....
Source.........................S06E01.................nzb
Download Downloaded in 6 mins 55 seconds at an average of 5.0 MB/s
Age: 686d
1 articles were malformed
Aborted, cannot be completed -
https://sabnzbd.org/not-complete
I hit "retry" and I see it had stopped half way thru. It resumes downloading
Repair[.................S06E01....................] No par2 sets
Trying RAR-based verification
RAR files verified successfully
Unpack[.......................S06E01.........................] Unpacked 1 files/folders in 1 min 1 sec
... and all is fine.
:
:
Is it unpacking no matter what? I don't have a crc code to check these files.
Re: Version 2.2.0
Posted: August 19th, 2017, 4:44 pm
by safihre
Maybe you can watch them videos and see if they work from start to finish?
This behavior is not new for 2.x.x, has been like that since maybe even before 1.0.0.
If you add the download again (not retry, just adding the NZB again), does it say 1 malformed again?
Re: Version 2.2.0
Posted: August 19th, 2017, 5:49 pm
by Confused_too
I readded 2 of the nzbs again and it stoped downloading in the same place.
I readded too one nzb with problems from version 2.2.0 (post #1) and it downloaded fine. No stall problem.
Re: Version 2.2.0
Posted: August 19th, 2017, 5:59 pm
by safihre
I think maybe it's better to allow up to 5 bad articles and just hope it unpacks fine.
5 is the same number we use before we abort Direct Unpack.
Re: Version 2.2.0
Posted: August 20th, 2017, 4:00 pm
by Confused_too
I got
Loading \\?\C:\Users\.............\incomplete\..............x2\__ADMIN__\SABnzbd_article_bcgg7r failed
whatever that means.
It was a pack of files and they unpacked fine.
Re: Version 2.2.0
Posted: August 20th, 2017, 4:12 pm
by safihre
Could you check in your log if below the line where the error is, there is a traceback what went wrong?
Re: Version 2.2.0
Posted: August 20th, 2017, 6:33 pm
by Confused_too
I can't find that specific line in the log.
The only mention of an error is at the end of the log:
Code: Select all
[ncenter]
ncenter_prio_download = 0
ncenter_prio_warning = 0
ncenter_prio_new_login = 0
ncenter_prio_queue_done = 1
ncenter_prio_startup = 1
ncenter_prio_failed = 1
ncenter_prio_disk_full = 1
ncenter_prio_error = 0
ncenter_enable = 0
ncenter_prio_complete = 1
ncenter_prio_pp = 0
ncenter_prio_other = 0
ncenter_cats = *,
[nscript]
nscript_prio_warning = 0
nscript_prio_complete = 1
nscript_prio_other = 0
nscript_prio_queue_done = 1
nscript_prio_failed = 1
nscript_prio_pp = 0
nscript_prio_new_login = 0
nscript_script = ""
nscript_prio_download = 0
nscript_prio_error = 0
nscript_prio_startup = 1
nscript_parameters = ""
nscript_enable = 0
nscript_prio_disk_full = 1
nscript_cats = *,
[pushover]
pushover_prio_error = 1
pushover_enable = 0
pushover_prio_complete = -1
pushover_prio_warning = 1
pushover_prio_startup = -3
pushover_prio_queue_done = -1
pushover_prio_other = -3
pushover_prio_pp = -3
pushover_prio_disk_full = 1
pushover_device = ""
pushover_token = <REMOVED>
pushover_prio_new_login = -3
pushover_prio_failed = -1
pushover_prio_download = -2
pushover_userkey = <REMOVED>
pushover_cats = *,
[growl]
growl_prio_disk_full = 1
growl_enable = 0
growl_prio_new_login = 0
growl_prio_other = 0
growl_prio_download = 0
growl_server = <REMOVED>
growl_prio_startup = 1
growl_prio_failed = 1
growl_prio_queue_done = 1
growl_prio_warning = 0
growl_prio_error = 0
growl_prio_complete = 1
growl_prio_pp = 0
growl_password = <REMOVED>
growl_cats = *,
[prowl]
prowl_prio_disk_full = 1
prowl_prio_error = -3
prowl_prio_download = -3
prowl_enable = 0
prowl_prio_failed = 1
prowl_prio_pp = -3
prowl_prio_new_login = -3
prowl_apikey = <REMOVED>
prowl_prio_startup = -3
prowl_prio_warning = -3
prowl_prio_other = -3
prowl_prio_complete = 0
prowl_prio_queue_done = 0
prowl_cats = *,
[acenter]
acenter_prio_warning = 0
acenter_prio_disk_full = 1
acenter_prio_new_login = 0
acenter_prio_error = 0
acenter_prio_failed = 1
acenter_prio_startup = 0
acenter_prio_queue_done = 1
acenter_enable = 1
acenter_prio_complete = 1
acenter_prio_download = 0
acenter_prio_pp = 0
acenter_prio_other = 0
acenter_cats = *,
[ntfosd]
ntfosd_prio_queue_done = 1
ntfosd_enable = 0
ntfosd_prio_error = 0
ntfosd_prio_startup = 1
ntfosd_prio_complete = 1
ntfosd_prio_pp = 0
ntfosd_prio_warning = 0
ntfosd_prio_other = 0
ntfosd_prio_disk_full = 1
ntfosd_prio_new_login = 0
ntfosd_prio_download = 0
ntfosd_prio_failed = 1
ntfosd_cats = *,
[pushbullet]
pushbullet_prio_download = 0
pushbullet_prio_queue_done = 0
pushbullet_enable = 0
pushbullet_prio_complete = 1
pushbullet_prio_warning = 0
pushbullet_device = ""
pushbullet_prio_failed = 1
pushbullet_prio_other = 0
pushbullet_apikey = <REMOVED>
pushbullet_prio_disk_full = 1
pushbullet_prio_new_login = 0
pushbullet_prio_pp = 0
pushbullet_prio_startup = 0
pushbullet_prio_error = 0
pushbullet_cats = *,
[servers]................. etc
... if this makes any sense
: