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
pajedas
Doomheim
#61 - 2016-01-21 22:00:18 UTC
As soon as I logged in just now I got the old socket closed error.

I was running logserver and this was the error message:

"Failed at storing client achievement events, e = User error, msg=GPSTransportClosed, dict={'what': 'The transport has not yet been connected, or authentication was not successful.'}"

Any help?

πŸ‡
Dante Alicante
From Hell's Heart
#62 - 2016-01-22 10:33:23 UTC
I've been getting "Socket Closed" issues every night for about 2 weeks now, and generally am able to log on for about 10 minutes before the first one, then can't log back in at all on either of my 2 accounts.

I'm not buying the "It's your ISP's fault" explanation from CCP, when so many people are having the same issue around the world (I'm in Australia with Exetel).

I've been playing for close to 10 years on my current and previous accounts, but I play in WH space, and can't get on long enough to fuel my POS or make any ISK to even pay for fuel.

If the issue isn't resolved in the next week, I may as well unsub (why pay to not play?), as I'll likely lose everything I worked to build in WH space.

Not being able to log in isn't fun, and there are other games out there that actually allow me to play them.

The single response from CCP so far has been unhelpful to say the least, and I agree with many posters that it's a very strange coincidence that many people have had this issue since around December.

Will keep my fingers crossed for a solution in the near future.....
pajedas
Doomheim
#63 - 2016-01-22 13:57:40 UTC
MADE IT 15 MINUTES!!!

Gamelog
Listener: pajedas
Session Started: 2016.01.22 13:39:27
[ 2016.01.22 13:40:29 ] (None) Undocking from Uedama VI - Moon 8 - Spacelane Patrol Logistic Support to Uedama solar system.
[ 2016.01.22 13:41:38 ] (notify) The scanner is recalibrating, please wait a second
[ 2016.01.22 13:42:31 ] (notify) Loading the Scanner Probe into the Scan Probe Launcher; this will take approximately 10 seconds.
[ 2016.01.22 13:42:34 ] (notify) Speed changed to 582 m/s
[ 2016.01.22 13:53:20 ] (notify) You were logged out of audio chat.
[ 2016.01.22 13:54:35 ] (info) The socket was closed

πŸ‡
pajedas
Doomheim
#64 - 2016-01-22 19:06:28 UTC

Maybe nothing, but I disabled Eve Voice and I've been on for a couple of hours without a DC.

Give it a try and let me know if it helps?

πŸ‡
pajedas
Doomheim
#65 - 2016-01-23 13:23:15 UTC
pajedas wrote:

Maybe nothing, but I disabled Eve Voice and I've been on for a couple of hours without a DC.

Give it a try and let me know if it helps?

Ended up just being a fluke. Went back to a socket closed about every 30 minutes.

πŸ‡
pajedas
Doomheim
#66 - 2016-01-24 16:37:56 UTC
Am I the only one still getting the socket closed error?

I am currently downloading the entire 6GB resource cache to see if that helps?

Ideas? Answers? Questions? Concerns?

It's very difficult to play when you expect to DC at any moment.

Thanks

πŸ‡
Veshai
NED-Clan
Goonswarm Federation
#67 - 2016-01-25 09:01:27 UTC
No, you're not the only one. Still seeing a bunch people disconnecting at the same time complaining about the error during fleets.

Just create a ticket and keep referring to this thread to create awareness for this issue within CCP.
Gungankllr
DAB
Solyaris Chtonium
#68 - 2016-01-25 21:36:01 UTC
I can't log in. At all. Tried the new launcher and tried from the .exe file, I can only get to the login screen then I get socket closed when I try to enter the game. Without fail.

pajedas
Doomheim
#69 - 2016-01-25 21:41:44 UTC
Gungankllr wrote:
I can't log in. At all. Tried the new launcher and tried from the .exe file, I can only get to the login screen then I get socket closed when I try to enter the game. Without fail.


I'm with you man. I get maybe 15 minutes and then, "The Socket is Closed".

