These forums have been archived and are now read-only.

The new forums are live and can be found at https://forums.eveonline.com/

Issues, Workarounds & Localization

 
  • Topic is locked indefinitely.
123Next pageLast page
 

Socket Closed - Launcher only

First post First post
Author
Previous Topic Next Topic
Airi Kitamura
Doomheim
#1 - 2016-01-05 20:21:25 UTC  |  Edited by: Airi Kitamura
Hi,

Two days ago I had 3 eve clients installed the old fashioned way, and was playing without any issues.

I removed the Eve installation, and installed the new Eve Launcher and added the 3 accounts through there.

Since then I constantly get the "socket was closed" error.

I looked through the documentation available on the forum and support section.
I highly doubt my ISP has made any changes at the exact time I was re-installing the eve clients through the new launcher.

Quote:

Starting basic diagnostics

Looking up hosts:
binaries.eveonline.com
res.eveonline.ccpgames.com
client.eveonline.com

Host lookup for client.eveonline.com returned:
87.237.39.208

Host lookup for res.eveonline.ccpgames.com returned:
54.240.184.156
54.240.184.55
54.240.184.86
54.240.184.188
54.240.184.51
54.240.184.50
54.240.184.110
54.240.184.222

Host lookup for binaries.eveonline.com returned:
54.240.184.17
54.240.184.80
54.240.184.62
54.240.184.69
54.240.184.232
54.240.184.137
54.240.184.6
54.240.184.61

Host lookups done
Starting ping for binaries.eveonline.com

Pinging d17ueqc3zm9j8o.cloudfront.net [54.240.184.17] with 32 bytes of data:
Reply from 54.240.184.17: bytes=32 time=2ms TTL=55
Reply from 54.240.184.17: bytes=32 time=2ms TTL=55
Reply from 54.240.184.17: bytes=32 time=2ms TTL=55
Reply from 54.240.184.17: bytes=32 time=2ms TTL=55

Ping statistics for 54.240.184.17:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 2ms, Maximum = 2ms, Average = 2ms

Starting ping for res.eveonline.ccpgames.com

Pinging dm794883twbxj.cloudfront.net [54.240.184.156] with 32 bytes of data:
Reply from 54.240.184.156: bytes=32 time=5ms TTL=55
Reply from 54.240.184.156: bytes=32 time=5ms TTL=55
Reply from 54.240.184.156: bytes=32 time=5ms TTL=55
Reply from 54.240.184.156: bytes=32 time=5ms TTL=55

Ping statistics for 54.240.184.156:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 5ms, Maximum = 5ms, Average = 5ms

Starting ping for client.eveonline.com

Pinging client.eveonline.com [87.237.39.208] with 32 bytes of data:
Reply from 134.222.109.115: Destination net unreachable.
Reply from 134.222.109.115: Destination net unreachable.
Reply from 134.222.109.115: Destination net unreachable.
Reply from 134.222.109.115: Destination net unreachable.

Ping statistics for 87.237.39.208:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Basic diagnostics finished



Quote:

Starting traceroute diagnostics - this may take several minutes

Starting tracert for binaries.eveonline.com

Tracing route to d17ueqc3zm9j8o.cloudfront.net [54.240.184.17]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.2.254
2 1 ms 1 ms 1 ms static.kpn.net [xxx.xxx.xxx.xxx]
3 3 ms 4 ms 3 ms nl-asd-dc2-git-cr03.kpn.net [213.75.1.81]
4 4 ms 3 ms 4 ms nl-asd-dc2-ice-ir01.kpn.net [213.75.1.80]
5 1 ms 1 ms 1 ms asd2-rou-1022.NL.eurorings.net [134.222.93.138]
6 1 ms 1 ms 1 ms asd2-rou-1043.NL.eurorings.net [134.222.48.223]
7 5 ms 6 ms 5 ms asd-s17-rou-1041.NL.eurorings.net [134.222.48.235]
8 2 ms 2 ms 2 ms 72.21.221.100
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 2 ms 2 ms 2 ms server-54-240-184-17.ams50.r.cloudfront.net [54.240.184.17]

Trace complete.

Starting tracert for res.eveonline.ccpgames.com

Tracing route to dm794883twbxj.cloudfront.net [54.240.184.51]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.2.254
2 5 ms 1 ms 1 ms static.kpn.net [xxx.xxx.xxx.xxx]
3 3 ms 3 ms 3 ms nl-asd-dc2-git-cr03.kpn.net [213.75.1.81]
4 2 ms 4 ms 3 ms nl-asd-dc2-ice-ir01.kpn.net [213.75.1.80]
5 1 ms 1 ms 1 ms asd2-rou-1022.NL.eurorings.net [134.222.93.138]
6 2 ms 1 ms 1 ms asd2-rou-1043.NL.eurorings.net [134.222.48.223]
7 2 ms 2 ms 2 ms asd-s17-rou-1041.NL.eurorings.net [134.222.48.235]
8 2 ms 2 ms 3 ms 72.21.221.100
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 2 ms 2 ms 2 ms server-54-240-184-51.ams50.r.cloudfront.net [54.240.184.51]

