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.
 

Socket Closed - Launcher only

First post First post
Author
Previous Topic Next Topic
Luukje
The Vendetta Mercenaries
Vendetta Mercenary Group
#141 - 2016-03-02 18:11:22 UTC
Getting multiple socket closures again today. 8 and counting.
Aoi Litvyak
Doomheim
#142 - 2016-03-02 21:27:24 UTC
Stopped happening for me since the server switch, yayifications \o/
Hatori Roku'dan
Merch Industrial
Goonswarm Federation
#143 - 2016-03-02 21:42:07 UTC  |  Edited by: Hatori Roku'dan
My eve is broken beyond any fixing it looks like.

On patch day there were market issues called, i got two characters with markets so it could be issue.
After restarting server I couldnt log in for more than few seconds and I would either get Socked closed, or 5 minute load, or client would get stuck in middle of load.
Tried to reinstall several times and delete files but didnt work.
I did get error message which somebody mentioned earlier, the one with error code xxxxx-xxxxxxxx-xxxxxx- etc.
Nearly 72 hours after patch and still not working!
Reinstalled windows. Log in, works 10 minutes, then breaks again. Router restarted. Port switched as per instructions. Still same. 5 minutes load, game is not capable of holding me into servers for more than several minutes after i manage to log in during multiple socked closures after 30 minutes. I am at 8+ socket closures now and counting goes even higher

I am customer for more than 5 years and this is so far worst technical issue I have seen. I cant even pinpoint what is wrong with it since I got multiple issues, not just one.

EDIT: my eve client has experienced socket closed messages regularly over last few weeks, eversince this issue post started. I am badly surprised that this has been a real thing for two months now and CCP puts poker face on and simply release patch which breaks everything else.

I cant play the game, CCP charges me for game time and I found 0 fixing on this. Today I spent 4 hours looking how to fix problem during endless connects and socket closures I managed to play approx. 15 minutes or less of very unsatisfying gameplay.
Iguanoid
Ascendance
Goonswarm Federation
#144 - 2016-03-03 02:36:14 UTC
Have the same thing currently. Can log 2 accounts at the same time on both my desktop and laptop, and the same account gets socket closed error every 15 minutes more or less, while the second account sits all night in Jita without any issues. Always the same account gets the error on multiple machines and different OS - Windows 7 and 10, it makes no difference.
Morbush
Red Thanators
#145 - 2016-03-03 05:16:04 UTC
I have lost my ship on mission tonight because of this issue. It was not only the closed socket, I could not even log in for a few minutes. Looks like this is some kind of ddos-protection or similiar thing: I could successfully ping client.eveonline.com using estonian vpn, but direct ping has 100% packet loss.
Mr Mac
Dark Goliath
#146 - 2016-03-03 07:25:23 UTC
Seems better now after hardware upgrade on TQ

Thank you, CCP
Helios Anduath
The Scope
Gallente Federation
#147 - 2016-03-03 09:09:47 UTC
Morbush wrote:
I have lost my ship on mission tonight because of this issue. It was not only the closed socket, I could not even log in for a few minutes. Looks like this is some kind of ddos-protection or similiar thing: I could successfully ping client.eveonline.com using estonian vpn, but direct ping has 100% packet loss.


If you did a tracert to client.eveonline.com, where did it die? That should give you more of an idea where the issue lies.
Helios Anduath
The Scope
Gallente Federation
#148 - 2016-03-03 09:15:13 UTC
Hatori Roku'dan wrote:
My eve is broken beyond any fixing it looks like.

On patch day there were market issues called, i got two characters with markets so it could be issue.
After restarting server I couldnt log in for more than few seconds and I would either get Socked closed, or 5 minute load, or client would get stuck in middle of load.
Tried to reinstall several times and delete files but didnt work.
I did get error message which somebody mentioned earlier, the one with error code xxxxx-xxxxxxxx-xxxxxx- etc.
Nearly 72 hours after patch and still not working!
Reinstalled windows. Log in, works 10 minutes, then breaks again. Router restarted. Port switched as per instructions. Still same. 5 minutes load, game is not capable of holding me into servers for more than several minutes after i manage to log in during multiple socked closures after 30 minutes. I am at 8+ socket closures now and counting goes even higher

I am customer for more than 5 years and this is so far worst technical issue I have seen. I cant even pinpoint what is wrong with it since I got multiple issues, not just one.

EDIT: my eve client has experienced socket closed messages regularly over last few weeks, eversince this issue post started. I am badly surprised that this has been a real thing for two months now and CCP puts poker face on and simply release patch which breaks everything else.

I cant play the game, CCP charges me for game time and I found 0 fixing on this. Today I spent 4 hours looking how to fix problem during endless connects and socket closures I managed to play approx. 15 minutes or less of very unsatisfying gameplay.


