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.
 

I keep crashing/logging out.

First post
Author
Previous Topic Next Topic
Panametrics
Future Corps
Sleeper Social Club
#61 - 2012-04-12 03:37:21 UTC
Just happened to me 3 times tonight, and a few other times in the passed few days. Had no issues before.

The eve website also does not work for this period of time while I cant reconnect(1-2 mins)

All my other internets are working fine :D

Edit: I'm in Canada
Velaren
Caldari Provisions
Caldari State
#62 - 2012-04-12 03:48:33 UTC
Fallo Gallentine wrote:
Same here.

IINET, ADSL2+, Australia, 150m from exchange ;-)

Everything has been perfect until a few weeks ago, a bit hard to pinpoint the exact date, which is why I too had originally thought it was related to the launcher and/or client.

It is not a localised connection issue, as all other interactive interwebs applications are still connected (mumble, rdp, ssh, etc), only eve client restarts and I did verify quickly that the modem link has not dropped out for weeks. Have not further monitored connectivity as yet because of this reason, but it may be an upstream connection between iinet and ccp.

I have run LogServer.exe before client start and whilst client disconnected randomly, and saved the workspace. What do we do with this little gem?

Regds

Fallo




i'm going to quote a reply from GM about what to do with those files:


C) Finding the crashdump ( if one is created )

Press Windows Key + R and paste the following line into the Run window.

%USERPROFILE%\Local Settings\Application Data\CCP\EVE\ if you use Windows XP %LOCALAPPDATA%\CCP\EVE\ if you use Windows Vista or Windows 7

Find the .dmp file with the most recent time stamp. Files called #error*.txt are useless.

D). Also if you haven't already sent us your Dxdiag files run the DirectX diagnostics tool:

1. Press 'Start' and select 'run'. Type dxdiag and hit enter. When you do this, a window will pop up.
2. Click the "Save All Information" button that's located in its lower right corner.

When you've gathered all the files compress them all into a .zip or .rar file ( depending on which compression program you use ) Then attach the compressed file to either this e-mail reply ( sent to the e-mail you associated with your EVE account ) or by using the attachment box by logging in to "My Petitions" on our homepage ( http://support.eve-online.com/Pages/Petitions/MyPetitions.aspx ) open the petition there. An attachment box is presented after opening the petition.
nulab jones
Wolfsbrigade
Ghost Legion.
#63 - 2012-04-12 06:09:38 UTC
Tried battleping today form the main PC, not a single DC

Laptop that is not running battleping has crashed about 5 times.

Maybe the changes to the route info that mort suggested will help.

Fingers crossed
Stella Sing-Love
Caldari Provisions
Caldari State
#64 - 2012-04-12 08:32:02 UTC
I still get drop outs from time to time. The graph pretty much looks just like DooDoo Gum's - high packet loss and about 100ms latency added to what it was previously. I'll have a ping plotter session saved in a couple of hours.
Mollernak
Brutor Tribe
Minmatar Republic
#65 - 2012-04-12 09:15:45 UTC  |  Edited by: Mollernak
It actually got a bit better for us the other week for a few days, but it's back to being basically unplayable for my wife and I atm.

Interesting to note that when we are both playing, the disconnections occur simultaneously on both computers, while mumble/TS on both continues on fine...

Followed the recommendations in the response to the my petition on my other account (including flashing all my network devices routers/modem/etc).

Running PingPlotter constantly atm, with it generating email alerts for each scenario that would result in a disconnection, got about 50 of those in the last 24 hours.