Trace complete.

Starting tracert for client.eveonline.com

Tracing route to client.eveonline.com [87.237.39.208]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.2.254
2 1 ms 1 ms 1 ms static.kpn.net [xxx.xxx.xxx.xxx]
3 9 ms 7 ms 7 ms nl-zl-dc2-git-cr02.kpn.net [213.75.64.237]
4 7 ms 7 ms 7 ms nl-rt-dc2-ice-ir01.kpn.net [213.75.64.236]
5 6 ms 6 ms 6 ms rt2-rou-1022.kpn.net [193.172.66.222]
6 12 ms 11 ms 11 ms ldn-s2-rou-1101.UK.eurorings.net [134.222.48.200]
7 134.222.109.115 reports: Destination net unreachable.

Trace complete.

Traceroute diagnostics finished


Any insight would be appreciated.
lmmortalist
lmmortality Associates
#2 - 2016-01-06 22:45:31 UTC
Whereas I have no idea of the possible involvement of the launcher, I've heard several people complaining about continuous socket closed -errors over the past few weeks (basically appeared out of nowhere), and the same goes for me too. It's really annoying and getting up to the point where I find it impossible to believe it has anything to do with my ISP / connection.
CCP Snorlax
C C P
C C P Alliance
#3 - 2016-01-07 15:32:02 UTC
Do these errors stop occurring if you close down the launcher after starting up the clients?

CCP Snorlax - Software Architect - Team RnB - @CCP_Snorlax - http://ccpsnorlax.blogspot.is/
GoTspeed
Doomheim
#4 - 2016-01-07 19:41:07 UTC  |  Edited by: GoTspeed
Since the end of December I have the same problems as the topicstarter and several corpmembers with me.
My provider is Telfort, a daughter ISP from KPN Netherlands (same as the topicstarter)

The problem occurs several times a day out of the sudden. We just disconnect and lately I dont even get a message anymore, but I have to close the client via the taskmanager.

Ive followed the suggestion from the dev to check what happens with a closed launcher, but we dropped with a few members just 10 minutes ago even with closed launchers.

A corpmember even contacted the ISP, but they didnt want to take the question to KPN for investigation, so we're kinda stuck here.

Never had any problems before playing EVE.
Flekkie
Native Freshfood
#5 - 2016-01-07 19:51:49 UTC
Hi,

I have had use the exe flile and not the launcher to avoid issues, i also dc with the socked closed message at the same time GoTspeed did on only 1 of the 3 clients.

Yes, i contacted telfort and they wont help me and they dont sent a msg to kpn to notice about it.

Also got a responces from a GM that he will ask a network admin.

Flekkie

...
Jeven HouseBenyo
Vanity Thy Name Is
#6 - 2016-01-09 00:29:20 UTC
CCP Snorlax wrote:
Do these errors stop occurring if you close down the launcher after starting up the clients?


No. They keep happening on no specific timing or setting even though I have the Launcher set to close after the client starts.

>Jeven

Minny boat flyer, unofficial squeaky wheel.

'Game Ethics and Morality Monitor' I remember promises.

Snark at 11-24/7/365.25. Overshare? Yup.

Yes it's my fault. And if you don't staap it I'll do it again. ;-P

No you can't has my stuffs OR my SPs.
Airi Kitamura
Doomheim
#7 - 2016-01-09 11:13:01 UTC  |  Edited by: Airi Kitamura
CCP Snorlax wrote:
Do these errors stop occurring if you close down the launcher after starting up the clients?


No difference when I close the launcher.

Even though I also connect through KPN (like above poster Telfort), I highly doubt it is the ISP.

As said, I played for half a day with 3 individual clients open. (without any issues)
I read about the launcher, and reinstalled mid-day. After that the problem started occurring.

I have found that when the client appears to be hanging, switching to another client sometimes makes the first client re-connect.
Basically the behaviour changes from a disconnect to a lagspike.

I am 100% sure this is due to the way the three clients interact with eachother.
Airi Kitamura
Doomheim
#8 - 2016-01-09 11:14:15 UTC  |  Edited by: Airi Kitamura
Above workaround only works in less than 50% of occurrences.
Airi Kitamura
Doomheim
#9 - 2016-01-10 13:15:38 UTC
Update:

Moving the SharedCache to a different drive from the main install may have fixed my issue.

I have ran several hours without disconnecting. Both with launcher open and closed.
(EU Prime Time last night and this morning. All three clients open.)
YourDeathAngel
The Legion of Spoon
Curatores Veritatis Alliance
#10 - 2016-01-10 20:45:51 UTC
Since end of Dec 2015, experiencing also repeated socket closure pretty much after logging in, making it impossible to even start playing. Everything else besides eve works fine and connectivity testing sites indicate v good ping/0 packet loss to servers in the UK at the same time the socket closures happen. Maybe after an hour of closing/restarting launcher it stops closing but that's not how one is expecting to play a subscription game.
Airi Kitamura
Doomheim
#11 - 2016-01-10 22:26:46 UTC
Airi Kitamura wrote:
Update:

