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.
 

possible fix for Closed Socket error.

First post
Author
Previous Topic Next Topic
Nicaragua
Federal Navy Academy
Gallente Federation
#61 - 2012-06-24 07:16:51 UTC
I get a socket closed about 3 or 4 times an hour, its cost me a fortune in lost drones and the occasional ship - which CCP wont reimburse.
Malakoma
HyperQuest Corp
#62 - 2012-06-24 10:02:10 UTC
Nicaragua wrote:
I get a socket closed about 3 or 4 times an hour, its cost me a fortune in lost drones and the occasional ship - which CCP wont reimburse.

As I'm mining my losses so far have only been ore and my time. I'm not sure how other players would see my ship when the socket close occurs. Fortunately my defense drones have all reappeared back in the drone bay so none lost so far.

However, even without losses it still ruins game play Straight
Piquet Raddei
Royal Amarr Institute
Amarr Empire
#63 - 2012-06-25 12:53:42 UTC
STOP CLOSING MY SOCKETS!!

It got irritating enough that now I'm here, posting as well.

East Coast, Pennsylvania, Pittsburgh. I'm getting the "closed socket" disconnect both at work (I believe the ISP is Verizon Fios) AND at home, ISP is Comcast "Xfinity". Was NEVER getting this before, now I'll have all 5 accounts booted all at once. FRUSTRATING!!!

I have no idea how to do a trace, so if someone can tell me how/when/where, I'll see if I can mess with it.
Malakoma
HyperQuest Corp
#64 - 2012-06-25 15:51:35 UTC
I'm back again as socket still closing even after today's Inferno 1.1 update.

Such a disappointment as for me Eve is unplayable Cry

Guess I'll have to try and search tor a solution in the forums and on web.
Sanya
Alexylva Paradox
#65 - 2012-06-25 19:30:16 UTC  |  Edited by: Sanya
I only used to get this if I would start League of Legends while EVE was running. After todays patch, it happens much more frequently. More so after I undock (almost always within 1 minute). Typical example is undocking, warping to gate, then I never get to jump.

Can also happen right after I go into, or out of windowed mode (during the change.) This could simply be that the error window doesn't show until I switch windowed mode.

.
HeyImStuck
Pandemic Horde Inc.
Pandemic Horde
#66 - 2012-06-25 20:44:22 UTC
CCP Sputnik wrote:
Sione Tolutau wrote:
Hi guys sorry I've posted this in another thread but I am having the exact same issue
Location: New Zealand
ISP: slingshot

I don't have any packet loss when it happens for me. ping -t was this at all times from log in to "Socket was closed":
Reply from 87.237.38.200: bytes=32 time=301ms TTL=108

and tracert was this:

2 11 ms 11 ms 11 ms cpiak1-l9-G-internet.tranzpeer.net [202.180.81.32]
3 12 ms 10 ms 11 ms vlan93-cpcak3-e1.tranzpeer.net [202.180.76.68]
4 11 ms 11 ms 10 ms vlan7-cpcak3-s1.tranzpeer.net [202.180.81.49]
5 44 ms 11 ms 12 ms x7-1-0-101.akbr5.global-gateway.net.nz [202.50.234.61]
6 12 ms 11 ms 12 ms ae1-2.akbr4.global-gateway.net.nz [202.50.232.77]
7 12 ms 12 ms 11 ms ae1-10.tkbr9.global-gateway.net.nz [202.50.232.37]
8 135 ms 142 ms 136 ms xe7-0-0.labr5.global-gateway.net.nz [202.50.232.18]
9 168 ms 167 ms 173 ms ae1-3.sjbr2.global-gateway.net.nz [203.96.120.94]
10 167 ms 169 ms 149 ms ae0.pabr4.global-gateway.net.nz [203.96.120.74]
11 169 ms 168 ms 138 ms vlan60.csw1.SanJose1.Level3.net [4.69.152.62]
12 146 ms 147 ms 149 ms vlan60.csw1.SanJose1.Level3.net [4.69.152.62]
13 141 ms 141 ms 211 ms ae-2-2.ebr2.NewYork1.Level3.net [4.69.135.186]
14 208 ms 211 ms 205 ms ae-92-92.csw4.NewYork1.Level3.net [4.69.148.46]
15 220 ms 209 ms 212 ms ae-92-92.csw4.NewYork1.Level3.net [4.69.148.46]
16 274 ms 208 ms 208 ms ae-91-91.ebr1.NewYork1.Level3.net [4.69.134.77]
17 285 ms 278 ms 284 ms ae-56-221.csw2.London1.Level3.net [4.69.153.130]
18 274 ms 273 ms 278 ms ae-56-221.csw2.London1.Level3.net [4.69.153.130]
19 * 273 ms 277 ms ae-2-52.edge4.London1.Level3.net [4.69.139.106]
20 278 ms 283 ms 302 ms srv248-e.ccp.cc [87.237.36.248]
21 305 ms 311 ms 307 ms srv248-e.ccp.cc [87.237.36.248]
22 307 ms 302 ms 312 ms srv200-g.ccp.cc [87.237.38.200]

