SABnzbd Forums

Sorry to let you guy know but the 99% sticking has moved to 98%

One thing that does work is that you have allowed it to move past that. I also found BY Accident that if you Pause then UnPause it. The File either completes or restarts the full download and finishes.

Hopes this helps

How many servers do you have?
And you are sure it's not just waiting for a server to timeout, you waited for more than 5 minutes?

When you look at the files still to be downloaded in the hanging job, which ones are they?

I've had this happen as well - if it happens it is during the "quick verify" I believe it says. I'll try the pause and unpause to see if that works - quitting SABnzb and starting it up again also gets things working again.

It happens during QuickCheck? But then it's in post-processing?

Could you also answer my other questions please?
- How many servers do you have? Do you have free/bad servers that timeout or give failed login errors?
- And you are sure it's not just waiting for a server to timeout, you waited for more than 5 minutes?
- When you look at the files still to be downloaded in the hanging job, which ones are they?

@pguillot69 does it also happen for you only after verification?

Yeah I can confirm that it is happening to me as well in 2.2.1. It is again stuck during checking phase and blocking the queue.



I am using one server. Grepping the logfile for the item that got stuck shows that it got downloaded five hours ago so I am pretty sure it's not running some threads in the background now I just restarted SABNZBd and now it's properly continuing again.

Unfortunately I can't seem to find any errors in the logfile (I have debugging loglevel enabled) so I am not sure why it will hang on processing I also can't seem to reproduce the issue. It's just seems to be happening randomly.

I think I have identified and now fixed the issue.

Can you try this test-build of 2.3.0? It says Alpha, but it is stable.
Link-removed, see post below.
(macOS build should be available within ~1 hour of this post, the build-server is a bit busy)

I have 2 servers.

I tried the 2.3.0Alpha1-2 build - it just crashed attempting to start (with option to open Console, or Terminate)
reverted to 2.2.1 and it's working again for now.

For me the pause & un-pause doesn't work - I have to quit & launch SABnzb again, or use the Troubleshoot menu to "restart" it (although this most recent time I tried that option, it crashed even more - had to use Activity Monitor to quit it - strangely didn't have to use force-quit option)

Can you try 2.3.0 again but start it with an empty queue? I should have mentioned that.

EDIT: nevermind, I now see the problem in this version. Will fix this.

Oke sorry about that, this is the correct working version.
Please try

https://github.com/sabnzbd/sabbuild/rel ... 0-Alpha1-3

that version starts up now (I did happen to have an empty queue as well), downloads started without issue.
"Verifying repair: 02/02" is where it now seems to be stuck - I left it for over 10 minutes.

Using Troubleshoot -> Restart got it working again immediately.
The next batch of test downloads the first one stalled at "Repair: Quick Checking"

possibly also of important to note - as soon I I select "Restart" from the troubleshoot menu, the item that was stalled immediately starts unpacking - then SAB actually shuts down, and starts up again where the unpacking continues.

also not sure if it helps - it only seems to "hang" on a new batch of files - it'll grind through 20+ that finished downloading without stalling/hanging again until I start some new downloads again.

Oke so using 2.3.0, could you switch logging to Debug in the Status window, wait for it to hang on that verification and the click Show Logging?
If you could send the log to me at [email protected]?

It seems to be a problem with Direct Unpack. But hard to say what.

Having the same hanging issue on 2.2.1 Ubuntu 16. Restarting sabnzbd did not solve the problem. There are 4 stuck nzbs:

Direct unpack: 19
Direct unpack: completed
Direct unpack: completed
Repair: Quick Checking

I have three servers and multicore Par2 enabled.

Have you gotten v2.3.0 to a place worth trying yet, or should I hold off for now?

It's stable and has some improvements for Direct Unpack for edge cases, so try 2.3.0 first. It's stable-release now.

If it happens again, could you enable Debug logging in the Status window and then send me the logs at [email protected]?