Further to my post 'Sometimes NB starts over downloading files' I often notice that Newsbin simply stops and nothing at all is happening.
Multiple files (different .nzb's) are in queue for download. Newsbin halts. 10-15 minutes.
To solve the issue I usually close Newsbin and restart it. NB will pick up where it left and continues. In most of the cases it finalizes the job(s).
In a worst case scenarion I might need to again close and relaunch.
In such cases files may be downloaded twice, so, for instance, I might be having 2x 2GB .mkv files.
In case of really large downloads (BDs), I discovered that it is best to download them one by one and relaunch NB in between.
Yesterday a (big) download halted, after relaunching NB the other half of the set was downloaded and the task was finalized properly.
I am writing this because, right now, NB hangs on completing a set, though all files seems to have been downloaded.
In the status it says:
[PAR:2847(141) OF 2847] D:219 DL:0 Retry:0 N:0
only the N: digit changes, so: N: 8, N:6, N3: N:0 -wait some 5 seconds, then again: N:9 N:7 N:4 N:0 etc.
Like this:
this time, relaunching did not help.
the 1st relaunch, NB downloaded another few files
could not complete
the 2nd relaunch - nothing was downloaded, but NB could not complete the job (see above error)
3rd - same as two
then I closed NB
double clicked the NZB and downloaded it again, bypassing filters.
same as the 1st time - could not complete.
I copied the whole set to a different folder and started the extraction process.
Here it comes: it appears the last file needed a password!
after providing it, the file could be extracted successfully...
Now
a) all the previous halts/restarts and finalizing the task upon restarts -> nothing to do with a password
b) the last download (just now and prompting me to write this post) -> password issue
as for item a) maybe it has something to do with buffers, I don't know
as for item b) it would be nice if there would be a kind of pop-up warning saying that a password is required
i wasn't aware of it and kept on trying and trying, assuming it had something to do with issue a)
NB 6.72 b 4776
Windows 10 x64
=