| Author |
Thread Statistics | Show CCP posts - 6 post(s) |
Inspiration
Focused Radical Energy Engineering
34
   |
Posted - 2012.07.11 22:10:00 -
[1] - Quote
I had it a few times when a client was idle, so i did not think much of it. But just I had an alt go into low sec and warp to a station + dock command via autopilot. Just as i sat at the undock, i got the socket issue again (on an active account), ofc, the server docked me in this instance, but it does give a bad feeling.
Sorry for not having any useful information (other then that i got a stellar Internet connection, most people would kill for). |
Inspiration
Focused Radical Energy Engineering
49
|
Posted - 2013.02.02 15:48:00 -
[2] - Quote
I already posted in my own thread here with more details (even explicit problem servers):
https://forums.eveonline.com/default.aspx?g=posts&t=200800&find=unread
For me the issue started last night, before that i found the service stable. Less then a week ago I added 4 accounts, it should not be hard to imagine how frustrating this network (+code?) issue is to me. These new accounts expire in just under a month and will stay expired unless i get the idea i can play stable.
At the moment there is nothing i can do in game, except maybe a little PI and not even that very well as i got to pick up stuff at some point! Just logging my accounts on, and forming a fleet takes about the same time as the next disconnect occurrence! I do not like the game:
logging on, repeatedly online! |
Inspiration
Focused Radical Energy Engineering
49
|
Posted - 2013.02.02 15:52:00 -
[3] - Quote
LordOfDespair wrote:I get socket closed everynight at around 1 am.
??
That sound like a router issue TBH, I used to have an issue like 6 or more years ago, where i would disconnect every hour (exact). After playing around it with this knowledge I updated my router firmware back then, which solved it. Some routers do have time critical bugs that can cause this sort of thing!
|
Inspiration
Focused Radical Energy Engineering
49
|
Posted - 2013.02.03 09:59:00 -
[4] - Quote
Packet loss is gone as sudden as it came, must have been a shift change somewhere, to people that knew how to replace or correct equipment :)
|
Inspiration
Focused Radical Energy Engineering
49
|
Posted - 2013.02.03 11:22:00 -
[5] - Quote
I Spoke too soon, right after DT it's back with a vengeance....which only hints at an issue in CCPs network, or its interaction with connecting hardware.
|
Inspiration
Focused Radical Energy Engineering
49
|
Posted - 2013.02.03 22:20:00 -
[6] - Quote
THis image tells a story:
http://clip2net.com/s/2N2cQ |
Inspiration
Focused Radical Energy Engineering
49
|
Posted - 2013.02.06 21:58:00 -
[7] - Quote
Arturus VII wrote:Ive been having this problem recently too.
I spoke to someone on the eve help chatboard who said thats its to do with "packet loss from a wireless modem".
Could the problem be that Eve needs a hard line to fucntion properly?
I mentioned that people all over the globe were having the same problem and posted a link to this thread to them
Not working with a wireless modem here, all cable! |
Inspiration
Focused Radical Energy Engineering
49
|
Posted - 2013.02.07 22:59:00 -
[8] - Quote
I got a little further to the cause, this is what happens on my side:
My cable modem has a 1, maybe 2 second period of 100% packet loss (for pings anyway), after which the line is clear again for a long time. This small window of no communication seems enough for the client to see a true loss of connection and it just gives up or the server boots it for being out of sync! The constant, but small amounts of packet loss near CCP's end of the server do not seen to cause the instability in my case.
A CCP developer should look closely at the network layer and the communication protocol between client and server, especially the error handling on both sides!. It looks like the code panics far more often then is necessary!
CCP should also consider having a client side spool/log of the last minute or so of communication that once connection is re-established, this information is uploaded for analysis. Even if you close the client after a disconnect and start again later, sending this information can greatly help to improve connection stability. If something similar is done on the server side for clients who's socket is closed, they got a full communication sequence to analyze!
The beauty of this approach is that all clients from all over the world help to monitor and debug the connection layer!
|
| |
|