Page 1 of 1

WSARecv Socket Error Code:10054 An existing connection was

PostPosted: Sat Jan 28, 2012 11:16 am
by jdmatl
Running Version 6.20, on a Quad I5 win7 64bit PC with 16gigs of ram.

Trying out Blocknews.net, have been using NewsHosting. NewsHosting does not give me the below errors.

Getting the following errors from provider blocknews.net, Is there some setting I can change in Newsbin to keep the below from happening.

As the log states, I get it is most likely 99% an issue on the blocknews.net end.

Thanks

===============
[09:04:53] ERROR Socket - Error: WSARecv Socket Error Code: 10054 An existing connection was forcibly closed by the remote host.
[09:04:53] ERROR NNTPSocket - SendCommand Worker - Server:usnews.blocknews.netSendCommand - failed to Read Response From server: Socket - Read From Server Failed
[09:04:53] ERROR NNTPSocket - Socket HandleError - Server: usnews.blocknews.net SendCommand - Server Disabled Service on connection:
[09:04:53] ERROR NNTPSocket - SendCommand Worker - Server:usnews.blocknews.netSendCommand - failed to Read Response From server: Socket - Read From Server Failed
[09:04:53] ERROR NNTPSocket - Socket HandleError - Server: usnews.blocknews.net SendCommand - Server Disabled Service on connection:
[09:04:54] ERROR InterSocket - Error: Connection Failed, Host: usnews.blocknews.net Error Code: 10061 No connection could be made because the target machine actively refused it.
[09:04:54] ERROR InterSocket - Error: Connection Failed, Host: usnews.blocknews.net Error Code: 10061 No connection could be made because the target machine actively refused it.
[09:04:55] ERROR InterSocket - Error: Connection Failed, Host: usnews.blocknews.net Error Code: 10061 No connection could be made because the target machine actively refused it.
[09:04:55] ERROR InterSocket - Error: Connection Failed, Host: usnews.blocknews.net Error Code: 10061 No connection could be made because the target machine actively refused it.
[09:04:55] ERROR InterSocket - Error: Connection Failed, Host: usnews.blocknews.net Error Code: 10061 No connection could be made because the target machine actively refused it.
[09:04:55] ERROR InterSocket - Error: Connection Failed, Host: usnews.blocknews.net Error Code: 10061 No connection could be made because the target machine actively refused it.

Re: WSARecv Socket Error Code:10054 An existing connection w

PostPosted: Sat Jan 28, 2012 11:19 am
by DThor
What port are you using?

Code: Select all
usnews.blocknews.net allows connections on ports 23,119, 2000,880,8080,9000


DT

Re: WSARecv Socket Error Code:10054 An existing connection w

PostPosted: Sat Jan 28, 2012 11:46 am
by itimpi
There seem to be potentially two different errors.

The first is where the remote end forcibly closed the connection - and that I suspect you cannot do anything about. This is probably due to something that is set at the remote end and is outside your control.

The second is where the remote end refused an attempt by Newsbin to re-establish the connection. This is normally happens because you ahve Newsbin configured to use the maximum (or close to the maximum) number of connections your account and the server has not freed up the connection internally before Newsbin tries to connect again. The solution to this is normally to set up Newsbins maximum connections to be slightly less that the account allows so that there is a small pool of unsed connections that can cover this server recycle time for closed connections.

Re: WSARecv Socket Error Code:10054 An existing connection w

PostPosted: Sat Jan 28, 2012 11:59 am
by jdmatl
itimpi wrote:There seem to be potentially two different errors.

The first is where the remote end forcibly closed the connection - and that I suspect you cannot do anything about. This is probably due to something that is set at the remote end and is outside your control.

The second is where the remote end refused an attempt by Newsbin to re-establish the connection. This is normally happens because you ahve Newsbin configured to use the maximum (or close to the maximum) number of connections your account and the server has not freed up the connection internally before Newsbin tries to connect again. The solution to this is normally to set up Newsbins maximum connections to be slightly less that the account allows so that there is a small pool of unsed connections that can cover this server recycle time for closed connections.


