*Fixed bug in Sabnzbd which made queues not display *Fixed bug where NZB would get stuck and not auto Unrar/par *Fixed bug where NZB would get stuck and not auto Unrar/par (Fixed this time) *Option to flatten extract directory (auto extracted files all go in same directory) *Set Thread(CPU) priority when downloading and for Unrar/Par *Choose DL and extract directories with a chooser *Optional alternate connection type for Newznab (debug) *Downloads some malformed files which failed before Add NZB (small size is also fine, just one that stalls) and wait until it stall at 99%.*Stop trying to reload last file when launch app Now turn on Debug logging in the Status page No other active downloads, having them individually paused is also fine (otherwise the log is very hard to read) How many servers do you have and what is the Timeout setting for each server? What have you set for Number of Retries (in Config->Switches)? Everything is working fine now on 1.0.0 Final?
#Sabnzbd queue repair upgrade
I will let the queue heal itself and if you guys need logs or anything, just let me know, I could always upgrade to 1.0.1RC1, test a few NZBs and send you the logs or whatever files you need to debug.Īnyone with this problem, could you please do the following? We are not able to reproduce it so we need user inputĬan you answer/do the following on 1.0.1:
It is behaving exactly like Futureman83's setup. par2 files will get downloaded in order for the repairing, verifying and post-processing tasks to complete.
#Sabnzbd queue repair download
The *Repair* function will fix the Download queue and the. To add insult to injury, by rolling back to 1.0.0, everything start working back like a charm (like it always did ! :-)). I do have multiple servers configured with different priority pointing at different locations using different ports, but 90% of the time, it will always fetch from my topmost priority server I assume that my news provider did not change anything on their end. My news servers have been the same ones for years, priority did not change as well (it changed from 0.7ish to 1.0ish with the new implemented changes to SAB). I tried with about 100 different ones, different sizes, different content and out of the blue, it will hang at 99%. It can be a mix of multiple variables but at this moment, I have no clue where to look. Something has definitely *broke* from 1.0.0 to 1.0.1RC1. Not sure if anyone else has had this issue. So I did another queue repair and then resumed the other 99% and they all started to complete and verified, weird!
Now I just did a fresh download this morning of a flac album and it actually processed through 100% like it used to, weird! a couple reboots and queue repairs didn't seem to resolve the issue either. I was just moving the folders out of incomplete then removing them manually from the queue because there was nothing wrong with the download, all files were there including the par2 sets which all verified out as good. at first I thought it was because I didn't have the python yenc package setup but everything's been working fine for months so I installed yenc anyway got sabnzbd to recognize it, still downloads would hang on 99%.
#Sabnzbd queue repair update
This issue popped up after my update manager (linux mint) pushed me the new 1.0 sabnzbd.Īll my settings and configuration were maintained however any new nzb files detected would download fine up to the last 1% then hang as if it were waiting for some post processing.
0 kommentar(er)
