Jump to content

Rabin_Uman

Member
  • Posts

    195
  • Joined

  • Last visited

  • Days Won

    3

Posts posted by Rabin_Uman

  1. I have had the longest period where I have not been able to patch.  It has happened before and I have posted at least once before about the problem.  In all previous cases it eventually solved itself, allowing me to patch.

    But this time I'm really worried, it is a long time.  In the forum I've followed the exchanges around the post from Javier23 and saw the request from Linus to run a tracer.  I ran it myself, and got the following results.  Can you identify the cause for the failure with this information?

    Tracing route to webpatch.ragnarok.co.kr [112.175.128.134]

    over a maximum of 30 hops:

      1    64 ms    36 ms     6 ms  10.133.128.1

      2    29 ms     8 ms     8 ms  10.133.4.1

      3     *        *        *     Request timed out.

      4    22 ms    35 ms    20 ms  10.192.55.53

      5    12 ms    23 ms    11 ms  10.192.41.165

      6    18 ms    29 ms    17 ms  10.192.12.38

      7    37 ms    38 ms    44 ms  38.88.165.29

      8    39 ms    54 ms    41 ms  be2582.ccr22.mia01.atlas.cogentco.com [154.54.31.157]

      9    81 ms    66 ms    64 ms  be2071.ccr22.iah01.atlas.cogentco.com [154.54.0.222]

     10   102 ms   102 ms   106 ms  be2066.ccr22.lax01.atlas.cogentco.com [154.54.7.54]

     11   125 ms   134 ms   116 ms  be2161.ccr22.sjc01.atlas.cogentco.com [154.54.27.170]

     12   123 ms   133 ms   115 ms  be2047.ccr21.sjc03.atlas.cogentco.com [154.54.5.114]

     13   116 ms   128 ms   127 ms  be2013.ccr21.sjc04.atlas.cogentco.com [154.54.5.106]

     14   121 ms   135 ms   115 ms  38.104.140.134

     15   256 ms   248 ms   259 ms  112.174.87.201

     16   246 ms   246 ms   252 ms  112.174.84.101

     17   269 ms   271 ms   246 ms  112.174.48.45

     18   249 ms   263 ms   248 ms  112.174.62.226

     19   248 ms   282 ms   247 ms  112.188.241.98

     20     *        *        *     Request timed out.

     21     *        *        *     Request timed out.

     22     *        *        *     Request timed out.

     23     *        *        *     Request timed out.

     24     *        *        *     Request timed out.

     25     *        *        *     Request timed out.

     26     *        *        *     Request timed out.

     27     *        *        *     Request timed out.

     28     *        *        *     Request timed out.

     29     *        *        *     Request timed out.

     30     *        *        *     Request timed out.

    Trace complete.

  2.  I ran the tracer, and the contents of the report fileare:

    Tracing route to webpatch.ragnarok.co.kr [112.175.128.134]

    over a maximum of 30 hops:

      1    64 ms    36 ms     6 ms  10.133.128.1

      2    29 ms     8 ms     8 ms  10.133.4.1

      3     *        *        *     Request timed out.

      4    22 ms    35 ms    20 ms  10.192.55.53

      5    12 ms    23 ms    11 ms  10.192.41.165

      6    18 ms    29 ms    17 ms  10.192.12.38

      7    37 ms    38 ms    44 ms  38.88.165.29

      8    39 ms    54 ms    41 ms  be2582.ccr22.mia01.atlas.cogentco.com [154.54.31.157]

      9    81 ms    66 ms    64 ms  be2071.ccr22.iah01.atlas.cogentco.com [154.54.0.222]

     10   102 ms   102 ms   106 ms  be2066.ccr22.lax01.atlas.cogentco.com [154.54.7.54]

     11   125 ms   134 ms   116 ms  be2161.ccr22.sjc01.atlas.cogentco.com [154.54.27.170]

     12   123 ms   133 ms   115 ms  be2047.ccr21.sjc03.atlas.cogentco.com [154.54.5.114]

     13   116 ms   128 ms   127 ms  be2013.ccr21.sjc04.atlas.cogentco.com [154.54.5.106]

     14   121 ms   135 ms   115 ms  38.104.140.134

     15   256 ms   248 ms   259 ms  112.174.87.201

     16   246 ms   246 ms   252 ms  112.174.84.101

     17   269 ms   271 ms   246 ms  112.174.48.45

     18   249 ms   263 ms   248 ms  112.174.62.226

     19   248 ms   282 ms   247 ms  112.188.241.98

     20     *        *        *     Request timed out.

     21     *        *        *     Request timed out.

     22     *        *        *     Request timed out.

     23     *        *        *     Request timed out.

     24     *        *        *     Request timed out.

     25     *        *        *     Request timed out.

     26     *        *        *     Request timed out.

     27     *        *        *     Request timed out.

     28     *        *        *     Request timed out.

     29     *        *        *     Request timed out.

     30     *        *        *     Request timed out.

    Trace complete.

    Can you identify what the problem is?

     

  3. Something went wrong after the reboot.  I played for about 1 hour, everything seemed fine.  Had to leave for about half an hour.  When I came back, my chars would not move, could not select.  Manually disconnected all 4 accounts and tried to log to no avail.  It shows 88 players on line. Then either "Server still recognizes your last log-in. Please try again after a few minutes (8), or gets to char selection and (after selecting) "Failed to Connect to Server".

    While I was typing, the Mao server went from Green to Red in the CP.  Guess that is the problem (and hope someone is taking care of it)

  4. I've had this problem before the server changes.  It comes and goes.  The best information I have been able to get is that the patch server is not available all the time.  When it is, you get the patch allow file and then you can patch.  Is this correct GMs?.  It is the same with other RO server I used to play on, which I used to keep up to date "just in case" but which I've been ignoring lately.  If you need this explained, just ask and I'll gladly do it.

×
×
  • Create New...