What debugging have you tried? In my experience helping people with socket closeds, it is usually an ISP issue or a local setup issue. Issues between ISPs and CCP are also common. Issues on CCP's side do happen but these generally result in significant disconnects of players.

Who is your ISP and where in the world are you?

How are you connecting to your home network? Is it wifi or wired?

Does anything else stop working or slow does when you get socket closeds?

What does a tracert to client.eveonline.com show? Especially about the time you have issues. A program called Pingplotter can help automate this a bit if you leave it running while playing.
Aoi Litvyak
Doomheim
#149 - 2016-03-03 09:20:40 UTC  |  Edited by: Aoi Litvyak
Helios Anduath wrote:

What debugging have you tried? In my experience helping people with socket closeds, it is usually an ISP issue or a local setup issue. Issues between ISPs and CCP are also common. Issues on CCP's side do happen but these generally result in significant disconnects of players.

These issues are exclusively on CCPs side, if you run a single client? no sockets closed ever! If you run multiple clients all but one will get socket closed. If you shut down the launcher after starting the clients it gets socked closed way less.

For me it started happening with the database upgrade on the 24th, and ended on the database move that happend some days ago. Meanwhile my ISP is 100% healthy as usual and there was zero packet loss and such during the entire duration. But sure it must be my ISP that i couldnt multibox clients! Dont debunk others issues as "ISP problems". Its usually not.
Helios Anduath
The Scope
Gallente Federation
#150 - 2016-03-03 09:34:56 UTC  |  Edited by: Helios Anduath
Aoi Litvyak wrote:

These issues are exclusively on CCPs side, if you run a single client? no sockets closed ever! If you run multiple clients all but one will get socket closed. If you shut down the launcher after starting the clients it gets socked closed way less.

For me it started happening with the database upgrade on the 24th, and ended on the database move that happend some days ago. Meanwhile my ISP is 100% healthy as usual and there was zero packet loss and such during the entire duration. But sure it must be my ISP that i couldnt multibox clients! Dont debunk others issues as "ISP problems". Its usually not.


Because depending on how intermittent or borderline the issue is, one client can work ok but two clients can be just enough traffic to cause issues. Being undocked and active sends more data than a client sat in station doing nothing so what you are doing in game on multiple clients can increase or decreases the chance of a socket closed on a flakey connection.

Most people saying they get packet loss are having a local issue and if these people are jumping on the band wagon without completely ruling out local issues first, then it just clouds any real issue that CCP need to look into and fix.

If you re-read my post, I am not just blaming it on ISPs. Upstream connectivity has been an issue for some and hard-to-trace local issues for others. The other day I helped someone with socket closeds on a seemingly stable connection - turned out to be intermittent wifi issues. ISP problems with the ISP reporting no issues are not outside the realms of possibility for some people though - ISPs are notorious for letting intermittent/borderline issues slide for ages as it is within their accepted boundaries.

How have you established that you were having 0% packet loss?

EDITed to add: if there really are problems that CCP need to fix, and you want them fixed, why take issue with running more tests that should conclusively show it is CCP's problem if it is?
Aoi Litvyak
Doomheim
#151 - 2016-03-03 09:57:15 UTC  |  Edited by: Aoi Litvyak
Pingplotter running nonstop, 100/100Mbit/s Bahnhof connection in Sweden, zero issues, zero packet loss, zero lag, no pingpikes of any sort, no issues with anything except socket disconnected from EVE when multiboxing(and only from all but 1 client), no firewall issues, no ports closed. Its all EVE serverside issues.

Unless there is a bug where the launcher/client needs to write to some folder/file it does not have access to/shares with other clients, and try to write/read it at the same time and collides.
Helios Anduath
The Scope
Gallente Federation
#152 - 2016-03-03 11:30:31 UTC  |  Edited by: Helios Anduath
Pingplotter running nonstop to where? You may go "it's obvious, dummy" but I have seen people think that running a ping plotter to a website hosted in the same country is a good test.

Also, completely 100% success rate with absolutely no packet loss or ping variation anywhere along the entire route is something I would not expect.For example, I am on a several-hundred-meg syunchronous connection right now with average 5ms latency to client.eveonline.com but I still see minor latency spikes and packet loss on a couple of the level3.net routers on my path.

If there is an issue server-side, I am betting it will be an awkward one to diagnose as there are a significant number of people who have no problems.
pajedas
Doomheim
#153 - 2016-03-03 12:34:08 UTC
Helios Anduath wrote:
If there is an issue server-side, I am betting it will be an awkward one to diagnose as there are a significant number of people who have no problems.

PingPlotter gets to 213.155.133.3 (ldn-b3-link.telia.net) in Sweden and starts gettting huge packet loss.

How can I fix a problem in Sweden? I live in Kentucky, USA.

I have AT&T Wireless that runs 45-60 Mb/s.

Thanks for helping as it sounds like you know what you're talking about Big smile

