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
Glijaron
Hell In A HandBasket Syndicate
#41 - 2012-04-10 12:06:43 UTC
Same issue as everyone else. Randomly booted to login screen and it seems to happen at the worst times. Started playing EvE again about 3 days ago after about a 2 month hiatus, but never had an issue before. I would suspect it started happening after last patch.
In Aus here.
nulab jones
Wolfsbrigade
Ghost Legion.
#42 - 2012-04-10 12:56:52 UTC  |  Edited by: nulab jones
Having the same issues, some days it doesn't seem to bad then others it's every 20 to 1-2 hours if im lucky.

Lost a HG crystal set + cyclone in lowsec form this today

4-5 accounts on 2 machines dropped at the same time. 2 accounts stayed "logged" in with ships sitting in space but no response the others rebooted to login screen.

I noticed the eve online website also hangs at times.

Also in Aus, using iinet and ADSL 2.

Never had connections issues like this since starting in 2006.

Losing implants is a pain but nothing major, being able to stay connected and play the game is more important.

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 35 ms 34 ms 33 ms nexthop.wa.iinet.net.au [203.215.5.244]
3 34 ms 33 ms 34 ms te7-1.per-qv1-bdr1.iinet.net.au [203.215.4.18]
4 80 ms 80 ms 80 ms te4-4.ade-pipe-bdr2.iinet.net.au [203.215.20.20]

5 82 ms 81 ms 82 ms po4-100.ade-pipe-bdr1.iinet.net.au [203.215.20.1
37]
6 84 ms 85 ms 84 ms te6-4.mel-pipe-bdr1.iinet.net.au [203.215.20.18]

7 227 ms 84 ms 85 ms xe-0-1-0-0.syd-ult-core1.iinet.net.au [203.215.2
0.102]
8 87 ms 87 ms 87 ms 26629.siko06.cu.reach.com [134.159.126.45]
9 85 ms 85 ms 84 ms i-0-2-4-0.sydo-core01.bi.reach.com [202.84.223.5
]
10 204 ms 204 ms 204 ms i-4-0-0.siko-core02.bx.reach.com [202.84.140.138
]
11 207 ms 207 ms 205 ms i-0-2-0-0.siko01.bi.reach.com [202.84.219.46]
12 278 ms 279 ms 277 ms 6453.tyo.equinix.com [203.190.230.26]
13 458 ms 456 ms 460 ms if-9-2.tcore2.PDI-PaloAlto.as6453.net [180.87.18
0.17]
14 464 ms 462 ms 497 ms if-2-2.tcore1.PDI-PaloAlto.as6453.net [66.198.12
7.1]
15 463 ms 471 ms * if-13-2.tcore2.NJY-Newark.as6453.net [66.198.127
.46]
16 422 ms 422 ms * if-2-2.tcore1.NJY-Newark.as6453.net [66.198.70.1
]
17 461 ms 464 ms 461 ms if-9-0-0.core4.LDN-London.as6453.net [66.198.70.
130]
18 401 ms 404 ms * ix-12-0-0-3046.core4.LDN-London.as6453.net [195.
219.67.246]
19 601 ms 480 ms * srv245-e.ccp.cc [87.237.36.245]
20 398 ms 398 ms 399 ms 87.237.36.248
21 406 ms 407 ms 406 ms srv200-g.ccp.cc [87.237.38.200]
Velaren
Caldari Provisions
Caldari State
#43 - 2012-04-10 12:57:07 UTC
same issue here. I'm from Australia.
this all started after 1.5patch deployed, at first my pc froze at random time, then after 1.6 patches i keep getting disconnections.

filed petition, got the same reply like everyone else in this thread.

did a tracert test and here's what i got:

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\>tracert srv200-g.ccp.cc

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.1.1
2 <1 ms 4 ms <1 ms iinet.iad [10.1.1.1]
3 6 ms 5 ms 5 ms nexthop.nsw.iinet.net.au [203.215.19.247]
4 6 ms 6 ms 6 ms te1-1.syd-mas-bdr2.iinet.net.au [203.215.18.20]

5 6 ms 6 ms 6 ms te1-2.syd-mas-bdr1.iinet.net.au [203.215.20.153]

