1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Crashes and timeouts

Discussion in 'Technical' started by Craggan, Aug 3, 2014.

  1. Craggan

    Craggan Member

    Messages:
    80
    Likes Received:
    18
    Trophy Points:
    8
    SO today while trying to participate in the final hours of the smuggler event at hidden falls I kept crashing and when I try to log back in I get the normal avatar logged in message once then always several timeouts. I ran the traceroute that MA sent out for us and discovered that I'm getting some requests that time out in the middle.

    Here's the first one.

    Sun 08/03/2014
    03:39 PM

    Pinging login.entropiauniverse.com [94.31.61.10] with 32 bytes of data:
    Reply from 94.31.61.10: bytes=32 time=112ms TTL=117
    Reply from 94.31.61.10: bytes=32 time=112ms TTL=117
    Reply from 94.31.61.10: bytes=32 time=110ms TTL=117
    Reply from 94.31.61.10: bytes=32 time=109ms TTL=117
    Reply from 94.31.61.10: bytes=32 time=125ms TTL=117
    Reply from 94.31.61.10: bytes=32 time=108ms TTL=117
    Reply from 94.31.61.10: bytes=32 time=108ms TTL=117
    Reply from 94.31.61.10: bytes=32 time=110ms TTL=117
    Reply from 94.31.61.10: bytes=32 time=109ms TTL=117
    Reply from 94.31.61.10: bytes=32 time=108ms TTL=117

    Ping statistics for 94.31.61.10:
    Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 108ms, Maximum = 125ms, Average = 111ms

    Tracing route to 94.31.61.11.available.above.net [94.31.61.11]
    over a maximum of 30 hops:

    1 1 ms <1 ms <1 ms 10.0.0.1
    2 38 ms 27 ms 22 ms c-73-52-56-1.hsd1.pa.comcast.net [73.52.56.1]
    3 11 ms 27 ms 28 ms te-0-7-0-3-sur01.montville.pa.pitt.comcast.net [68.85.43.13]
    4 27 ms 12 ms 15 ms te-0-7-0-9-ar03.lowerpaxton.pa.pitt.comcast.net [69.139.194.65]
    5 26 ms 19 ms 19 ms 69.139.168.185
    6 33 ms 48 ms 28 ms 68.86.166.189
    7 * * * Request timed out.
    8 28 ms 29 ms 42 ms ae2.er2.lga5.us.above.net [64.125.13.205]
    9 * 30 ms 42 ms ae5.cr2.lga5.us.above.net [64.125.21.82]
    10 110 ms 112 ms 112 ms xe-0-1-0.cr1.ams5.nl.above.net [64.125.27.186]
    11 124 ms 117 ms 131 ms ae1.er1.ams5.nl.above.net [64.125.22.62]
    12 130 ms 115 ms 117 ms 94.31.61.11.available.above.net [94.31.61.11]

    Trace complete.

    Tracing route to a3938.mindark.atom86.net [178.237.32.78]
    over a maximum of 30 hops:

    1 1 ms <1 ms <1 ms 10.0.0.1
    2 39 ms 12 ms 25 ms c-73-52-56-1.hsd1.pa.comcast.net [73.52.56.1]
    3 42 ms 11 ms 15 ms te-0-7-0-3-sur01.montville.pa.pitt.comcast.net [68.85.43.13]
    4 14 ms 11 ms 12 ms te-0-12-0-3-ar03.lancaster.pa.pitt.comcast.net [69.139.194.69]
    5 18 ms 18 ms 19 ms he-0-15-0-0-ar01.mckeesport.pa.pitt.comcast.net [69.139.168.141]
    6 25 ms 26 ms 25 ms he-4-5-0-0-cr01.ashburn.va.ibone.comcast.net [68.86.94.165]
    7 28 ms 25 ms 63 ms he-0-13-0-0-pe04.ashburn.va.ibone.comcast.net [68.86.87.6]
    8 24 ms 38 ms 23 ms xe-11-2-0.was10.ip4.gtt.net [173.241.131.61]
    9 113 ms 114 ms 113 ms xe-11-1-2.ams12.ip4.gtt.net [141.136.111.254]
    10 121 ms 119 ms 121 ms atom86-gw.ipv4.tinet.net [77.67.72.67]
    11 120 ms 117 ms 120 ms a3938.mindark.atom86.net [178.237.32.78]

    Trace complete.




    And another one that I just ran after it happening again for the 2nd time in 20 minutes

    Sun 08/03/2014
    03:39 PM

    Pinging login.entropiauniverse.com [94.31.61.10] with 32 bytes of data:
    Reply from 94.31.61.10: bytes=32 time=112ms TTL=117
    Reply from 94.31.61.10: bytes=32 time=112ms TTL=117
    Reply from 94.31.61.10: bytes=32 time=110ms TTL=117
    Reply from 94.31.61.10: bytes=32 time=109ms TTL=117
    Reply from 94.31.61.10: bytes=32 time=125ms TTL=117
    Reply from 94.31.61.10: bytes=32 time=108ms TTL=117
    Reply from 94.31.61.10: bytes=32 time=108ms TTL=117
    Reply from 94.31.61.10: bytes=32 time=110ms TTL=117
    Reply from 94.31.61.10: bytes=32 time=109ms TTL=117
    Reply from 94.31.61.10: bytes=32 time=108ms TTL=117

    Ping statistics for 94.31.61.10:
    Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 108ms, Maximum = 125ms, Average = 111ms

    Tracing route to 94.31.61.11.available.above.net [94.31.61.11]
    over a maximum of 30 hops:

    1 1 ms <1 ms <1 ms 10.0.0.1
    2 38 ms 27 ms 22 ms c-73-52-56-1.hsd1.pa.comcast.net [73.52.56.1]
    3 11 ms 27 ms 28 ms te-0-7-0-3-sur01.montville.pa.pitt.comcast.net [68.85.43.13]
    4 27 ms 12 ms 15 ms te-0-7-0-9-ar03.lowerpaxton.pa.pitt.comcast.net [69.139.194.65]
    5 26 ms 19 ms 19 ms 69.139.168.185
    6 33 ms 48 ms 28 ms 68.86.166.189
    7 * * * Request timed out.
    8 28 ms 29 ms 42 ms ae2.er2.lga5.us.above.net [64.125.13.205]
    9 * 30 ms 42 ms ae5.cr2.lga5.us.above.net [64.125.21.82]
    10 110 ms 112 ms 112 ms xe-0-1-0.cr1.ams5.nl.above.net [64.125.27.186]
    11 124 ms 117 ms 131 ms ae1.er1.ams5.nl.above.net [64.125.22.62]
    12 130 ms 115 ms 117 ms 94.31.61.11.available.above.net [94.31.61.11]

    Trace complete.

    Tracing route to a3938.mindark.atom86.net [178.237.32.78]
    over a maximum of 30 hops:

    1 1 ms <1 ms <1 ms 10.0.0.1
    2 39 ms 12 ms 25 ms c-73-52-56-1.hsd1.pa.comcast.net [73.52.56.1]
    3 42 ms 11 ms 15 ms te-0-7-0-3-sur01.montville.pa.pitt.comcast.net [68.85.43.13]
    4 14 ms 11 ms 12 ms te-0-12-0-3-ar03.lancaster.pa.pitt.comcast.net [69.139.194.69]
    5 18 ms 18 ms 19 ms he-0-15-0-0-ar01.mckeesport.pa.pitt.comcast.net [69.139.168.141]
    6 25 ms 26 ms 25 ms he-4-5-0-0-cr01.ashburn.va.ibone.comcast.net [68.86.94.165]
    7 28 ms 25 ms 63 ms he-0-13-0-0-pe04.ashburn.va.ibone.comcast.net [68.86.87.6]
    8 24 ms 38 ms 23 ms xe-11-2-0.was10.ip4.gtt.net [173.241.131.61]
    9 113 ms 114 ms 113 ms xe-11-1-2.ams12.ip4.gtt.net [141.136.111.254]
    10 121 ms 119 ms 121 ms atom86-gw.ipv4.tinet.net [77.67.72.67]
    11 120 ms 117 ms 120 ms a3938.mindark.atom86.net [178.237.32.78]

    Trace complete.




    Since i'm rather nub at these things does anyone have any advice? I tried calling my ISP but they wanted to charge me for info on this (complete BS imo). Any help would be appreciated.
     
  2. SallyBridges

    SallyBridges Adviser Arkadia Adviser

    Messages:
    703
    Likes Received:
    284
    Trophy Points:
    63
    I would say this isn't your ISP or the IP routing currently.

    I would say that this is more than lickley due to the reduced infrastructure that all Planets are currently running on due to the failure last weekend. That and Ned Kelly Smuggler Causing Chaos

    Server issues



    July 26,
    Entropia Universe had an unexpected production disturbance. It turned out that the root cause of the disturbance was hardware issues that resulted in failing servers. The failing hardware has now been removed. In the meantime we are running EU with reduced HW resources and that is the reason for the exceptional lag.
    Replacement hardware is scheduled for delivery beginning of next week. With the new and more powerful servers installed, end next week at the latest, we should see a considerable improvement of the lag situation.
    We are very sorry for this inconvenience and will get back to you when we have more information.
    Klas Moreau
    CEO MindArk


    If you really want to check then you might find the following useful - but then your going to need to get assistance from your ISP.
    I know this isnt your ISP but its got instructions on how to capture and analyse the data.

    http://community.plus.net/library/faults/using-wireshark-for-data-capture/
     
  3. Feynan

    Feynan Member

    Messages:
    25
    Likes Received:
    9
    Trophy Points:
    8
    This is no fun!

    I cant log in at all now!

    Server status:
    Some areas or services may be inaccessible.
    This does not have to affect your gameplay.

    Anyone know how long i will have to wait? :(



     
  4. SallyBridges

    SallyBridges Adviser Arkadia Adviser

    Messages:
    703
    Likes Received:
    284
    Trophy Points:
    63
  5. Feynan

    Feynan Member

    Messages:
    25
    Likes Received:
    9
    Trophy Points:
    8
    Nice

    Ty for the info Sally.
    This gave me some time to fix my profile on the forums, no harm done :)
     
  6. Craggan

    Craggan Member

    Messages:
    80
    Likes Received:
    18
    Trophy Points:
    8
    THanks Sally. I will look into this. The one reason I thought maybe that it was my ISP is because at one point i did see comcast.NY somewhere in the list right about where the request is timing out now. Things got a bit better later last night and haven't checked into it yet today so here's to hoping.
     

Share This Page