πŸ‡
Silent Samurai
Deep Exploration Projects and Programs
#70 - 2016-01-26 08:34:33 UTC  |  Edited by: Silent Samurai
For me (and also some Ally-Mates) the nightmare started about 2 weeks ago. I can remember installing a client update on January 11th was the initial event. I had the old launcher and 2 seperately installed clients I started by exefile, never had any problems for 8 years. Since that update I am experiencing everything already mentioned above. Some day it's a little better and one client runs stable for 2-3 hours while the other one disconnects "only" 3-5 times, most days it's worse and i have to reconnect every 2-5 minutes.

Right now I tried to do some logistics (buying/selling/hauling stuff). In that 3 hours I had to reconnect about 40-50 times, no lie. Normally this work would have taken me 20-30 minutes. PvP is not even an option right now and also PvE is deadly now, just imagine disconnecting scrambled in a Burner mission and the client not closing for nearly 2 minutes.

I tried EVERY mentioned workaround:

- full swipe of old clients & complete reinstall with new launcher (new launcher made it worse, even more disconnects)
- switched IP port to 3724, even ran one client on standard port 26000 and the other on 3724
- multiple router resets & I always run on cabled LAN not wireless

I ran network diagnostics (pings & traceroutes):

- all network diagnostics look fine, bandwidth & ping, no problems between me and ISP
- manual perma-pings to EVE IP's (the 3 from launcher diagnostics tool) show about 25% timeouts over 30 minutes
- EVE launcher network diagnostics shows from 100% success to 75% packet loss randomly even within the same minute, but packet losses always occur between ISP and CCP

I can even run 2 parallel Full-HD-TV-Streams without lags & interrupts.

It simply can't be an ISP problem, as many posters in this thread & me and my ally mates all have different ISP's and even geographical locations, and several people incl. me reported of good network diagnostic results towards their ISP. But all seem to have the same problem and it all started with a launcher update Shocked.

CCP DO SOMETHING PLS !!!! Simply just not answering my petition for over 10 days now is not the right way, and also not just pasting a standard answer that basically says nothing else than "it's your fault, you can not play the game ... well ... sorry".Evil

The only option that answer gives us is cancelling the subscriptions. All my accounts had subscription renewal in the last few days, if there is nothing changing within the next 3-4 weeks, there will be no further renewal.
pajedas
Doomheim
#71 - 2016-01-26 15:28:31 UTC
Silent Samurai wrote:
For me (and also some Ally-Mates) the nightmare started about 2 weeks ago. I can remember installing a client update on January 11th was the initial event. I had the old launcher and 2 seperately installed clients I started by exefile, never had any problems for 8 years. Since that update I am experiencing everything already mentioned above. Some day it's a little better and one client runs stable for 2-3 hours while the other one disconnects "only" 3-5 times, most days it's worse and i have to reconnect every 2-5 minutes.

Right now I tried to do some logistics (buying/selling/hauling stuff). In that 3 hours I had to reconnect about 40-50 times, no lie. Normally this work would have taken me 20-30 minutes. PvP is not even an option right now and also PvE is deadly now, just imagine disconnecting scrambled in a Burner mission and the client not closing for nearly 2 minutes.

I tried EVERY mentioned workaround:

- full swipe of old clients & complete reinstall with new launcher (new launcher made it worse, even more disconnects)
- switched IP port to 3724, even ran one client on standard port 26000 and the other on 3724
- multiple router resets & I always run on cabled LAN not wireless

I ran network diagnostics (pings & traceroutes):

- all network diagnostics look fine, bandwidth & ping, no problems between me and ISP
- manual perma-pings to EVE IP's (the 3 from launcher diagnostics tool) show about 25% timeouts over 30 minutes
- EVE launcher network diagnostics shows from 100% success to 75% packet loss randomly even within the same minute, but packet losses always occur between ISP and CCP

I can even run 2 parallel Full-HD-TV-Streams without lags & interrupts.

