by Quade (Posted Thu, 01 Jan 2015 18:06:40 GMT)
It's not really a problem. It declared it failed and lets any other active servers have a shot at it. On retry, the original server will get tried again. I don't see any reason to not hand it to another server. I have no idea if the connection failure is temporary or permanent. You could just as easily have run out of quota and the failure really is a semi-permanent failure. Newsbin will always re-connect after a failed connection. That's why if you run max connections, it'll boot you over your limit because news servers are slow to release your authentication token.
You basically get N tokens, equal to max connections. The server has to release a token back to the free pool when you disconnect and it takes most servers awhile to do so. That's why you don't want to run max connections so, you always have a couple free tokens for cases like this.
My AW fails like this periodically and it doesn't require lots of retries. Connection failures make Newsbin reconnect. The connection failures are what boots you over your connection limit not the retries. Retries don't disconnect and re-connect. They just tell Newsbin to try again on the same server. It sounds like you lose the ability to connect to the server and then eventually it fixes itself.
On a related note, Newsbin will never assemble incomplete files till the retries expire so, if you have say 10 retries set, it might be an hour or more before it assembles and repairs. I use 2 retries which is a minute or two.
I don't have any problems like this so, I'm pretty much guessing. I have had reports of files left as ".nb2" files. Newsbin assembles files into NB2's then renames them to the real name. If the rename fails. You might end up with ".rar.nb2" instead of ".rar". When they get left as NB2's I'm pretty sure the problem is security software blocking the rename. Probably because they're scanning the file at the same time Newsbin attemps to rename them.
You're mixing up a bunch of different issues in a single topic so, don't be surprised if I miss some.
Read Main Topic
2. I don't use astraweb as I previously stated, however it seems other users on your forum do. The problem isn't the news server. It's how newsbin behaves once it throws the miscommunication error and automatically decides the article is lost even though it might not be. I'll upgrade and see if it there's new behavior.
It's not really a problem. It declared it failed and lets any other active servers have a shot at it. On retry, the original server will get tried again. I don't see any reason to not hand it to another server. I have no idea if the connection failure is temporary or permanent. You could just as easily have run out of quota and the failure really is a semi-permanent failure. Newsbin will always re-connect after a failed connection. That's why if you run max connections, it'll boot you over your limit because news servers are slow to release your authentication token.
You basically get N tokens, equal to max connections. The server has to release a token back to the free pool when you disconnect and it takes most servers awhile to do so. That's why you don't want to run max connections so, you always have a couple free tokens for cases like this.
This requires many retries and eventually the news server will just start refusing your IP for a small period so many attempts. It would be nice to be able to leave that article attachment labelled blank as if it was never tried before instead of failing it. Right now I can't tell if the article attachment doesn't exist or if the news server is just rejecting my connection attempt.
My AW fails like this periodically and it doesn't require lots of retries. Connection failures make Newsbin reconnect. The connection failures are what boots you over your connection limit not the retries. Retries don't disconnect and re-connect. They just tell Newsbin to try again on the same server. It sounds like you lose the ability to connect to the server and then eventually it fixes itself.
On a related note, Newsbin will never assemble incomplete files till the retries expire so, if you have say 10 retries set, it might be an hour or more before it assembles and repairs. I use 2 retries which is a minute or two.
The result is I need to force each and every single volume to assemble. A side effect is that most volumes can be forced assembled, but not all. Running quickpar will show you one or two volumes are missing even though it appears as downloaded in newsbin. I'll try and grab a screenshot since this has been happening regularly. thankfully I had enough pars to repair even the missing volume.
I don't have any problems like this so, I'm pretty much guessing. I have had reports of files left as ".nb2" files. Newsbin assembles files into NB2's then renames them to the real name. If the rename fails. You might end up with ".rar.nb2" instead of ".rar". When they get left as NB2's I'm pretty sure the problem is security software blocking the rename. Probably because they're scanning the file at the same time Newsbin attemps to rename them.
You're mixing up a bunch of different issues in a single topic so, don't be surprised if I miss some.
Read Main Topic