I am actually many times under their connection limit. I am using 15, they allow 50. just thinking out loud, I think everyone must but putting it @ 50, when 10 or 15 would do. Blockusenet might be giving you 50, but system could be cutting them down to 10. going to drop down to 10 concurrent. that should be enough to max out my comcast connection.

Re: WSARecv Socket Error Code:10054 An existing connection w

PostPosted: Sat Jan 28, 2012 12:01 pm
by jdmatl
DThor wrote:What port are you using?

Code: Select all
usnews.blocknews.net allows connections on ports 23,119, 2000,880,8080,9000


DT


using 119, tried using 8080 and the speed was HORRIBLE. Figured it was Crumcast possibly doing some 80/8080 caching "behind the scenes).

Re: WSARecv Socket Error Code:10054 An existing connection w

PostPosted: Sat Jan 28, 2012 1:23 pm
by Quade
[09:04:54] ERROR InterSocket - Error: Connection Failed, Host: usnews.blocknews.net Error Code: 10061 No connection could be made because the target machine actively refused it.


This suggests the port is wrong. I'd try setting it to 23, then restart Newsbin and try again.

Re: WSARecv Socket Error Code:10054 An existing connection w

PostPosted: Sun Jan 29, 2012 2:04 pm
by jdmatl
Dropped the number of connections to 10 and problems seem to have gone away in early testing. just pulled down about 1gig and didn't have any of these errors. Speed was at max levels for my connection. Will keep updating thread a couple of times during the week with progress. I left port at 119 for now.

Re: WSARecv Socket Error Code:10054 An existing connection w

PostPosted: Sun Jan 29, 2012 9:51 pm
by jdmatl
Connections dropped to 10 didn't do the trick less errors, but they still pop up. will try changing port to 23 next.

Re: WSARecv Socket Error Code:10054 An existing connection w

PostPosted: Wed Feb 08, 2012 3:20 pm
by clement1
I'm having the same problem.
===
[13:13:55] ERROR - SSL Read Failed: 10060 A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.

[13:13:55] ERROR NNTPSocket - Server:news.us.usenet-news.net NNTPServer: Timeout - Waiting for Server to send Data: Socket - Read or Write Timeout
[13:13:55] ERROR NNTPSocket - SendCommand Worker - Server:news.us.usenet-news.netSendCommand - failed to Read Response From server: Socket - Read or Write Timeout
[13:13:55] ERROR NNTPSocket - Socket HandleError - Server: news.us.usenet-news.net SendCommand - Server Disabled Service on connection:
===
I've got number of connections set to 20 (Usenet News allows 50). I've looked the ISP logs online and it shows over 48 connections!!! It seems Newsbin is constantly trying to establish new connections, rather than going back to old ones?????

The resetting is very bad - also seems to be damaging the db files - have to keep re-downloading headers. I've tried compressing headers, but that doesn't seem to fix the problem.

Any suggestions?

Re: WSARecv Socket Error Code:10054 An existing connection w

PostPosted: Wed Feb 08, 2012 3:31 pm
by Quade
Header downloads don't talk directly to the DB so, I'm skeptical about this damaging the DB. The header downloads write RV4 files which are later fed into the DB. You might want to set a 100-200 post header overlap in the server options in case this is a server farm and it's not well synchronized.

- First thing I'd do is check "Disable XFeatures" in the server options. At this point only Giga and Astra seem to have implemented Xfeatures properly.

- I'd check your virus scanner/firewall and make sure it's not monitoring the data between Newsbin and the news server. Most virus scanner/firewalls don't know how usenet works any more. Then tend to damage the data.

This specific error means, Newsbin sent a command to the server and it didn't reply in time. Could be a number of causes but, typically it's a firewall issue. Some servers drop the connection when enough data is sent over it. Metered accounts commonly do that. Typically it's a different error though.