Stuck on "Quick Check" & "Verifying"

[xman123321]

Hey,

I've had SABnzbd running well for a few days now - no problems, apart from a few incompletes - but this is nothing to do with SAB...

However, now it's paused itself and left me with quite a few unfinished NZBs...



It's paused itself because I set it to pause when there is around 5 - 10GB space left (That is where the NZBs get put first, they are soon shoved onto another hard drive once they finish).

Any ideas why the NZBs won't move from "Quick Check..." and "Verifying..."?

Thanks,
xman

[shypike]

Possibly the par2 program is hanging.
If you suspect this, kill the running instance of par2 with your operating system task manager.
This should fail the hanging job and will start processing the other ones.
You can retry the failed job later.

[xman123321]

I just totally restarted the server and all the files that were in quick check and verifying have changed to 0:00:00 left and they all have 3mb remaining to download but aren't downloading. It's come out of paused and is continuing to download other files now...

[xman123321]

I tried pressing "Repair" under Status which sort of fixed it - about 20 nzbs were moved to the processing area and then they all failed due to not enough repair bits

Now the files are downloading again but it looks like they are downloading until 3mb left and then moving onto the next one like last time :/

It looks like by pressing the repair button it just resets the download and moves it to the back of the queue...

[shypike]

Check your server settings.
The timeout should not be too short (increase it).
Check "Retries" on Config->Switches. It should say 3 (or another small value).
"Only for optional servers" right below it should be off.

[cappycdn]

I have the same issue as xman123321...no luck with the suggestions provided so far. I will follow this thread to see where it goes.

I noticed when looking into the 'incomplete' folder that only some files are downloaded. Some weird behaviour usually happens as well where the download speed plummets to almost zero, yet the file goes from 0MB downloaded to 1/4 downloaded to pretty much done. Then it either gets stuck sitting in queue as forced missing only a few MBs or it bounces back and forth between queue and finished a few times and when that happens it usually erros out with various messages...latest one for me was invalid par2 files. Others will be missing parts etc.

I apologize ahead time for my poor description above.

[shypike]

Possibly it's a combination with specific servers.
Which Usenet provider are you using?

[cappycdn]

I am using Giganews as my primary and newshosting as my backup. I had increased my "Server" 'timeout' to 240 secs. "Switches" 'Server', 'maximum retries' tried '5' instead of '3'. 'Only for Optional servers' = off.

Also, When the nzb is sitting in queue set to force - I click on the nzb and showing are files remaining to be downloaded are always par files. Time left always shows 0.

When I hover over the 1st nzb in the green box that shows up it says "status" 'downloading' all others indicate 'verifying'. As well as age green box also includes number of missing articles.

If I check the size of the folders located in 'Incomplete' folder they are all only a few MBs where they should be ~2GB.

[shypike]

Can you email an example NZB to bugs@sabnzbd.org ?
Please add the url of this message.

[cappycdn]

Sure thing. Sent.

I did conduct a repair on the queue and then Sab reported correct sizes and my download speeds went low to almost 0. I checked incomplete folder and now the files are populated whereas previously only a couple of files existed. As well I opened a 'get info' window to see size of the nzb folder within the incomplete folder and as sab started reporting more of the file being downloaded 'get info' did not show the same size.

I am now seeing my speed go up to normal for a bit and back down. Possibly this is sab looking at primary server and not finding the articles and moving to the backup server?

I may have been playing around with my servers enabling and disabling and switching between them a little while ago. Possibly I created issues when I did this. I have since restarted the nzbs while having a primary and backup server as previously stated in thread configured and enabled.

BTW using:

Mac OS 10.8.2
SAB 0.7.6

[xman123321]

Yep exactly the same problem! I use Supernews.

[shypike]

Sure thing. Sent.

The case you sent me is rather simple: it's not on Giganews any more.
Only your backup server still has it.
If you start enabling and disabling servers in the middle of a download,
the results are unpredictable.
Once it has been established that an article is not available from the active servers,
it doesn't help that another server is later enabled.
SABnzbd isn't going back to ask again for missing articles.
BTW: when you use "Retry" from History, any missing file will retried,
but not individual missing articles of files.

BTW: the low speed just means that SABnzbd has hit a whole range of missing articles.
You can get an indication by hovering the mouse over the queue entry, watch the popup.

PS:
SABnzbd has a problem with this specific NZB, it keeps sending back to the queue a number of times
in order to get more par2 files, but without success.
This looks like a bug in SABnzbd, but even without that behaviour the job cannot be successfully
completed with just Giganews (or SuperNews).

[cappycdn]

The case you sent me is rather simple: it's not on Giganews any more.
Only your backup server still has it.
If you start enabling and disabling servers in the middle of a download,
the results are unpredictable.
Once it has been established that an article is not available from the active servers,
it doesn't help that another server is later enabled.
SABnzbd isn't going back to ask again for missing articles.
BTW: when you use "Retry" from History, any missing file will retried,
but not individual missing articles of files.

I had assumed the enabling/disabling of servers would cause a problem so I started the process from scratch using different combinations of servers between primary/backup or primary/primary or primary/optional. Thank you for clarifying missing file vs. missing article and when SAB asks for what is missing.

BTW: the low speed just means that SABnzbd has hit a whole range of missing articles.
You can get an indication by hovering the mouse over the queue entry, watch the popup.

This is pretty much what I assumed...just a little surprised at my primary missing so much...will chalk it up to takedown requests.

PS:
SABnzbd has a problem with this specific NZB, it keeps sending back to the queue a number of times
in order to get more par2 files, but without success.
This looks like a bug in SABnzbd, but even without that behaviour the job cannot be successfully
completed with just Giganews (or SuperNews).

After a little contemplation I am leaning towards a combination of the par2 issue above as when I check all my nzb's that are having problems they are all only missing the par files when clicked on. I also think part of the issue is missing articles.

So in a nutshell it looks like nzb 'A" has missing files/articles and checks both servers. During this process it somehow thinks its complete but missing par files of some sort and then fails completely sitting in queue as forced?

I assume to verify the missing articles/files you just used a reader to check the files themselves form the respective server? That was my next step in my investigation.

BTW from the limited time I have been on the forums you are one busy person! Thank you for taking the time and making this experience a very positive one.

[shypike]

The reason for the NZB to bounce a few times between queue and post-processing
is because something resembling a par2 file is downloaded but
not complete enough to be usable by the par2 program.
There's also a "sample" set in the NZB which partially completes.
A takedown request is the most likely reason for the bad results.

[cappycdn]

I assumed as much but had no way to validate my assumption that I knew of so I came to the forums. Again, thanks for working it through for me.