Posted - 2010.06.14 02:04:00 - [2]

 

nope, ive got it too, lost my ship as it says im ina capsule

fix plz CCP, thanks

Posted - 2010.06.14 03:13:00 - [4]

 

I am sorry, you are obviously mistaken. EVE does not have Socket Closed Errors anymore. It is obviously an Hallucination on your part due to an over consumption of psychedelic substances. This was all fixed several patches before. Honest. CCP said they fixed it, so it must be true!

oh wai.....

Posted - 2010.07.02 06:06:00 - [6]

 

i have started to have these too since eve cluster moved. Not even once before that. Now 1-2 a day :(

Posted - 2010.07.02 11:25:00 - [8]

 

A 'socked closed' error means there was a connection drop somewhere along the route, you could try pinging the server and see where potentially problematic spots might be.

I only wish EVE wasn't so delicate to connection fluctuation, most MMOs can update you even after 10 to 15 seconds of no communication between the client and the server.

Posted - 2010.07.02 13:44:00 - [12]

 

Edited by: IQ 001 on 02/07/2010 13:44:05
socket closed doesnt always indicate a connection drop...it could also be bad programming not caught by the regular testing.

for instance (and a little off topic) , in my organisation, application A was producing a time out error when contacting application b for about 5% of the calls which was over the defined thresholds. all the devs insisted to check why the broker was producing the timeout...turned out it wasnt the broker at at, it was a particular call to the DB not handled in the correct way as the dev didnt read the functions small print, no idea why that lead to a time out being generated by the db though...

that being said, with the recent socket closed errors, i scanned my line (i am lucky enuf to work for the telecoms company that i have my interweb thingy on) and i can see a severely errored line, coinciding with the peak disconnections i was achieving... give ur isp a call and see if they can see anything wrong with the ErroredSecondsUp, severlyerroredsecondsup, signal / noise ratio's, attenuation up and attenuation down parameters.

edit: removed wall of text

Posted - 2010.07.02 14:18:00 - [14]

 

Originally by: IQ 001

---

Edited by: IQ 001 on 02/07/2010 13:44:05
socket closed doesnt always indicate a connection drop...it could also be bad programming not caught by the regular testing.

for instance (and a little off topic) , in my organisation, application A was producing a time out error when contacting application b for about 5% of the calls which was over the defined thresholds. all the devs insisted to check why the broker was producing the timeout...turned out it wasnt the broker at at, it was a particular call to the DB not handled in the correct way as the dev didnt read the functions small print, no idea why that lead to a time out being generated by the db though...

that being said, with the recent socket closed errors, i scanned my line (i am lucky enuf to work for the telecoms company that i have my interweb thingy on) and i can see a severely errored line, coinciding with the peak disconnections i was achieving... give ur isp a call and see if they can see anything wrong with the ErroredSecondsUp, severlyerroredsecondsup, signal / noise ratio's, attenuation up and attenuation down parameters.

edit: removed wall of text

---

If only people like you worked in the call centers for most ISPs. The usual response is the following, "unplug your modem", "reboot your computer", then "we'll send someone out within a week" to any problem. It is a rare, rare thing for me to ever get someone who actually tests the line or even thinks of testing the line.

Posted - 2010.07.06 22:41:00 - [16]

 

Edited by: IQ 001 on 06/07/2010 22:42:42

Originally by: IQ 001

---

Edited by: IQ 001 on 02/07/2010 13:44:05
socket closed doesnt always indicate a connection drop...it could also be bad programming not caught by the regular testing.

for instance (and a little off topic) , in my organisation, application A was producing a time out error when contacting application b for about 5% of the calls which was over the defined thresholds. all the devs insisted to check why the broker was producing the timeout...turned out it wasnt the broker at at, it was a particular call to the DB not handled in the correct way as the dev didnt read the functions small print, no idea why that lead to a time out being generated by the db though...

that being said, with the recent socket closed errors, i scanned my line (i am lucky enuf to work for the telecoms company that i have my interweb thingy on) and i can see a severely errored line, coinciding with the peak disconnections i was achieving... give ur isp a call and see if they can see anything wrong with the ErroredSecondsUp, severlyerroredsecondsup, signal / noise ratio's, attenuation up and attenuation down parameters.

edit: removed wall of text

---

just finished the last diagnostics with my isp, i have new hardware and new wiring, all errors are at zero and have been informed that some of the errors are diagnostic only...

as of yesterday all the equipment was installed. since yesterday i have been disconnected approx 30 times...

its the eve client with lousy programming for error handling.

Originally by: CCP Navigator

---

If you are getting a "Socket Closed" error I would suggest you read this thread for further information and advice.

---

yes, lets go to a forgotten thread that is completely ignored by ccp...

Posted - 2010.07.06 23:00:00 - [18]

 

Originally by: Julius Rigel

---

"Something is wrong and I'm about to post on the forum" checklist:

[x] There's something wrong.
[ ] I've asked people in the immediate vicinity, Corp chat, Help chat, Local.
[ ] I've searched google and eve-search for a solution / people with the same or similar problems.
[ ] I've filed a petition.
[ ] I've gotten a response on my petition.
[ ] I've filed a bug report.
[ ] I've taken every step above and there's still something wrong.
[ ] I've checked to see if there is an existing thread on this topic.
[ ] I've checked to make sure every relevant piece of information is included in my post.
[x] I've performed a spell check on my post.
[ ] I'm prepared to give you all my stuff.

You're almost there, buddy!

---

<rolls up newspaper>
bad troll, bad!

Posted - 2010.07.06 23:31:00 - [20]

 

thanks xxuda that fixed it i didnt know they moved the servers around
suppose most people read the dev notes
no more disconnects anymore :)