🐇
Helios Anduath
The Scope
Gallente Federation
#154 - 2016-03-03 14:27:38 UTC
pajedas wrote:
PingPlotter gets to 213.155.133.3 (ldn-b3-link.telia.net) in Sweden and starts gettting huge packet loss.

How can I fix a problem in Sweden? I live in Kentucky, USA.


OK, so from the reverse DNS name on that (not always accurate), that node is probably in London. It probably geo-locates as Sweden as that is where the company are based.

When you say huge, how much and does it continue past the problem node? Packet loss at one node may just mean that one node is quite heavily loaded and is prioritising dealing with traffic than responding to requests to it.

Is that the last hop on your route before the CCP servers or are there more hops after it?
Iguanoid
Ascendance
Goonswarm Federation
#155 - 2016-03-04 04:41:39 UTC
Running pingplotter to client.eveonline.com shows steady 120ms latency and no packet loss with client running, including a socket closed episode just now...
Tipa Riot
Federal Navy Academy
Gallente Federation
#156 - 2016-03-04 11:43:16 UTC  |  Edited by: Tipa Riot
Since the TQ hardware change things got worse, these are the frequent issues since Tuesday:


  • lags in combat, click on weapon, tank, wait 5s till reaction, often surroundings "jump" to catch up with server state, deja vu effects
  • lags in UI, killmails don't open (you often need to click 3 times, waiting 10s), market delay 10s, UI freezes
  • socket close, had 5 since Tuesday - in comparison I had a half a dozen in the almost 3(!) years before.
  • ingame sounds stop working during fights - toggle sound off/on fixes the issue, but may not be healthy during fights


Actually this makes any solo activities a russian roulette ... Ugh

I have not changed any setup on my side, still using the old launcher, single client only.

I'm my own NPC alt.
Shade Millith
Tactical Farmers.
Pandemic Horde
#157 - 2016-03-04 13:53:17 UTC
Ever since a few days ago, I've been getting many socket closes over and over.

This was PingPlotter at the most recent one.

http://i.imgur.com/WmcKi1g.jpg
Arkanis Bloodmoon
Spectre Tech
#158 - 2016-03-04 15:06:38 UTC
I opened a bug report for this 3 days ago - exact same symptoms, started about the same time as everyone here it seems. I got the first bug report closed with a generic "it's your innerwebs, the innerwebs between us, or some magical force that isn't us" response in the comments. The next night I started up LogLite and logged in both accounts. Sure enough, the second account would get disconnected at random intervals, and would not stay online for longer than 20 minutes or so. However, if I just run one account I didn't have any issues and it seemed to play fine.

I have used the exe and not the launcher to connect and gotten the same results. I also found that I was getting the headlines error every minute that I am logged in coming from the billboard (according to the LiteLog report).


------From LogLite------
Closing connection to 87.237.34.200:26000: {'reasonCode': None, 'reason': u'The socket was closed', 'exception': error(10054, 'An existing connection was forcibly closed by the remote host'), 'reasonArgs': {}}

I also noticed this as well:
Failed to get news headlines from: http://www.eveonline.com/mb/news-headlines.asp?s=tranquility&language_id=EN, Retrying in 1 minute..over and over and over.


Also, I get 2 popups letting me know that I am being socket bombed, which was known about in 2012. See CCP Habakuk's post...
https://forums.testeveonline.com/default.aspx?g=posts&m=1404579#post1404579

/sigh
Helios Anduath
The Scope
Gallente Federation
#159 - 2016-03-04 15:08:23 UTC
Shade Millith wrote:
Ever since a few days ago, I've been getting many socket closes over and over.

This was PingPlotter at the most recent one.

http://i.imgur.com/WmcKi1g.jpg


Did you socket close at the first block of packet loss for the final hop or in the second block? or both?

That pingplotter implies that the cause was to do with the Telia <> CCP peering link - definitely worth a ticket/bug report with that pingplotter attached and details of when in that packet loss chunk you DCed.
Helios Anduath
The Scope
Gallente Federation
#160 - 2016-03-04 15:13:27 UTC  |  Edited by: Helios Anduath
Arkanis Bloodmoon wrote:
I opened a bug report for this 3 days ago - exact same symptoms, started about the same time as everyone here it seems. I got the first bug report closed with a generic "it's your innerwebs, the innerwebs between us, or some magical force that isn't us" response in the comments. The next night I started up LogLite and logged in both accounts. Sure enough, the second account would get disconnected at random intervals, and would not stay online for longer than 20 minutes or so. However, if I just run one account I didn't have any issues and it seemed to play fine.

I have used the exe and not the launcher to connect and gotten the same results. I also found that I was getting the headlines error every minute that I am logged in coming from the billboard (according to the LiteLog report).

....

/sigh


What does a pingplotter to client.eveonline.com show during a disconnect event? post a screenshot. As mentioned by Goliath and Sputnik in that thread, more details are good and a pingplotter can fairly definitiely show over time where an issue may be if there is a connectivity issue.