In New Zealand, and pretty much starting to have to consider closing accounts (7 accounts when you can't even play is a bit of an expense).
Bending Unit 22
The Asteroid is Depleted
#66 - 2012-04-12 12:17:47 UTC  |  Edited by: Bending Unit 22
My route has changed around the time of the bounce today... it is now

Quote:

Tracing route to srv200-g.ccp.cc [87.237.38.200]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms gordon [192.168.1.254]
2 16 ms 16 ms 17 ms nexthop.nsw.iinet.net.au [203.215.17.248]
3 17 ms 17 ms 16 ms te1-1.syd-ult-bdr1.iinet.net.au [203.215.16.22]
4 17 ms 17 ms 17 ms xe-1-1-0-0.syd-ult-core1.iinet.net.au [203.215.20.30]
5 18 ms 17 ms 17 ms 26629.siko06.cu.reach.com [134.159.126.45]
6 17 ms 18 ms 17 ms i-0-7-1-0.sydo-core02.bi.reach.com [202.84.223.1]
7 157 ms 157 ms 156 ms i-0-2-0-0.1wlt-core01.bx.reach.com [202.84.140.21]
8 202 ms 202 ms 202 ms i-1-2.eqla01.bi.reach.com [202.84.251.174]
9 232 ms 221 ms 215 ms gblx-peer.eqla01.pr.reach.com [134.159.63.202]
10 396 ms 402 ms 349 ms 204.245.39.38
11 306 ms 306 ms 307 ms srv248-e.ccp.cc [87.237.36.248]
12 306 ms 306 ms 305 ms srv200-g.ccp.cc [87.237.38.200]

Trace complete.


7 less hops, and around 100ms improvement in ping. The main diff though? Previously I was averaging 10-15% packet loss to the final destination, the new one seems to be about 1.5%

No hiccups so far. Fingers crossed.

Update

Trace running for last hour while in game... packet loss down to 0.8% and no drops.
Matuk Grymwal
Collapsed Out
Pandemic Legion
#67 - 2012-04-12 13:39:46 UTC
So I've had ping plotter running all (AU) evening, so from before DT to 3 hours after. Since DT I've seen one block of about 30s of packet loss (which is generally long enough to disconnect eve). However completely green otherwise. Certainly better.
DooDoo Gum
Center for Advanced Studies
Gallente Federation
#68 - 2012-04-12 21:51:53 UTC
Excitedly log in to give EVE another go...

All seems to be going well, even get a nice drop in latency which runs steady for a while....

30 mins in, dropped connection...

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

Getting REALLY pi**ed off now !
Linolea Austrene
0.0 Massive Dynamic
Pandemic Horde
#69 - 2012-04-12 22:42:16 UTC  |  Edited by: Linolea Austrene
Had very few disconnects from the EVE client for the year that I have been playing. All of a sudden since the 12 April patch I disconnected 3 times in a couple hours. Aus player here.

*EDIT* Make that 4 times...
Lucus Ranger
The Scope
Gallente Federation
#70 - 2012-04-12 23:47:33 UTC
Same problem as everyone else. It keeps logging/crashing me to desktop. It's pretty random I've noticed; also I can have both my accounts online and only one will crash while the other is fine... Been like this for a while now.
DooDoo Gum
Center for Advanced Studies
Gallente Federation
#71 - 2012-04-13 00:31:58 UTC  |  Edited by: DooDoo Gum
Lucus Ranger wrote:
Same problem as everyone else. It keeps logging/crashing me to desktop. It's pretty random I've noticed; also I can have both my accounts online and only one will crash while the other is fine... Been like this for a while now.


Yeah, i have all accounts that are logged in disconnect simultaneously [including SISI]
nulab jones
Wolfsbrigade
Ghost Legion.
#72 - 2012-04-13 01:59:51 UTC  |  Edited by: nulab jones
Issue is still not fixed, i just turned battle ping off to test it and sure enough all dced within 20 mins.

Back to pingplotter we go


EDIT:


Well that took a whole 10 mins to happen again

http://imgur.com/9mwMb


The routing changes the mort made the other day do seem to have lowered my ping overall by about 100 and has 7 or so less hops, however the error is still happening on the fist hop after the ccp named servers, IP 204.245.39.32 - no name this time


and another one about 1.5 hours from the last

http://imgur.com/qxDpY


about 30 mins later

http://imgur.com/wCVva
Byerly Plodalong
#73 - 2012-04-13 05:32:21 UTC
Same problem as everyone else from iiNet in Australia. I'm a new player but this thread gives me hope that my relationship with Eve will not be short lived!
Linolea Austrene
0.0 Massive Dynamic
Pandemic Horde
#74 - 2012-04-13 10:12:13 UTC  |  Edited by: Linolea Austrene
This was the situation during normal operation:

Quote:
Pinging 87.237.38.200 with 32 bytes of data:
Reply from 87.237.38.200: bytes=32 time=291ms TTL=116
Reply from 87.237.38.200: bytes=32 time=291ms TTL=116
Reply from 87.237.38.200: bytes=32 time=291ms TTL=116
Reply from 87.237.38.200: bytes=32 time=291ms TTL=116

Ping statistics for 87.237.38.200: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds: Minimum = 291ms, Maximum = 291ms, Average = 291ms

tracert 87.237.38.200

Tracing route to srv200-g.ccp.cc [87.237.38.200]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.2.1
2 14 ms 14 ms 14 ms nexthop.wa.iinet.net.au [203.215.5.243]
3 14 ms 14 ms 13 ms te7-2.per-qv1-bdr1.iinet.net.au [203.215.4.20]
4 62 ms 62 ms 62 ms te4-4.ade-pipe-bdr2.iinet.net.au [203.215.20.20]
5 61 ms 63 ms 62 ms po4-100.ade-pipe-bdr1.iinet.net.au [203.215.20.137]
6 65 ms 64 ms 62 ms te6-4.mel-pipe-bdr1.iinet.net.au [203.215.20.18]
7 64 ms 88 ms 65 ms xe-0-1-0-0.syd-ult-core1.iinet.net.au [203.215.20.102]
8 63 ms 60 ms 60 ms 26629.siko06.cu.reach.com [134.159.126.45]
9 65 ms 65 ms 65 ms i-0-7-1-0.sydo-core02.bi.reach.com [202.84.223.1]
10 202 ms 202 ms 202 ms i-0-0-0-0.1wlt-core01.bx.reach.com [202.84.141.146]
11 249 ms 250 ms 249 ms i-3-4.eqla01.bi.reach.com [202.84.251.154]
12 288 ms 272 ms 298 ms gblx-peer.eqla01.pr.reach.com [134.159.63.202]
13 291 ms 291 ms 299 ms 204.245.39.42
14 291 ms 291 ms 291 ms srv245-e.ccp.cc [87.237.36.245]
15 291 ms 291 ms 291 ms srv248-e.ccp.cc [87.237.36.248]
16 292 ms 291 ms 292 ms srv200-g.ccp.cc [87.237.38.200]

Trace complete.


Then I was dumped from the client and pinged with the following result:

Quote:
ping 87.237.38.200

Pinging 87.237.38.200 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Reply from 87.237.38.200: bytes=32 time=292ms TTL=116

Ping statistics for 87.237.38.200: Packets: Sent = 4, Received = 1, Lost = 3 (75% loss),
Approximate round trip times in milli-seconds: Minimum = 292ms, Maximum = 292ms, Average = 292ms


And later dumped again and attempted tracert immediately and was greeted with:

Quote:
Tracing route to srv200-g.ccp.cc [87.237.38.200]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.2.1
2 13 ms 13 ms 13 ms nexthop.wa.iinet.net.au [203.215.5.243]
3 14 ms 14 ms 14 ms te7-2.per-qv1-bdr1.iinet.net.au [203.215.4.20]
4 62 ms 62 ms 62 ms te4-4.ade-pipe-bdr2.iinet.net.au [203.215.20.20]
5 62 ms 62 ms 62 ms po4-100.ade-pipe-bdr1.iinet.net.au [203.215.20.137]
6 61 ms 62 ms 62 ms te6-4.mel-pipe-bdr1.iinet.net.au [203.215.20.18]
7 106 ms 64 ms 64 ms xe-0-1-0-0.syd-ult-core1.iinet.net.au [203.215.20.102]
8 60 ms 60 ms 60 ms 26629.siko06.cu.reach.com [134.159.126.45]
9 65 ms 65 ms 65 ms i-0-7-1-0.sydo-core02.bi.reach.com [202.84.223.1]
10 203 ms 202 ms 202 ms i-0-0-0-0.1wlt-core01.bx.reach.com [202.84.141.146]
11 250 ms 249 ms 249 ms i-3-4.eqla01.bi.reach.com [202.84.251.154]
12 274 ms 275 ms 273 ms gblx-peer.eqla01.pr.reach.com [134.159.63.202]
13 * * 299 ms 204.245.39.42
14 296 ms 477 ms 399 ms srv245-e.ccp.cc [87.237.36.245]
15 296 ms 296 ms 300 ms srv248-e.ccp.cc [87.237.36.248]
16 296 ms 296 ms 296 ms srv200-g.ccp.cc [87.237.38.200]

Trace complete.


Hope this helps identify the problem. Issue with the connection to 204.245.39.42? Probably 4-5 disconnects in 3-4 hours tonight ... getting old very quickly.
Leads Dent
Deep Core Mining Inc.
Caldari State
#75 - 2012-04-13 18:07:37 UTC  |  Edited by: Leads Dent
Adding my name to the list. Australia too.

Happened twice tonight and has been happening over the past week or so.

Did this traceroute about 40 mins after the second crash so not sure if it will help but in any case.

Tracing route to srv200-g.ccp.cc [87.237.38.200]
over a maximum of 30 hops:

1 2 ms 1 ms 1 ms bob.iad [10.1.1.1]
2 18 ms 18 ms 19 ms nexthop.wa.iinet.net.au [203.215.5.243]
3 18 ms 19 ms 21 ms te7-2.per-qv1-bdr2.iinet.net.au [203.215.4.38]
4 66 ms 68 ms 66 ms po1-100.per-qv1-bdr1.iinet.net.au [203.215.20.130]
5 66 ms 67 ms 66 ms te4-4.ade-pipe-bdr2.iinet.net.au [203.215.20.20]
6 70 ms 71 ms 71 ms po4-100.ade-pipe-bdr1.iinet.net.au [203.215.20.137]
7 70 ms 71 ms 70 ms te6-4.mel-pipe-bdr1.iinet.net.au [203.215.20.18]
8 66 ms 68 ms 68 ms te6-1-100.mel-pipe-bdr2.iinet.net.au [203.215.20.139]
9 73 ms 77 ms 73 ms xe-0-1-0-0.syd-mas-core1.iinet.net.au [203.215.20.106]
10 156 ms 72 ms 71 ms ae0.syd-ult-core1.iinet.net.au [203.215.20.110]
11 72 ms 71 ms 71 ms 26629.siko06.cu.reach.com [134.159.126.45]
12 75 ms 76 ms 74 ms i-0-7-1-0.sydo-core02.bi.reach.com [202.84.223.1]
13 214 ms 212 ms 211 ms i-0-0-0-0.1wlt-core01.bx.reach.com [202.84.141.146]
14 278 ms 405 ms 411 ms i-1-2.eqla01.bi.reach.com [202.84.251.174]
15 243 ms 244 ms 243 ms gblx-peer.eqla01.pr.reach.com [134.159.63.202]
16 405 ms 295 ms 295 ms 204.245.39.42
17 304 ms 301 ms 303 ms srv245-e.ccp.cc [87.237.36.245]
18 303 ms 302 ms 303 ms srv248-e.ccp.cc [87.237.36.248]
19 297 ms 297 ms 300 ms srv200-g.ccp.cc [87.237.38.200]

Trace complete.
Linolea Austrene
0.0 Massive Dynamic
Pandemic Horde
#76 - 2012-04-13 22:57:49 UTC
Reading through the thread it appears that whatever was changed on Thursday (EVE time) which was Friday morning when I patched, seems coincidently to have resulted in a few Aussie players posting that they have this issue. I applied the last patch Friday morning and the disconnects started happening at a rate of at least 1-2 per hour.

Is CCP going to revert/fix the Thursday change or we Aussies just going to have to fork out for third party software to make EVE work?
Glijaron
Hell In A HandBasket Syndicate
#77 - 2012-04-13 23:12:28 UTC  |  Edited by: Glijaron
Still happening for me and it's coming to the point where I am not doing anything major in the game due to these random disconnects. Which is really not fun.

Tracing route to srv200-g.ccp.cc [87.237.38.200]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms BoB.iiNet
2 8 ms 8 ms 8 ms nexthop.nsw.iinet.net.au
3 9 ms 8 ms 9 ms gi3-9.syd-ult-bdr1.ii.net
4 9 ms 8 ms 8 ms te1-2.syd-ult-bdr1.iinet.net.au [203.215.20.146]

5 8 ms 8 ms 8 ms xe-1-1-0-0.syd-ult-core1.iinet.net.au [203.215.2
0.30]
6 10 ms 9 ms 9 ms 26629.siko06.cu.reach.com [134.159.126.45]
7 10 ms 9 ms 9 ms i-0-7-1-0.sydo-core02.bi.reach.com [202.84.223.1]

8 148 ms 148 ms 148 ms i-0-0-0-0.1wlt-core01.bx.reach.com [202.84.141.1
46]
9 194 ms 194 ms 258 ms i-1-2.eqla01.bi.reach.com [202.84.251.174]
10 185 ms 184 ms 184 ms gblx-peer.eqla01.pr.reach.com [134.159.63.202]
11 352 ms 329 ms 329 ms [204.245.39.42]
12 332 ms 501 ms 405 ms srv245-e.ccp.cc [87.237.36.245]
13 330 ms 330 ms 330 ms srv248-e.ccp.cc [87.237.36.248]
14 330 ms 329 ms 329 ms srv200-g.ccp.cc [87.237.38.200]

Trace complete.

http://i1155.photobucket.com/albums/p546/JM4n43/Pingplotter-1.jpg
50.8% packet loss on the last 4 hops.
Bending Unit 22
The Asteroid is Depleted
#78 - 2012-04-14 00:33:05 UTC
Well, I can report I'm still solid as a rock since the change the other day, not a single drop.

Didn't post this to gloat, just to point out that it defintely looks more like a network issue, not a client one, in IMO.

I've also looked at my new route compared to the route everyone else seems to be taking and they are different... in the last 3 hops, the following are common to everyone that's posted a traceroute:

srv245-e.ccp.cc [87.237.36.245]
srv248-e.ccp.cc [87.237.36.248]
srv200-g.ccp.cc [87.237.38.200]

those are usually, but not always, proceeded by this node

[204.245.39.42]

With my new route, the last hops are

srv248-e.ccp.cc [87.237.36.248]
srv200-g.ccp.cc [87.237.38.200]

it no longer hits

srv245-e.ccp.cc [87.237.36.245]

and the preceeding node is also different, being

[204.245.39.38]

This might be a logically leap too far, but based on the above, it would seem traffic going via srv245-e.ccp.cc [87.237.36.245] or the nodes that route to it is where the fault may lie.
Linolea Austrene
0.0 Massive Dynamic
Pandemic Horde
#79 - 2012-04-14 01:23:16 UTC
Unfortunately 204.245.39.42 seems to be the one causing my issues, and I suspect issues for other Aussie players above. I wish to know whether the change implemented by CCP Mort is encouraging our packets to go through this dodgy server. Sorry I am not techie enough to know the correct terminology, but from several tracert's I have run, they all seem to hang at that point longer than all the other jumps. As mentioned before, I almost never had unexplained drops in a year of playing, and now they are happening regularly to the point of making EVE unplayable.
Glijaron
Hell In A HandBasket Syndicate
#80 - 2012-04-14 01:27:29 UTC
This IP 204.245.39.42 also shows up in a thread from 2010 and it's Global Crossing as far as I can tell.

Thread Here

Obviously that router needs fine tuning with a sledge Blink