Moving the SharedCache to a different drive from the main install may have fixed my issue.

I have ran several hours without disconnecting. Both with launcher open and closed.
(EU Prime Time last night and this morning. All three clients open.)



Problem has returned again tonight.
H0lmes
Federal Navy Academy
Gallente Federation
#12 - 2016-01-11 14:04:08 UTC  |  Edited by: H0lmes
Getting Socket closed here too with the Launcher. Seems to be random with moments where 6 accounts crash to moments where only 1 out of 3-6 crash. ISP is KPN in the Netherlands. Internet connection is stable. Also experiencing UI Lag specially in Jita and while going out of warp and other things in space it seems that i am Teleporting over the place a bit. so one moment i'm landing on the gate split second later i am 100km off warping to the gate again. kinda awkward as i do tend to scout and tackle for fleets.

Reinstallation of the Launcher was unsuccessful and clearing the logs did not change anything either. i did notice that after a december patch of the Launcher it is struggling with Rights on my PC even if i try to run the fix permissions it will simply hang and do nothing. If i close down the Launcher and i need another account online for a Cyno for example i need to close down every client reopen the launcher let if verify and then start up all characters again.
Airi Kitamura
Doomheim
#13 - 2016-01-11 14:20:42 UTC
H0lmes wrote:
Getting Socket closed here too with the Launcher. Seems to be random with moments where 6 accounts crash to moments where only 1 out of 3-6 crash. ISP is KPN in the Netherlands. Internet connection is stable. Also experiencing UI Lag specially in Jita and while going out of warp and other things in space it seems that i am Teleporting over the place a bit.


Very similar situation here. I have noticed some mini lagspikes and UI lag. After disconnecting one time, I ended up 2 gates before the one I was jumping before disconnecting.


H0lmes wrote:
Reinstallation of the Launcher was unsuccessful and clearing the logs did not change anything either. i did notice that after a december patch of the Launcher it is struggling with Rights on my PC even if i try to run the fix permissions it will simply hang and do nothing. If i close down the Launcher and i need another account online for a Cyno for example i need to close down every client reopen the launcher let if verify and then start up all characters again.


I also re-installed from scratch and noticed no change. I have a similar issue with the launcher, but only when my main account (main profile) is active. All other accounts are on a different profile (Alt_profile_A / Alt_Profile_B).
When these crash I can simply restart the clients through the launcher.
If the main account crashes, I have to restart all of them.
H0lmes
Federal Navy Academy
Gallente Federation
#14 - 2016-01-11 14:35:54 UTC
Forgot to mention i run on Windows 10. More in my Corp use the launcher and windows 10 without issue's but hey it might be a combination? Seen weirder stuff happen ;)
Hav0cide
The Graduates
The Initiative.
#15 - 2016-01-11 14:51:34 UTC
Socket closed errors are getting more frequent and more frustrating. Today I am unable to login for any length of time due to it happening very quickly. Some days it is worse than others. Last night I managed to play just fine till the late night time.

My ISP is Virgin Media cable 200mb/s internet and I have spoke to them, there is no issues with my connection. CCP have confirmed no issues their side but potentially somewhere between the two.

This all started in December and is getting more and more frequently yet every other internet app/game/connection works as normal.

The Sadistic Clowns - Recruiting new players who want to learn PVP/PVE/Exploration. Join our channel - 'Clowns recruits'
H0lmes
Federal Navy Academy
Gallente Federation
#16 - 2016-01-11 16:03:43 UTC
Also getting this with the old Launcher.
Crimson optimus
Dutch Legions
Solyaris Chtonium
#17 - 2016-01-11 16:07:15 UTC
today t3 x socked close disconnection, i have cabel internet .
H0lmes
Federal Navy Academy
Gallente Federation
#18 - 2016-01-11 16:27:42 UTC
Hope this gets resolved soon as its pretty much unplayable with this going on. Just disconnected again on all clients and I simply don't even want to login any more.
Teinyhr
Ourumur
#19 - 2016-01-11 16:33:04 UTC
Have the same issue as the OP with practically identical logs, everything works fine until the client part where it simply cannot for some reason connect. Usually this lasts only a minute at most, but it is most annoying and obviously can potentially be deadly at the wrong time, luckily I've only been ship spinning and flying in hi-sec when it has happened.
Donald MacRury
LankTech
#20 - 2016-01-11 17:32:20 UTC
I'm getting the same problem as others here. Started shortly after getting the new launcher in late December. Frequent socket is closed errors, at least once a day at random times and some days is worse than others. Everything else works on my internet perfectly fine when this happens and my isp says there is nothing wrong on their end.

I have ran several tracerts in the diagnostic tools in the launcher and usually when I have this problem there are disruptions but always on networks between my isp and ccp.
123Next pageLast page