Posted - 2010.07.07 00:14:00 - [22]

 

Originally by: IQ 001

---

Originally by: Sturmwolke

---

Edited by: Sturmwolke on 06/07/2010 23:33:17

It's typically caused by an intermittent packet loss (due to congestion/router errors/proxy filters) somewhere along the way.
Browser/website connections aren't really reliable indicators unless what you're facing is a chronic connection problem.

Run up the PingPlotter iterations as per Wiki. The program is trialware, but you can still use it after 30days for tracing (after some waiting on the registration pop-up). I'd suggest running a TCP trace over the default UDP as some routers may have UDP trace blocked.

P.S Why on earth is this thread still in GD?

P.S Gawd, it's a necro. /me fail.

---

tracert shows line/connection having no problems. none of the stuff ccp point to also shows no problem....
all help channels sought show NO PROBLEM with my connection.

yet i disconnection about 10 times per hour.

---

However, judging by the fact that we're all on, and you're one of few having issues (and it is few - if 50 people complain, then that's only 1/1000 of the people on EVE (not even taking into account subscribers).

I would keep trying until you find the cause, because 99% of the time, it's something as simple as ****ty AV software, or a a crappy router.

Posted - 2010.07.07 07:04:00 - [24]

 

Originally by: Sturmwolke

---

Originally by: IQ 001

---

tracert shows line/connection having no problems. none of the stuff ccp point to also shows no problem....
all help channels sought show NO PROBLEM with my connection.

yet i disconnection about 10 times per hour.

---

Read again. Pay attention to the words "intermittent" and "iterations".

Assuming you done a proper log of all your network traces (for a period > 1hr) and failed to locate any noticeable packet losses in the routing, start isolating the hardware/software by either running EVE on a different internet connection (using the same computer) or vice-versa. Basic common sense.

Those basic troubleshooting regime will usually narrow down where the problem is. No one in this world can tell you where the exact problem is because no one knows exactly your unique technical situation. You need to do your own leg work at isolating where the problem is coming from. Speculations won't help.

---

you have mentioned nothing new. i have done pretty much everything you have said. as for switching my isp/connection - im legally contracted to them and i cant break it especially when they can PROVE that theres nothing wrong on there side.
that leaves a problem down the pipe, or with the client. and given that any problem down the pipe (i.e. packet loss) is INHERENT with tcp & overbooking, thats like saying 'its the internets fault for working the way its designed to work'

Posted - 2010.07.07 09:16:00 - [26]

 

Originally by: Sturmwolke

---

Edited by: Sturmwolke on 07/07/2010 09:08:37

Originally by: IQ 001

---

you have mentioned nothing new...

---

Well then, there shouldn't be any guesses where the problem resides. "Or" should not exist between client hardware & software and connectivity since it's a simple matter of elimination. There are plenty of clues, suggestions and workarounds from players under the main sticky in the Issues forum, as linked by CCP Navigator above. I'm wondering why this was dismissed so readily.

Also read this thread. This guy ran through fairly exhaustive troubleshooting steps, trying to isolate the problem. He managed to isolate the issue to somewhere within his uni's network. Working from there, players posted several suggestions.

edit:grammar/formatting

---

i will check out that new thread this evening in more detail to check if i have done it all. off hand i can see he has attempted some of the same things as me. thanx for info.