Issues, Workarounds & Localization

 
 

Socket was closed traced back to Amazon

Author
Amarr Empire
#1 - 2017-05-15 10:44:02 UTC
So I've been struggling with regular socket closed messages while trying to play, and I decided to look into what is causing the problem for me. I've used the network diagnostic tool to run a traceroute to the eve hosts with mixed results, included at the end of this post.

Hops 1-7 in each trace are operated by my ISP, and from 8 onward are operated by Amazon. Now I've looked into the IP address of the hop before the timeouts (178.236.3.119, and 54.240.221.108) and found it's run by Amazon over in Ireland. Now this makes me believe there may be an issue with Amazon's cloudfront service, in combination with Eve Online. I would be curious to know if others can trace their socket closed issues back to Amazon, or if I am simply misunderstanding the logs.


Quote:
launcher.eveonline.com:
5 29 ms 30 ms 29 ms host-78-144-9-51.as13285.net [78.144.9.51]
6 28 ms 28 ms 28 ms host-78-144-14-118.as13285.net [78.144.14.118]
7 28 ms 29 ms 30 ms host-78-144-5-53.as13285.net [78.144.5.53]
8 52 ms 42 ms 32 ms 54.239.100.132
9 29 ms 29 ms 28 ms 54.239.100.139
10 29 ms 30 ms 29 ms 178.236.3.119
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 29 ms 29 ms 29 ms server-216-137-63-165.lhr3.r.cloudfront.net [216.137.63.165]

binaries.eveonline.com:
5 29 ms 29 ms 31 ms host-78-144-9-47.as13285.net [78.144.9.47]
6 29 ms 29 ms 30 ms host-78-144-14-122.as13285.net [78.144.14.122]
7 28 ms 30 ms 31 ms host-78-144-5-53.as13285.net [78.144.5.53]
8 34 ms 38 ms 45 ms 54.239.100.72
9 30 ms 30 ms 29 ms 54.239.100.79
10 29 ms 29 ms 29 ms 178.236.3.119
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 30 ms 30 ms 30 ms server-216-137-63-241.lhr3.r.cloudfront.net [216.137.63.241]

resources.eveonline.com:
5 96 ms 35 ms 34 ms host-78-144-9-45.as13285.net [78.144.9.45]
6 29 ms 29 ms 28 ms host-78-144-14-122.as13285.net [78.144.14.122]
7 30 ms 28 ms 30 ms host-78-144-5-53.as13285.net [78.144.5.53]
8 50 ms 32 ms 44 ms 54.239.100.92
9 46 ms 30 ms 29 ms 54.239.100.105
10 30 ms 29 ms 29 ms 54.240.221.108
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 28 ms 28 ms 29 ms server-216-137-63-103.lhr3.r.cloudfront.net [216.137.63.103]
Amarr Empire
#2 - 2017-05-15 17:24:18 UTC
I believe the issue may be somehow related to the download-as-you-play feature through Amazon, and that by checking the option to download everything upfront I may be able to avoid routing through amazon's data centre during gameplay. I will report back if this resolves the problem for others reference.
Greater D.U.S.K. Coalition
#3 - 2017-05-19 11:00:58 UTC
I have the "download everything" option selected (always had it) got 2 socket error disconnects today in 2 hours of play.
I have a 300mb down 100mb up line fiber optics, tested so no ping loss so the issue is definitely NOT ON MY SIDE!
Fix your **** CCP!
Gallente Federation
#4 - 2017-05-21 20:43:57 UTC
I get this error quite often. It usually happens when a spike of bandwidth usage occurs in my household. Streaming movies, etc. Though I suspect it may also have something to do with the launcher. If I close the launcher, the socket closed error rarely occurs.
Forum Jump