6 5 ms 5 ms 5 ms xe-1-1-0-0.syd-mas-core1.iinet.net.au [203.215.2
0.94]
7 196 ms 195 ms 197 ms 34023.sydp06.cu.reach.com [134.159.160.57]
8 199 ms 198 ms 197 ms i-0-5-0-0.tlot-core01.bx.reach.com [202.84.140.1
02]
9 204 ms 196 ms 196 ms i-4-1.eqla01.bi.reach.com [202.40.149.130]
10 199 ms 211 ms 216 ms gblx-peer.eqla01.pr.reach.com [134.159.63.202]
11 334 ms 334 ms 334 ms 204.245.39.42
12 624 ms 629 ms 640 ms srv245-e.ccp.cc [87.237.36.245]
13 334 ms 333 ms 333 ms srv248-e.ccp.cc [87.237.36.248]
14 334 ms 334 ms 332 ms srv200-g.ccp.cc [87.237.38.200]

Trace complete.
Blackknight LTD
#44 - 2012-04-10 13:25:31 UTC
Aus here as well, cant stay connected for longer than 5min if that, lost a rorq the other day when droped out:(


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

1 1 ms 1 ms 1 ms XXX.XXX.X.X
2 21 ms 20 ms 21 ms XXX-X-XX-X.static.dsl.dodo.com.au [XXX.X.XX.X]
3 22 ms 20 ms 21 ms 123-2-4-34.core.dodo.com.au [123.2.4.34]
4 33 ms 23 ms 23 ms bundle-ether20.lon70.melbourne.telstra.net [165.228.136.77]
5 26 ms 23 ms 23 ms bundle-ether2.exi-core1.melbourne.telstra.net [203.50.6.1]
6 44 ms 47 ms 47 ms bundle-ether12.chw-core2.sydney.telstra.net [203.50.11.74]
7 45 ms 46 ms 47 ms bundle-ether1.oxf-gw2.sydney.telstra.net [203.50.6.90]
8 38 ms 39 ms 37 ms tengigabitethernet14-0.sydo-core01.sydney.reach.com [203.50.13.42]
9 1378 ms 155 ms 155 ms i-4-0-0.siko-core02.bx.reach.com [202.84.140.138]
10 165 ms 158 ms 162 ms i-0-2-0-0.siko01.bi.reach.com [202.84.219.46]
11 * * * Request timed out.
12 409 ms 409 ms 412 ms if-9-2.tcore2.pdi-paloalto.as6453.net [180.87.180.17]
13 416 ms 416 ms 416 ms if-2-2.tcore1.pdi-paloalto.as6453.net [66.198.127.1]
14 * 414 ms 419 ms if-13-2.tcore2.njy-newark.as6453.net [66.198.127.46]
15 * 341 ms 329 ms if-2-2.tcore1.njy-newark.as6453.net [66.198.70.1]
16 421 ms 416 ms 416 ms if-9-0-0.core4.ldn-london.as6453.net [66.198.70.130]
17 408 ms 408 ms 408 ms ix-12-0-0-3046.core4.ldn-london.as6453.net [195.219.67.246]
18 408 ms 411 ms 407 ms srv245-e.ccp.cc [87.237.36.245]
19 * 408 ms 407 ms srv248-e.ccp.cc [87.237.36.248]
20 408 ms 412 ms 409 ms srv200-g.ccp.cc [87.237.38.200]

Trace complete.
CCP Mort
C C P
C C P Alliance
#45 - 2012-04-10 14:50:21 UTC  |  Edited by: CCP Mort
ok - we are not ignoring you guys ...

so, about ping tests - has anyone seen packetloss with ping/ping plotter tests to 87.237.38.200 - at the same time you are thrown out of EVE ?


so.. for the tech's - open a cmd window - have a ping 87.237.38.200 -t running in the background...

do you lose pings when thrown out of the game ?

Traceroutes are good for me to see the path/what provider you are using, and request-timeout in the traceroute only means a router in the path is not replying to the traceroute tool.

- Mort
Plato Idari
SoE Roughriders
Electus Matari
#46 - 2012-04-10 18:19:24 UTC  |  Edited by: Plato Idari
This just started happening to me over the last few days, today has been particularly bad. USA - California

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\*****>ping 87.237.38.200

Pinging 87.237.38.200 with 32 bytes of data:
Reply from 87.237.38.200: bytes=32 time=160ms TTL=111
Reply from 87.237.38.200: bytes=32 time=163ms TTL=111
Reply from 87.237.38.200: bytes=32 time=162ms TTL=111
Reply from 87.237.38.200: bytes=32 time=162ms TTL=111

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

C:\Users\*****>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 ---[---.---.---.---]
2 16 ms 15 ms 13 ms -------.---.---.---[---.---.---.---]

3 13 ms 13 ms 13 ms 76.246.22.2
4 13 ms 13 ms 13 ms 151.164.93.237
5 14 ms 15 ms 15 ms sffca01jt.ip.att.net [12.122.81.73]
6 22 ms 15 ms 17 ms xe-1-2-0.mpr4.sjc7.us.above.net [64.125.12.117]

7 19 ms 29 ms 19 ms xe-5-3-0.cr2.sjc2.us.above.net [64.125.30.177]
8 19 ms 17 ms 19 ms xe-1-0-0.cr1.sjc2.us.above.net [64.125.30.137]
9 68 ms 72 ms 70 ms xe-1-2-0.cr1.ord2.us.above.net [64.125.26.138]
10 92 ms 92 ms 92 ms xe-3-0-0.cr1.lga5.us.above.net [64.125.24.37]
11 158 ms 157 ms 157 ms ge-2-1-0.mpr1.lhr3.uk.above.net [64.125.26.38]
12 161 ms 161 ms 161 ms 213-152.240-250.PXu259.above.net [213.152.240.25
0]
13 161 ms 161 ms 161 ms srv248-e.ccp.cc [87.237.36.248]
14 161 ms 161 ms 161 ms srv200-g.ccp.cc [87.237.38.200]

Trace complete.

Update:
Just happened again

Pinging 87.237.38.200 with 32 bytes of data:
Reply from 87.237.38.200: bytes=32 time=162ms TTL=111
Reply from 87.237.38.200: bytes=32 time=162ms TTL=111
Reply from 87.237.38.200: bytes=32 time=163ms TTL=111
Reply from 87.237.38.200: bytes=32 time=162ms TTL=111
Stella Sing-Love
Caldari Provisions
Caldari State
#47 - 2012-04-10 20:02:25 UTC  |  Edited by: Stella Sing-Love
CCP Mort wrote:
ok - we are not ignoring you guys ...

so, about ping tests - has anyone seen packetloss with ping/ping plotter tests to 87.237.38.200 - at the same time you are thrown out of EVE ?


so.. for the tech's - open a cmd window - have a ping 87.237.38.200 -t running in the background...

do you lose pings when thrown out of the game ?

Traceroutes are good for me to see the path/what provider you are using, and request-timeout in the traceroute only means a router in the path is not replying to the traceroute tool.

- Mort


Packet loss will almost always originate from 204.245.39.42 for anyone under the ISP, iinet. I've sent in a few pingplotter tests via petition and was advised to contact my ISP - unfortunately they're being very slow about it.
Here's another 6-8 hours worth of pretty much the same.
http://dl.dropbox.com/u/71422966/eve.pp2
DooDoo Gum
Center for Advanced Studies
Gallente Federation
#48 - 2012-04-10 22:36:24 UTC  |  Edited by: DooDoo Gum
CCP Mort wrote:
ok - we are not ignoring you guys ...

so, about ping tests - has anyone seen packetloss with ping/ping plotter tests to 87.237.38.200 - at the same time you are thrown out of EVE ?


so.. for the tech's - open a cmd window - have a ping 87.237.38.200 -t running in the background...

do you lose pings when thrown out of the game ?

Traceroutes are good for me to see the path/what provider you are using, and request-timeout in the traceroute only means a router in the path is not replying to the traceroute tool.

- Mort


Yes, im watching pingplotter as the dropouts occur, over time there is occasional packetloss, but nothing too strenuous for the client to handle, then at the exact moment the client drops connection, there is an error reported ['ERR'] for the last 4 servers, [3 of them being the CCP ones and the first hop out, you can see this in the picture i linked earlier in this thread] http://i.imgur.com/I47M5.jpg

Note: none of the other routers in the route are reporting error

Pingplotter reports a solid red chunk of 100% packetloss sometimes up to 60 seconds worth, usually more like 20 or so seconds, and then the client drops me back to the login screen

and the whole process is repeated over and over again...

At the most inopportune moments...

And as fequently as 2 [sometimes 3-4] times an hour..

Have spoken with my ISP, they were very quick to respond, and had a look at it from their end, they changed my IP, but as expected it has done nothing to stop the dropouts from occuring
nulab jones
Wolfsbrigade
Ghost Legion.
#49 - 2012-04-11 02:20:01 UTC  |  Edited by: nulab jones
1st screen shot of increased packet loss as i launched 2 extra clients.

http://imgur.com/N3GUt


2nd screenshot as the clients all die

http://imgur.com/5aEvB


3rd Screenshot as clients die again

http://imgur.com/RHXWS


Time of screens shots (my local)
1. 10.14
2. 11.43
3. 12.27
Leeonwung
Damned And Disinherited
#50 - 2012-04-11 02:30:12 UTC  |  Edited by: Leeonwung
Ive been having the same random disconnects since the launcher has been installed. Its happened about 4 times with 2 of them being within 5 minutes of each other on Monday afternoon ...

I'd run the ping and tracert plans this evening when i get home from work but i have other plans unfortunately

"Know the enemy and know yourself; in a hundred battles you will never be in peril. When you are ignorant of the enemy, but know yourself, your chances of winning or losing are equal. If ignorant both of your enemy and yourself, you are certain in every battle to be in peril." - Sun Tzu
MasterDebater
No Crabs Allowed
#51 - 2012-04-11 04:46:18 UTC
First off, thanks to CCP Mort for the response!

Second off, it would be much more helpful if you guys post the ping plotter results. Run the test to 87.237.38.200. Do unlimited for "# of times to trace". Set the interval to like 1 or 2 seconds. Set the samples to include to make it so you have 2-3 minutes of history (for for 1 second interval use 120-180 and for 2 second interval use 60-90). Keep ping plotter up while running the client.

When you drop, screen shot the ping plotter. What this is going to do is show us WHERE your traffic stops. It will show if it's coming from your ISP, from CCP, or somewhere along the way.

You'll see red bars show up on the nodes your traffic isn't making it to.




About 2 days ago my ISP started having packet loss issues and as such I haven't been able to nail down my own discos (hard to tell from legitimate discos cause by my ISP). But if you guys come back with that info it will be very useful.
Matuk Grymwal
Collapsed Out
Pandemic Legion
#52 - 2012-04-11 09:44:15 UTC
CCP Mort wrote:
ok - we are not ignoring you guys ...

so, about ping tests - has anyone seen packetloss with ping/ping plotter tests to 87.237.38.200 - at the same time you are thrown out of EVE ?


so.. for the tech's - open a cmd window - have a ping 87.237.38.200 -t running in the background...

do you lose pings when thrown out of the game ?

Traceroutes are good for me to see the path/what provider you are using, and request-timeout in the traceroute only means a router in the path is not replying to the traceroute tool.

- Mort

Yes, yes and oh god yes. I've been retesting this tonight using ping plotter. I'm actually coming in through a different route now than when I first saw the problem, but I'm still getting packet loss. Usually its in short bursts, but occasionally it goes up to over half a minute, and that's when I drop. I'm now getting the loss in node #16 (ix-12-0-0-3045.core4.LDN-London.as6453.net):

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

1 <1 ms <1 ms <1 ms Vigor.router [192.168.1.1]
2 16 ms 16 ms 15 ms nexthop.nsw.iinet.net.au [203.215.19.247]
3 16 ms 16 ms 16 ms te1-1.syd-mas-bdr1.iinet.net.au [203.215.18.18]
4 15 ms 15 ms 16 ms xe-1-1-0-0.syd-mas-core1.iinet.net.au [203.215.20.94]
5 16 ms 101 ms 95 ms ae0.syd-ult-core1.iinet.net.au [203.215.20.110]
6 17 ms 16 ms 16 ms 26629.siko06.cu.reach.com [134.159.126.45]
7 17 ms 17 ms 17 ms i-0-2-4-0.sydo-core01.bi.reach.com [202.84.223.5]
8 135 ms 136 ms 135 ms i-4-0-0.siko-core02.bx.reach.com [202.84.140.138]
9 137 ms 138 ms 138 ms i-0-2-0-0.siko01.bi.reach.com [202.84.219.46]
10 * * * Request timed out.
11 390 ms 407 ms 388 ms if-9-2.tcore2.PDI-PaloAlto.as6453.net [180.87.180.17]
12 389 ms 389 ms 387 ms if-2-2.tcore1.PDI-PaloAlto.as6453.net [66.198.127.1]
13 409 ms 392 ms 394 ms if-13-2.tcore2.NJY-Newark.as6453.net [66.198.127.46]
14 353 ms 354 ms 360 ms if-2-2.tcore1.NJY-Newark.as6453.net [66.198.70.1]
15 392 ms 392 ms 392 ms if-9-0-0.core4.LDN-London.as6453.net [66.198.70.130]
16 * 421 ms 425 ms ix-12-0-0-3045.core4.LDN-London.as6453.net [195.219.67.242]
17 423 ms 422 ms 422 ms srv248-e.ccp.cc [87.237.36.248]
18 423 ms * 423 ms srv200-g.ccp.cc [87.237.38.200]

Trace complete.

FYI: for affected pilots, as a temporary work around for the issue I have been using the trial version of Battle Ping (server connection was rock solid when I used it). If it's still an issue in a few days, I guess I'll be buying a copy.

-Mat
nulab jones
Wolfsbrigade
Ghost Legion.
#53 - 2012-04-11 09:56:30 UTC
Another crash and another screenshot, this time using pingplotter

http://imgur.com/MpyeM

Velaren
Caldari Provisions
Caldari State
#54 - 2012-04-11 10:07:54 UTC
CCP Mort wrote:
ok - we are not ignoring you guys ...

so, about ping tests - has anyone seen packetloss with ping/ping plotter tests to 87.237.38.200 - at the same time you are thrown out of EVE ?


so.. for the tech's - open a cmd window - have a ping 87.237.38.200 -t running in the background...

do you lose pings when thrown out of the game ?

Traceroutes are good for me to see the path/what provider you are using, and request-timeout in the traceroute only means a router in the path is not replying to the traceroute tool.

- Mort


yes. there was
CCP Mort
C C P
C C P Alliance
#55 - 2012-04-11 13:47:11 UTC
ok - this is interesting

I'm going to go over the traces you showed me - hopefully I can pin this to a single provider.

I have already asked the GM's to give me the IP's you are connecting from, as we don't want you to give that out in the forums. The path trace you take is not necessarily the same that I see as the routes are very often asymmetric

thanks for all the input - this is very valuable.

Mort
CCP Mort
C C P
C C P Alliance
#56 - 2012-04-11 14:04:38 UTC

ok - just a very informal look - looking at the nearest hop to you . I see that the path I chose to you is through Teleglobe/TATA.

I'm going to do a route change and make Teleglobe unsexy to use - I'm going to do that during DT tomorrow Thursday. I would then like to see if this changes anything. It's quite hard to talk to those guys, this would give me some gold-ammo to use if this fixes the problems.
Plato Idari
SoE Roughriders
Electus Matari
#57 - 2012-04-11 18:46:17 UTC
I just wanted to give you a heads up that it has been much better today. There was one minute where I thought I was going to get kicked off, but the client recovered.
Bending Unit 22
The Asteroid is Depleted
#58 - 2012-04-11 21:53:16 UTC
Plato Idari wrote:
I just wanted to give you a heads up that it has been much better today. There was one minute where I thought I was going to get kicked off, but the client recovered.


Agreed, I played for probably a couple of hours last night and I don't think I dropped out once...
Fallo Gallentine
The Scope
Gallente Federation
#59 - 2012-04-11 22:30:42 UTC
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
DooDoo Gum
Center for Advanced Studies
Gallente Federation
#60 - 2012-04-11 23:27:56 UTC  |  Edited by: DooDoo Gum
I have still experienced dropouts in todays session.

looking forward to tonights downtime more than ever...

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

^another PIngplotter screenshot showing the 3x servers the pings are not getting to

Also worth noting i get kicked off SISI at the same time as Tranq