It simply can't be an ISP problem, as many posters in this thread & me and my ally mates all have different ISP's and even geographical locations, and several people incl. me reported of good network diagnostic results towards their ISP. But all seem to have the same problem and it all started with a launcher update Shocked.

CCP DO SOMETHING PLS !!!! Simply just not answering my petition for over 10 days now is not the right way, and also not just pasting a standard answer that basically says nothing else than "it's your fault, you can not play the game ... well ... sorry".Evil

The only option that answer gives us is cancelling the subscriptions. All my accounts had subscription renewal in the last few days, if there is nothing changing within the next 3-4 weeks, there will be no further renewal.

Yes, yes, yes.

All that.

It's on CCP's end, of this I have no doubt.

PLEASE FIT IT!!!

πŸ‡
Silent Samurai
Deep Exploration Projects and Programs
#72 - 2016-01-27 18:32:29 UTC
I finally got an answer to my 12 day old petiotion, and it is basically a bad joke.Evil

GM Karidor sent me a copy&paste statement pointing on ISP and customers on a totally different problem.
I have socket losses, they excuse for low bandwith and download speed for updates, which I never had any issues with.

Either the people at customer support did not even read my petition or they weren't able to understand its content (which would be really awkward).

At this moment I, and some Ally-Mates too, see no other option than cancelling our subscriptions as we cant play 5 minutes without client freezing on socket loss and CCP support simply ignores us as you can see in the concerning threads and in the petitions.

I talked to a friend who works as a Network Tecnician, and after looking on tracerts he told me, that over 90% of the packet losses occur on the last steps from the London network nodes to CCP. So if it really is an ISP problem as CCP always says, maybe CCP should talk to their ISP Evil

I am a little bit older, worked in IT Sales & Support many years, the way CCP treats this problem is not acceptable for a PAYING customer.
YourDeathAngel
The Legion of Spoon
Curatores Veritatis Alliance
#73 - 2016-01-27 21:37:17 UTC
No fix, no answer from ccp. But at least the credit card is being automatically billed and the advertisements in the launcher work. Business as usual, all quiet on the western front...
Paddok Arbosa
Sebiestor Tribe
Minmatar Republic
#74 - 2016-01-29 09:09:53 UTC  |  Edited by: Paddok Arbosa
got the same thing here repeted socket closing error did take me 3hr from amarr>>Jita in a Stab Freighter disconected 3 times in the same system due to socket closing

Basic Ping to EVE


Starting ping for client.eveonline.com

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

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

Starting ping for binaries.eveonline.com

Pinging d17ueqc3zm9j8o.cloudfront.net [205.251.219.143] with 32 bytes of data:
Reply from 205.251.219.143: bytes=32 time=57ms TTL=53
Reply from 205.251.219.143: bytes=32 time=45ms TTL=53
Reply from 205.251.219.143: bytes=32 time=43ms TTL=53
Reply from 205.251.219.143: bytes=32 time=42ms TTL=53
Ninendal
Doomheim
#75 - 2016-01-29 12:54:25 UTC  |  Edited by: Ninendal
Same problem here.

1. Reinstalled Windows 10
2. reinstalled EVE multiple times
3. Switch off firewall en AV
4. Got my self a new modem, Experia V10
5. changed port numbers
6. Opened a ticket with support
7. tried with UTP cable and WIFI
8. running launcher diagnostics which doesn't make sense since packets are lost during transport or not reachable
9. Sometimes a warning in Windows log that DNS cannot find certain EVE connections
10. changed DNS servers in my moden, using the OpenDNS servers
11. living in the Netherlands & KPN is my provider

Whatever I do still get message Socket Closed.
pajedas
Doomheim
#76 - 2016-01-29 14:35:16 UTC
According to PingPlotter Pro the problem is with srv200-g.ccp.cc. (87.237.34.200).

The trace up to that point runs flawlessly every time.


πŸ‡
General Guardian
Perkone
Caldari State
#77 - 2016-01-29 22:16:25 UTC
Same issue for me now on my laptop after installing that small patch from last night.