hope this helps..


Thank you Sione Tolutau.

I wanted to highlight your post to show people which information they should include in their petitions about the socket closed issue. Having all this information makes it a lot easier for us to figure out who, in this long trace, is responsible for dropping the ball/package.

PS. You might not see the package loss via ping -t if only packages within specific port rages get dropped.



While your computer generates some records, these records are generated client side and are not considered conclusive regarding reimbursement. According to our records, your ------- was killed at 20:30:52 and your pod was lost at 20:30:59. Any discrepancies with your own record of events indicates an issue either with your EVE client, your local computer's hardware or software, your local internet connection or third party hardware or software between the game server and your local client. Unfortunately, such issues are not eligible for reimbursement.

Explain that please dev. you provide evidence they tell you" While your computer generates some records, these records are generated client side and are not considered conclusive regarding reimbursement." Petition denied.
Sirius Deinhardt
Money Crew
Stain Neurodiverse Democracy
#67 - 2012-06-26 01:54:32 UTC
I usually get socket resets every 15 min, but at the moment its immediate. I have enough time to get my drones out but never enough time to make it into a station :(

I've been playing for 7 months or so? Only had one disconnect until the Inferno release. Now its unplayable. Hope this info helps, can't wait to get playing again. This game rocks!


C:\>tracert 87.237.38.200

Tracing route to srv200-g.ccp.cc [87.237.38.200]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.1.254
2 * * * Request timed out.
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 537 ms 447 ms 332 ms srv200-g.ccp.cc [87.237.38.200]

Trace complete.

see that trace route? LOL
I traced 4 times, it only ever makes it on the 12th attempt. Maybe there is something wrong on my end? I'm not too good with this kind of stuff, if anyone has any suggestions for me I'd appreciate it.
Darkside KmS
Tea And Sympathy Ltd. Liability
#68 - 2012-06-26 07:40:53 UTC  |  Edited by: Darkside KmS
I am also now getting this same problem. I can't even play. I just got back into eve and I am now wishing I had not paid for a 3 month sub. This is really getting on my nerves.

Going to do some packet sniffing and try and see if I can figure out what is going on.

I reset my modem / router and that did not fix the problem. Log in and sometimes I get the error before I even get in station/space.

Edit: My local ip changed and the port 26000 wasn't being forwarded, so far no d/c if I don't get any more I will post back. Everyone else should also make sure their port 26000 is forwarded to their computers local ips.
Malakoma
HyperQuest Corp
#69 - 2012-06-26 10:17:12 UTC
I've tried tracing as some other posters have done and my results are:-

C:\Documents and Settings\Administrator>tracert 87.237.38.200

Tracing route to srv200-g.ccp.cc [87.237.38.200]
over a maximum of 30 hops:

1 100 ms 99 ms 99 ms 192.168.1.254
2 * * * Request timed out.
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 35 ms 40 ms 31 ms ethernet21-4.ar9.lon3.gblx.net [64.212.34.97]
7 70 ms 31 ms 31 ms ae5.scr3.LON3.gblx.net [67.17.72.22]
8 31 ms 31 ms 30 ms te7-4-10G.ar6.LON3.gblx.net [67.16.144.249]
9 32 ms 31 ms 32 ms 204.245.39.42
10 31 ms 30 ms 30 ms srv245-e.ccp.cc [87.237.36.245]
11 31 ms 31 ms 31 ms srv248-e.ccp.cc [87.237.36.248]
12 32 ms 30 ms 30 ms srv200-g.ccp.cc [87.237.38.200]

Trace complete.


Here is a ping result:-

C:\Documents and Settings\Administrator>ping 87.237.38.200

Pinging 87.237.38.200 with 32 bytes of data:

Reply from 87.237.38.200: bytes=32 time=31ms TTL=115
Reply from 87.237.38.200: bytes=32 time=30ms TTL=115
Reply from 87.237.38.200: bytes=32 time=30ms TTL=115
Reply from 87.237.38.200: bytes=32 time=30ms TTL=115

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


Frankly I'm not into networks so don't really understand the "request timed out" part of this.
By the way, to simplify things i removed network bridge and tested with just router and no other computers sharing it.


I have filed a petition with CCP and included links to these threads. Hopefully CCP will give some helpful feedback before my subscription comes up for renewal in a few days time.


Crysantos Callahan
Imperial Shipment
Amarr Empire
#70 - 2012-06-26 13:42:48 UTC
Never had any issues, now I can't even connect. 1h after DT I get perma dc'ed due to "socket closed", sometimes it starts a short time but shuts down after 10-20 seconds. Nothing changed on my end, check ISP and router, too -.-
Anastasius Steiner
Science and Trade Institute
Caldari State
#71 - 2012-06-27 08:23:43 UTC
I have the same "Connection Lost" "The Socket was closed" Problem.

It all started after the Installation of the Inferno Patch.
All Workarounds (closing Steam, etc ... ) wont work.

As long as i do/clcik smth i am fine. but the moment i went "afk", it closes my Client.


A Hotfix for it would be quite nice, cause its non playable the way it is atm!
Bjurn Akely
The Scope
Gallente Federation
#72 - 2012-06-27 19:11:04 UTC  |  Edited by: Bjurn Akely
I've edited this post.

Last night we discovered our land (telephone) line was acting up, only to die completely later in the evening. I've talked to the service provider and they are having a problem with a major cable.

This is a telia.com cable located somewhere in the middle of Sweden (sorry could not get more info). My problem is probably due to that. Perhaps others too if they are routed through Sweden. So I left my Tracert down there.

Once the cable is repaired (5th of July they said) I'll re-edit this to report back if the Socket Closed error persists or not.



Quote:
Yeah.

Happens a lot. Not good as I'm usually cloaked somewhere dangerous. Cry

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.


C:\Users\x>tracert 87.237.38.200

Tracing route to srv200-g.ccp.cc [87.237.38.200]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms READYSHARE [10.10.10.1]
2 197 ms 159 ms 5 ms gw2-no193.tbcn.telia.com [62.20.221.1]
3 6 ms 6 ms 6 ms s-b1-link.telia.net [80.91.248.195]
4 6 ms 6 ms 7 ms s-bb2-link.telia.net [80.91.254.110]
5 32 ms 23 ms 24 ms hbg-bb1-link.telia.net [80.239.147.166]
6 35 ms 35 ms 35 ms ldn-bb2-link.telia.net [80.91.250.223]
7 33 ms 35 ms 32 ms ldn-b3-link.telia.net [80.91.245.27]
8 51 ms 199 ms 203 ms eveonline-ic-138015-ldn-b3.c.telia.net [213.248.
83.198]
9 38 ms 37 ms 38 ms srv248-e.ccp.cc [87.237.36.248]
10 35 ms 35 ms 38 ms srv200-g.ccp.cc [87.237.38.200]

Trace complete.
Malakoma
HyperQuest Corp
#73 - 2012-06-27 19:16:42 UTC
Anastasius Steiner wrote:
I have the same "Connection Lost" "The Socket was closed" Problem.

It all started after the Installation of the Inferno Patch.
All Workarounds (closing Steam, etc ... ) wont work.

As long as i do/clcik smth i am fine. but the moment i went "afk", it closes my Client.


A Hotfix for it would be quite nice, cause its non playable the way it is atm!


Thanks for the info about doing something (clicking) that keeps it working for you.

I'm testing a mouse mover utility and so far have received no socket closed dialog boxes for the past 3 hours even though my ship is sitting cloaked in a safe spot and I haven't touched the mouse or keyboard during this period. Normally it would give a socket closed error between a few minutes to an hour max.
The mouse mover just moves the mouse to a random position every 10 seconds although perhaps a minute or more might work.

This fix, if it works, won't be to everyone's liking. I'm often mining and have to interact with the ship at least every 6 minutes or the mining lasers stop working. Anyhow I'm going to keep this test on overnight to see if it works.

Will be great when a fix comes out because these socket closed errors are making Eve unplayable.

I'm not sure if socket closed errors occur when docked?
Def Monk
Phoenix Naval Operations
Phoenix Naval Systems
#74 - 2012-06-27 21:47:03 UTC
Hey all. Just wanted to mention I've been having this issue as well lately (couldn't log in since the update last night). I was reading through the thread and saw other people were having issues with steam running in the background. I went through my current processes to see what could cause it (steam wasn't running) and so I figured I'd try anything else that may be using the network.

First thing I tried was Hi-Rez Studios' Update Manager for Tribes: Ascend. This instantly fixed the issue, but what confused me was the process should not be running (I have auto-update off). My guess is that is uses the same process to update by hand as well, and just runs it when starting the game and the process got left at some point. I can't explain the interference between Eve & this updater, but it seems to be (in my case) caused by networking processes being left open.

If you lock your computer a lot or have had an online program crash (which could, in theory, cause it to keep attempting to use the network), try rebooting your machine entirely (cold boot - shut down, wait a few seconds, start back up) or (if you know what you're doing) search/end your processes to see if you can find what else causes the issue.

Hope you can figure this one out CCP! If I continue to have the issue in the future, I'll bring you more information then. If you are interested now, I live on a college campus in north New Jersey, so they act as my ISP.

Quote:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\Def_Monk>tracert 87.237.38.200

Tracing route to srv200-g.ccp.cc [87.237.38.200]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms Vlan206.cc.stevens-tech.edu [155.246.70.1]
2 * * * Request timed out.
3 1 ms 1 ms 1 ms ge-8-37.car1.Newark1.Level3.net [4.28.0.173]
4 12 ms 1 ms 1 ms ae-31-51.ebr1.Newark1.Level3.net [4.69.156.30]
5 1 ms 1 ms 2 ms ae-2-2.ebr1.NewYork1.Level3.net [4.69.132.97]
6 70 ms 70 ms 70 ms ae-42-42.ebr2.London1.Level3.net [4.69.137.69]
7 79 ms 74 ms 74 ms ae-58-223.csw2.London1.Level3.net [4.69.153.138]
8 70 ms 70 ms 70 ms ae-2-52.edge4.London1.Level3.net [4.69.139.106]
9 70 ms 70 ms 70 ms 195.50.122.214
10 70 ms 71 ms 70 ms srv248-e.ccp.cc [87.237.36.248]
11 70 ms 70 ms 72 ms srv200-g.ccp.cc [87.237.38.200]

Trace complete.

C:\Users\Def_Monk>tracert 87.237.38.200

Tracing route to srv200-g.ccp.cc [87.237.38.200]
over a maximum of 30 hops:

1 2 ms 1 ms 2 ms Vlan206.cc.stevens-tech.edu [155.246.70.1]
2 * * * Request timed out.
3 35 ms 3 ms 28 ms ge-8-37.car1.Newark1.Level3.net [4.28.0.173]
4 1 ms 1 ms 12 ms ae-31-51.ebr1.Newark1.Level3.net [4.69.156.30]
5 1 ms 1 ms 3 ms ae-2-2.ebr1.NewYork1.Level3.net [4.69.132.97]
6 71 ms 70 ms 70 ms ae-42-42.ebr2.London1.Level3.net [4.69.137.69]
7 70 ms 70 ms 72 ms ae-58-223.csw2.London1.Level3.net [4.69.153.138]
8 * 70 ms 70 ms ae-2-52.edge4.London1.Level3.net [4.69.139.106]
9 70 ms 70 ms 70 ms 195.50.122.214
10 70 ms 70 ms 70 ms srv248-e.ccp.cc [87.237.36.248]
11 70 ms 70 ms 70 ms srv200-g.ccp.cc [87.237.38.200]

Trace complete.

C:\Users\Def_Monk>tracert google.com

Tracing route to google.com [173.194.43.14]
over a maximum of 30 hops:

1 3 ms 2 ms 3 ms Vlan206.cc.stevens-tech.edu [155.246.70.1]
2 * * * Request timed out.
3 1 ms 1 ms 1 ms ge-8-37.car1.Newark1.Level3.net [4.28.0.173]
4 7 ms 1 ms 1 ms ae-31-51.ebr1.Newark1.Level3.net [4.69.156.30]
5 2 ms 3 ms 1 ms ae-2-2.ebr1.NewYork1.Level3.net [4.69.132.97]
6 1 ms 1 ms 2 ms ae-81-81.csw3.NewYork1.Level3.net [4.69.134.74]
7 1 ms 1 ms 1 ms ae-3-80.edge1.NewYork1.Level3.net [4.69.155.142]
8 1 ms 1 ms 1 ms GOOGLE-INC.edge1.NewYork1.Level3.net [4.71.172.86]
9 2 ms 1 ms 2 ms 209.85.255.68
10 2 ms 2 ms 2 ms 72.14.237.252
11 1 ms 1 ms 1 ms lga15s34-in-f14.1e100.net [173.194.43.14]

Trace complete.

C:\Users\Def_Monk>


As you can see, the timeout at part 2 is consistent, and happens regardless of destination. My college's network setup can be admittedly bad. Running Win7 64-bit. If you guys need anything else, let me know.
arcca jeth
Dark Alliance
#75 - 2012-06-28 00:20:12 UTC
last night was fine, today there was a quick patch. now getting "socket closed" error as well.

Houston, TX US
ISP: Comcast
Malakoma
HyperQuest Corp
#76 - 2012-06-28 05:46:56 UTC
Malakoma wrote:
Anastasius Steiner wrote:
I have the same "Connection Lost" "The Socket was closed" Problem.

It all started after the Installation of the Inferno Patch.
All Workarounds (closing Steam, etc ... ) wont work.

As long as i do/clcik smth i am fine. but the moment i went "afk", it closes my Client.


A Hotfix for it would be quite nice, cause its non playable the way it is atm!


Thanks for the info about doing something (clicking) that keeps it working for you.

I'm testing a mouse mover utility and so far have received no socket closed dialog boxes for the past 3 hours even though my ship is sitting cloaked in a safe spot and I haven't touched the mouse or keyboard during this period. Normally it would give a socket closed error between a few minutes to an hour max.
The mouse mover just moves the mouse to a random position every 10 seconds although perhaps a minute or more might work.

This fix, if it works, won't be to everyone's liking. I'm often mining and have to interact with the ship at least every 6 minutes or the mining lasers stop working. Anyhow I'm going to keep this test on overnight to see if it works.

Will be great when a fix comes out because these socket closed errors are making Eve unplayable.

I'm not sure if socket closed errors occur when docked?




Well my idea didn't seem to work as Socket Closes seem connected with actual in-world activity and not with lack of activity.

Mouse mover kept client alive with no Socket Closes for over 12 hours.
I then tried to let client sit for 25 minutes with no KB or mouse interaction at all - result was no Socket Closes.
Next decided to try some mining but with out mouse mover - result after 40 minutes Socket Close !!!
Bjurn Akely
The Scope
Gallente Federation
#77 - 2012-06-28 08:53:46 UTC
Last night we discovered our land (telephone) line was acting up, only to die completely later in the evening. I've talked to the service provider and they are having a problem with a major cable.

This is a telia.com cable located somewhere in the middle of Sweden (sorry could not get more info). My problem is probably due to that. Perhaps others too if they are routed through Sweden. So I left my Tracert in my original post.

Once the cable is repaired (5th of July they said) I'll re-edit this to report back if the Socket Closed error persists or not.
arcca jeth
Dark Alliance
#78 - 2012-06-28 20:49:28 UTC
I reset my modem, rebooted my computer and killed the steam process, socket closed continued all night. Couldn't play so I quit and gave up. I really hope a patch was released to day so I can actually play when I get off work.

This was not an issue until yesterdays "quick fix" patch. So I cannot help but think that it was something to do with that.
Anastasius Steiner
Science and Trade Institute
Caldari State
#79 - 2012-06-28 21:48:21 UTC
all patches are worthless ...

as soon as i dont move my mouse, i get dcd ... with progs like mosuemover, i can stay idle ...

but after all, it sucks ... eve is unplayabe atm ,,,
Wraiths Crono
Iridium Incorporated
#80 - 2012-06-28 22:00:38 UTC  |  Edited by: Wraiths Crono
Hi, not at home for a trace at the moment, but I only seem to get the socket closed when running two clients. Ill update with a screen cap asap. Also Noticing for the US people that the connection over Level3 and some the ASH Virginia datacenter connection, could it be the international trunk hitting a capacity or just dropping off.. (Worked for Bandcon a business ISP that resold Level 3 waves so I got to know that they could be flaky in in Virginina)