Issues, Workarounds & Localization

I started having this problem yesterday.
When the socket error happens all other internet based programs close/stop working for a micro second then start right back up.

ISP: Rogers Communications Inc
Location: Toronto, Canada

I am getting the socked closed error since the odyssey release. I play since august last year and never had any trouble till odyssey was released.

I can confirm that the socked closed happens with and without steam - as i suspected that as a reason myself and started eve without steam several times, but had the same result: a socket closed error.


I can furthermore confirm that it seems not to be connection or ISP based cause i run 2 different machines, and one runs fine all the time, the other gets socket closed errors all the time since odyssey. Just to make sure i also exchanged all cables on my end, to make sure it is no problem of that. Both connections are wire/cable based, so it is no wireless issue either.

As the one machine runs super fine for hours without any trouble, uses the same ISP (obviously) and the same router, i would pretty much say i can exclude those from being the trouble makers.
So why does it run fine for a year.. odyssey comes out.. and i have socket cloed errors? On one machine and not the other? Definately no ISP/router issue at all!! Otherwise both my machines would get kicked out at the same time (as they are also in the same system, using the same "part of the cluster server").


The always running machine still uses old windows xp with a 32bit OS, the other one runs windows 7 in a 64bit version.


The issue seemed to be solved for some time when i was running my EVE client in admin modus on the windows 7 version, i could play several days without issues. Then Odyssey was patched, and the issues returned. Could not get rid of them since. They can be pretty annoying as they hit randomly without any warning. Not all too nice if you fly through hostile territory (as i did to take the screenshots of "steve" for the sanctuary image contest - had the socket closed at least 4 times on that route... it for sure caused super huge adrenaline rushes.. lol

Ok back on topic and some ideas/hints:

• I have been wondering if a localized client could cause trouble in whatever way? Many of my corpmates who all use the localized client have the same trouble


• Some right/service conflicts with windows 7 maybe, as my XP machine seems to run fine. Also cause i was able to fix the issue for some time with using admin mode on windows 7 - unfortunately it is now back even with admin mode. Are windows 7 network quality services maybe more time critical? Or causing the network packets to behave differently than on windows xp machines?


• I heard one of my corpmates say that adding fleetmembers to the watchlist caused him to get socket closed errors all the time. Since he is not using this feature anymore, he is not getting socket closed errors anymore. So maybe it is just specific data or the client side interpretation of it?


• as noted by someone else before in this thread, i also always get 2 socked closed error windows whenever it occurs

Wish i could provide a lot more information - but i think confirming that it may NOT be isp/router/connection based at all, may bring the research in a different direction, and may help finding its actual source.

I've been having this issues ONLY since the release of Odyssey. Before Odyssey I don't remember a single event involving lost sockets.

I've tried changing settings in my router, rebooted router and modem several times, sent a constant stream of pings to google.com to insure I've not lost connection to the actual internet. I'm connected via charter communications and I don't see anything in the windows event log either.

Considering the apparent common occurance (and frequent)of this problem, I find it impossible to believe that it's an 'ISP' problem - also considering my issues didn't exist pre-Odyssey. Something with this expansion is broken and causing problems .. and I can't fix it on my end.

I am still keep having the same issue.

Even worst these last 2 days, it happens like every 10 - 15 Minutes. It starts to be VERY annoying.


Now like 20 minutes ago i have had the CCP Server log Application running in the background, and SURE as hell, after 10 minutes of being logged in, the Socket was closed again.

looking at the server log application, it states the following at the moment the socket closed:



50403 2013.07.25 12:49:19:155 Sending event: ship_effect_jumpdrive_out_play to game object 999 (effect_1010196060716_effects.JumpOut)
50404 2013.07.25 12:49:19:300 Closing connection to 87.237.38.200:26000: {'reasonCode': None, 'reason': u'The socket was closed', 'exception': error(10054, 'An existing connection was forcibly closed by the remote host'), 'reasonArgs': {}}
50405 2013.07.25 12:49:19:301 Exception during MachoTransport::Close ignored.
50406 2013.07.25 12:49:19:301 Creating Closed Packet: The socket was closed exception:error(10054, 'An existing connection was forcibly closed by the remote host')
50407 2013.07.25 12:49:19:301 Couldn't send close packet, rhe socket is probably already closed. [Errno 10054] An existing connection was forcibly closed by the remote host: 'descriptor not alive'


The list goes on .... and on ... and on,

but i dont want to swarm the forum with the whole thing.

I want to send the entire fille together with a petition or a bug report.

Lets see what happens.

I dont use e-mule

Just started for me after downtime today. Onto my 5th socket disconnect in a few hours.

I don't have another other programs to kill off, it is a lean gaming rig, I know all the processing that are running, and have most services disabled. Downloaders and things are on my "communication rig"

I did find an NVidia update error in the Windows Event logs so will see if killing this service fixes it. The service was on delayed start and when the system tried to run it the socket error triggered.

When I tried to run Nvidia update manually it errored out while loading the program... so I hope that was the problem

Edit: Will see if that fixed it. Just killed off my drivers and replaced my Nvidia with an updated Beta

Edit: Update: Didn't get a disconnect yet but only played a few hours

Still getting too many disconnects. Some days are fine but mostly the just after dinner time zone is very risky.

Just moved from ADSL2 to cable 6 weeks ago. The disconnects started about 4 weeks after the move.

Have had technicians out from my ISP twice now. I think they won't tell me the problem, as in I think it is a network issue they won't admit to. They say there is no problem.

From my point of view 2 - 5 disconnects every time I play EVE is a problem.

Both I think.. as in Eve seems quicker to decide it has disconnected when the uplink is lagged or something.

My ISP finally found a network problem that I think they knew about but didn't put priority on till I complained and asked for my money back.

But yes running 2 clients I have still had a disconnect on one but not the other, but only like 1 in long play sessions.

I have been experiencing these closed socket errors since I started playing a few weeks ago. Tried all the fixes I have found via the forums etc and none really help at all. Anyway, I recently took advantage of the buddy programme and I am running 2 clients at the same time. Two times this morning the socket close on one client whilst the other was fine. Must surely be an external issue?

There is one primary cause of this issue IMO: CCP hasn't built in an in-game algorithm that handles packet loss....or hasn't built it in well.

The indirect cause is a packet getting lost somewhere along the router train between CCP and your home. It only takes one router to get overloaded or misfire and not send the packet to you. You probably have an average of 20 routers the data goes through to get to and from CCP servers. Any one can fail. AND, they won't fail frequently. Considering the load they handle, you might lose one packet out of a million sent...but the desktop client can't handle that loss and instead loses connection to the open socket on CCP's servers.

What should be happening is the program determines it's not getting data any more, and signals (through pop up or notification) to the user that packet loss is occurring and lag could result. Then the program should automatically resend data and try to get the data stream working again. In my experience, I can tell I'm about to lose the connection because I can't issue commands any further...nothing in game reacts to my clicks beyond opening windows that won't load data.

Instead, what is happening is the socket gets closed, and the program shuts down. That's where the logic fails me. There should be some error handling built in to the desktop side to handle the network data loss and compensate. If it's even possible, CCP should run trace analysis on their end to determine lagging routers and identify ways around those routers.

I only get the lag during US East Coast business hours. At night and weekends, I'm fine. And it's not every day...so during high load times, the network uses a router that is faulty.

For those who have an error on one PC but not the other, that's because the router only lost data to your one machine. It's probably just by chance that it repeats to the same machine multiple times.