newsbin.com

I had beta4 stuck for a while not downloading headers. Restarting the app started it working again.

Is this a known issue? I updated to rc2

What does the cache count look like down at the status bar? Do you have it set to automatically update headers.

I will do more research if it happens again. Yes, update headers is used and the download list had the headers on top.

It occurred again. Cache says 0/200
Logs have a lot of 430 errors

What happens if you hit "help/about" when it gets stuck?

430 errors happen during file downloads.

Long unrars will block the header downloads until the unrar completes because download runs out of packets.

When this happens no unrars or repairs are happening.

Restarting the application kicks outback into action


It looks like this happens after enough 430s are encountered.

The list of connections is empty on the right and all the server connections are disconnected.

What is help/about supposed to do?

How many servers do you have?

One active.

Is it possible it is doing some rar/par work that I am not seeing?

Is there a way to determine what exactly the software is doing?

Quade wrote:What happens if you hit "help/about" when it gets stuck?

430 errors happen during file downloads.

Long unrars will block the header downloads until the unrar completes because download runs out of packets.

How does the download run out of packets when the unrar process should not be connected to the internet? Would that not free up connections to allow the download process to continue?

Unrars don't block downloading but it does block writing chunks of partial files to disk so when you run out of cache blocks, Newsbin will wait till more free up. The cache block writing to disk continues when the unrar/repair complete. That's how 6.62 works.

You can download headers and unrar at the same time as long as your file downloads haven't already run the system out of blocks during the unrar. The reason it blocks writes is that unrars can take as much as 3 times longer when the chunk writes happen at the same time.

People complained about this so a future version will permit them to run concurrently again. It's already working that way in the new engine. The problem with the old way was that file downloads could get way ahead of the unrar/repair and restarts became problematic. The new concurrent download doesn't permit that to happen because if writes chunks to disk. It's assembly of the files which is now deferred till after unrar/repair completes. So you still get full download speed and the unrar/repair can't get behind.

syshog wrote:

Quade wrote:What happens if you hit "help/about" when it gets stuck?

430 errors happen during file downloads.

Long unrars will block the header downloads until the unrar completes because download runs out of packets.

How does the download run out of packets when the unrar process should not be connected to the internet? Would that not free up connections to allow the download process to continue?

So, it happened again (6.62 RC2). cache 0/200. No Urar or PARs going on. Looks like it was stuck like that for about 24hrs.

All connections were disconnected.

There were a few strange errors in the logs (ERROR <name of server> Error talking to Server).
Also, ERROR NW_DirectDownloadChunkWorker: <name of file>. Then, ERROR NW_CloseChunk - closing a dirty connection.
Finally, a ERROR NW_DirectDownloadChunkWorker:Connection to News server failed <name of server> ARTICLE <name of article> |400 session time limit reached (please reconnect)

Is it possible that there's a server side session time limit and that NBP simply does not try to disconnect and reconnect when it gets it?

pressing help | About caused it to be immediately unstuck.

What does help | About do?

So, it happened again (6.62 RC2). cache 0/200. No Urar or PARs going on. Looks like it was stuck like that for about 24hrs.

Do you use periodic header downloads? I mean the setting where Newsbin automatically downloads headers for you at set intervals? I have 3-4 people now who have a problem with the cache running out and the one common thing seems to be that they all use automatic header downloads.

Yes. I have automatic header downloads with regex download filters.

TBlack thinks he's found an issue with appending log files together.

[LOGGING]
Append=0

You might search your "NBI" file for "Append" and if it's set to 1, set it to zero and see if it changes the symptoms.

There was no append value at all. What is the default for this entry?

I added it to the nbi file.

No entry means it's disabled. So basically this isn't the fix you're looking for.