Managed to log in for about a whole minute in the last hour. It's permanent socket closed errors outside of that one minute.
General Guardian
Perkone
Caldari State
#78 - 2016-01-29 23:20:51 UTC
I've reset my connection that I am currently using (4g Tethered) and was assigned a new I.P address. So far I haven't had socket closed issues. If it was a coincidence I am not sure.

My question is now, why would one IP address from the same machine, same ISP and using the same route have huge packet loss issues that another IP address doesn't? It makes no sense to me.
pajedas
Doomheim
#79 - 2016-01-29 23:24:18 UTC
General Guardian wrote:
It makes no sense to me.

Occam's razor (also written as Ockham's razor, and lex parsimoniae in Latin, which means law of parsimony) is a problem-solving principle attributed to William of Ockham (c. 1287–1347), who was an English Franciscan friar and scholastic philosopher and theologian. The principle can be interpreted as stating Among competing hypotheses, the one with the fewest assumptions should be selected.

The application of the principle can be used to shift the burden of proof in a discussion. However, Alan Baker, who suggests this in the online Stanford Encyclopedia of Philosophy, is careful to point out that his suggestion should not be taken generally, but only as it applies in a particular context, that is: philosophers who argue in opposition to metaphysical theories that involve any kind of probably "superfluous ontological apparatus."[a]

Baker then notes that principles, including Occam's razor, are often expressed in a way that is unclear regarding which facet of "simplicity"β€”parsimony or eleganceβ€”the principle refers to, and that in a hypothetical formulation the facets of simplicity may work in different directions: a simpler description may refer to a more complex hypothesis, and a more complex description may refer to a simpler hypothesis.[b]

Solomonoff's theory of inductive inference is a mathematically formalized Occam's razor: shorter computable theories have more weight when calculating the probability of the next observation, using all computable theories that perfectly describe previous observations.

In science, Occam's razor is used as a heuristic technique (discovery tool) to guide scientists in the development of theoretical models, rather than as an arbiter between published models. In the scientific method, Occam's razor is not considered an irrefutable principle of logic or a scientific result; the preference for simplicity in the scientific method is based on the falsifiability criterion. For each accepted explanation of a phenomenon, there may be an extremely large, perhaps even incomprehensible, number of possible and more complex alternatives, because one can always burden failing explanations with ad hoc hypothesis to prevent them from being falsified; therefore, simpler theories are preferable to more complex ones because they are more testable.

πŸ‡
Silent Samurai
Deep Exploration Projects and Programs
#80 - 2016-01-30 00:43:06 UTC  |  Edited by: Silent Samurai
My connection problems seem to be solved for the moment. There were many really irritating test results on the way, espacially tracert led me to many false conclusions. Read my writing to CCP for further details.

Quote:
Hello CCP,

please consider my petition closed, I was able to narrow down the problem to one of the 4 LAN-Ports of my router with the help of a befriended network technician. Tracerts were really irritating in that process, cause they always showed good connection to router and ISP and packet losses on the last hops between London nodes.

We narrowed down the problem by doing ping -t to my router and 1st hop to ISP with all possible connections (WLAN and 4 LAN ports). My usual 1GBit-LAN-connection showed up to 50% packet loss to the router already, but WLAN had 0%. so it could not be the router core but the cable or the port. We then tested the other 3 LAN Ports which are 100 MBit, and they also all show 0% packet loss. Clients running stable again.

Please take my excuse for any false accusations, I will correct/comment my posts in the official forums, but also my critics for the kind of handling this request by CCP support. I felt pretty alone and misunderstood. Positive side is I learned a lot about TCP/IP networks ;-).

Regards from Germany


As this problem is really annoying and CCP keeps quiet on every version of connection problems I post a small Guide for narrowing down the node on your route that causes the problems. Glad if I can help somebody. Sadly this forums seem to have no spoiler function, so I have to make a double post because of character limit.