AMIA ARCHIVE • View topic

The server has been lagging huge, nine or more seconds delay on everything i do. I do not know where i post this but i figure here is ok. Anyone else noticing this? Is this going to be fixed?

it's unplayable indeed.

VodeAn wrote:

Is this going to be fixed?

It's being looked into, yes.

DerkDerkistan wrote:

VodeAn wrote:

Is this going to be fixed?

It's being looked into, yes.

Thanks for taking note, I want to add that the pin I get is extremely high, going from 1200-2500, when should be under 100 max 180 to me.

It seems very up and down for me, quite hard to debug I'm doing doing my best to resolve it.

When you get bad ping, please run a tracert on amiaworld.net. You do it like this: http://support247webs.com/windows-traceroute.htm

Post the results in this thread, they should look something like this:

Code:

  1    11 ms     1 ms     1 ms  192.168.1.254
  2    17 ms    19 ms    17 ms  82-168-149-254.ip.telfort.nl [82.168.149.254]
  3    19 ms    19 ms    21 ms  ams-ix.a2b-internet.com [195.69.144.209]
  4    31 ms    21 ms    52 ms  core5-alphen.a2b-internet.com [46.244.0.5]
  5    26 ms    29 ms    20 ms  mail.amiaworld.net [84.243.255.52]

Please use the code tag, that makes it a bit more readable.

Code:

Tracing route to amiaworld.net [84.243.255.52]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  BTHomeHub.home [192.168.1.254]
  2     6 ms     5 ms     5 ms  217.32.145.234
  3     6 ms     6 ms     5 ms  217.32.146.30
  4    13 ms    13 ms    13 ms  213.120.181.98
  5    13 ms    13 ms    13 ms  217.41.169.93
  6    14 ms    13 ms    13 ms  217.41.169.107
  7    13 ms    13 ms    13 ms  109.159.251.71
  8    25 ms    21 ms    24 ms  core1-te0-0-0-7.ealing.ukcore.bt.net [109.159.251.31]
  9    18 ms    17 ms    18 ms  core1-pos5-0-0.telehouse.ukcore.bt.net [194.74.65.122]
 10    18 ms    18 ms    17 ms  t2as1-tge1-4.uk-lon1.eu.bt.net [166.49.211.141]
 11    55 ms    20 ms    20 ms  166-49-211-38.eu.bt.net [166.49.211.38]
 12    26 ms    25 ms    26 ms  xe-2-1-0.ams12.ip4.tinet.net [213.200.80.17]
 13    27 ms    26 ms    25 ms  core4-tc2.a2b-internet.com [46.244.0.4]
 14    27 ms    26 ms    29 ms  core5-alphen.a2b-internet.com [46.244.0.5]
 15    28 ms    28 ms    28 ms  mail.amiaworld.net [84.243.255.52]

Trace complete.

This is what I get but as I only speak English and not nerd I have no idea what any of it means

I am the Master of Lag-Fu, stringing commands to my character based on snap predictions during combat. Swift calculative abilities surpass the restrictions of lag, allowing you to coordinate such beautiful moments of victory like the next series of frame updates showing nothing but your weaponmaster achieving several critical hits.

BAM

BAM

BAM.

....Smooth.

Code:

Tracing route to amiaworld.net [84.243.255.52]
over a maximum of 30 hops:

  1     1 ms     2 ms     2 ms  192.168.1.1
  2    64 ms    56 ms    70 ms  SUBS.cpiak3-l2.tranzpeer.net [101.98.0.53]
  3    62 ms    78 ms    67 ms  xe-8-0-1-100.cpcak3-r1.tranzpeer.net [101.98.3.1
3]
  4    63 ms    62 ms    59 ms  ae-4-20.cpcak3-r1.tranzpeer.net [101.98.3.9]
  5    82 ms    76 ms    81 ms  core2.cpcak3-r2.tranzpeer.net [101.98.2.230]
  6    77 ms    73 ms    75 ms  xe-4-0-3-10.cpcak4-r1.tranzpeer.net [101.98.3.97
]
  7     *       87 ms    76 ms  xe-4-0-2-10.cpcak4-r1.tranzpeer.net [101.98.3.96
]
  8    74 ms    86 ms    71 ms  ten-0-2-0.bdr01.akl05.akl.VOCUS.net.nz [175.45.1
02.17]
  9   210 ms   174 ms   206 ms  ten-0-1-0-2.cor01.akl05.akl.VOCUS.net.nz [114.31
.202.122]
 10   208 ms   156 ms   205 ms  ten-0-3-0-1.cor01.sjc01.ca.VOCUS.net [114.31.199
.31]
 11   188 ms   187 ms   193 ms  ten-0-3-0.bdr02.sjc01.ca.VOCUS.net [114.31.199.1
89]
 12   277 ms   317 ms   390 ms  10gigabitethernet3-2.core1.sjc1.he.net [64.71.18
4.45]
 13   239 ms   241 ms     *     10gigabitethernet1-4.core1.pao1.he.net [72.52.92
.113]
 14   308 ms   315 ms   325 ms  10gigabitethernet13-2.core1.ash1.he.net [184.105
.213.178]
 15   374 ms   361 ms   367 ms  10gigabitethernet1-2.core1.par2.he.net [184.105.
213.94]
 16     *      386 ms   353 ms  10gigabitethernet4-3.core1.ams1.he.net [184.105.
213.101]
 17   355 ms     *      350 ms  core4-tc2.a2b-internet.com [46.244.0.4]
 18   353 ms   360 ms   358 ms  core5-alphen.a2b-internet.com [46.244.0.5]
 19   359 ms   364 ms   367 ms  mail.amiaworld.net [84.243.255.52]

Trace complete.

1 <1 ms <1 ms <1 ms 192.168.1.1
2 5 ms 4 ms 5 ms 77.105.0.233
3 5 ms 5 ms 5 ms catalyst-12t.sezampro.rs [77.105.0.2
4 5 ms 5 ms 5 ms 178-253-193-17.adsl-a-10.sezampro.rs
3.17]
5 5 ms 5 ms 5 ms 46.107.27.65
6 12 ms 11 ms 11 ms 81.183.0.111
7 42 ms 42 ms 42 ms ams-ix.a2b-internet.com [195.69.144.
8 45 ms 45 ms 44 ms core5-alphen.a2b-internet.com [46.24
9 38 ms 38 ms 37 ms mail.amiaworld.net [84.243.255.52]

so still laggy as hell what does it all mean? Come on boffins fix eet!

Code:

tracert www.amiaworld.net

Tracing route to amiaworld.net [84.243.255.52]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  dslrouter.westell.com [192.168.1.1]
  2    29 ms    29 ms    28 ms  10.7.59.1
  3    30 ms    31 ms    55 ms  P0-3-0-5.PHLAPA-LCR-21.verizon-gni.net [130.81.1
93.176]
  4    28 ms    29 ms    29 ms  ae0-0.PHIL-BB-RTR1.verizon-gni.net [130.81.209.1
78]
  5    34 ms    35 ms    34 ms  0.xe-3-0-1.XL3.IAD8.ALTER.NET [152.63.3.61]
  6    34 ms    34 ms    34 ms  GigabitEthernet6-0-0.GW8.IAD8.ALTER.NET [152.63.
33.13]
  7    36 ms     *        *     tinet-gw.customer.alter.net [152.179.50.30]
  8   123 ms   123 ms   122 ms  xe-11-1-2.ams12.ip4.tinet.net [141.136.111.254]

  9   129 ms   131 ms   131 ms  core4-tc2.a2b-internet.com [46.244.0.4]
 10   129 ms   131 ms   132 ms  core5-alphen.a2b-internet.com [46.244.0.5]
 11   132 ms   129 ms   129 ms  mail.amiaworld.net [84.243.255.52]

Trace complete.

If it helps, it seems the high ping is only on server A, serve B does not seem to have it

Routenverfolgung zu amiaworld.net [84.243.255.52] über maximal 30 Abschnitte:

1 1 ms 2 ms 9 ms speedport.ip [192.168.2.1]
2 39 ms 39 ms 45 ms 217.0.116.218
3 40 ms 39 ms 41 ms 217.0.77.154
4 48 ms 43 ms 46 ms f-ed5-i.F.DE.NET.DTAG.DE [217.5.95.34]
5 44 ms 64 ms * 62.157.249.50
6 52 ms 57 ms 58 ms xe-8-3-0.ams12.ip4.tinet.net [89.149.181.209]
7 52 ms 52 ms 52 ms core4-tc2.a2b-internet.com [46.244.0.4]
8 53 ms 52 ms 62 ms core5-alphen.a2b-internet.com [46.244.0.5]
9 55 ms 54 ms 54 ms amiaworld.net [84.243.255.52]

Ablaufverfolgung beendet.

None of these tracerts show any spectacular nastiness. Well, the one from New Zealand does, but that's apparently being routed through a sheep's anus and I can't (or want to) do anything about that.

So, it's something with NWN itself. "Ping" basically means "time a program takes to answer", and if it's not the route to and from the program that's the problem, it must be the program itself.

Had a particularly interesting thing just happen. Lagging my way through Kohl - Tritemple District. Got hit with a massive lag spike, and got the 'entangled debuff' blinking on my screen. I could move (with latency) but could not open my inventory.

When I tried to transition, I got the loading screen for an unrelated area. And crashed immediately after.

Methinks its more than simple lag.

Is it just A or is it both servers?

It is just A, only has been A since this started AFAIK.

My results were fairly normal for my localisation.

Code:

Tracing route to amiaworld.net [84.243.255.52]
over a maximum of 30 hops:

  1    10 ms     8 ms    15 ms  10.62.0.1
  2     9 ms     7 ms     9 ms  riv3-ge4-0.gw.optusnet.com.au [198.142.163.221]

  3     9 ms    11 ms     8 ms  mas3-ge2-0.gw.optusnet.com.au [211.29.126.105]
  4   178 ms   163 ms   162 ms  203.208.174.85
  5   161 ms   174 ms   254 ms  ge-5-0-0-0.laxow-cr1.ix.singtel.com [203.208.183
.141]
  6   162 ms   182 ms   171 ms  ge-2-0-0-0.sngc3-dr1.ix.singtel.com [203.208.183
.38]
  7   318 ms   321 ms   321 ms  if-2-2.tcore2.LVW-LosAngeles.as6453.net [66.110.
59.2]
  8   321 ms   320 ms   337 ms  if-1-3.tcore2.NJY-Newark.as6453.net [64.86.252.5
8]
  9     *      321 ms     *     if-2-2.tcore1.NJY-Newark.as6453.net [66.198.70.1
]
 10   347 ms   357 ms   313 ms  if-7-2.tcore1.L78-London.as6453.net [66.198.70.2
6]
 11   348 ms   349 ms   339 ms  if-2-2.tcore2.L78-London.as6453.net [80.231.131.
1]
 12   316 ms   313 ms   313 ms  if-8-2.tcore2.AV2-Amsterdam.as6453.net [80.231.1
31.6]
 13   318 ms   319 ms   321 ms  if-11-2.tcore1.AD1-Amsterdam.as6453.net [80.231.
152.26]
 14   316 ms   315 ms   318 ms  gin-ad1-unet1.as6453.net [195.219.150.6]
 15   325 ms   331 ms   331 ms  core5-alphen.a2b-internet.com [46.244.0.5]
 16   320 ms   319 ms   321 ms  mail.amiaworld.net [84.243.255.52]

Trace complete.

C:\Users\PC>

I was on A at the time.

Aside from today where I felt no lag on B, late last night and the two or so days prior, I had massive lag on B, too.

I was on A aswell.

Code:

Microsoft Windows [Version 6.2.9200]
(c) 2012 Microsoft Corporation. All rights reserved.

C:\Users\Gregory>tracert 84.243.255.52:5121
Unable to resolve target system name 84.243.255.52:5121.

C:\Users\Gregory>tracert www.amiaworld.net

Tracing route to amiaworld.net [84.243.255.52]
over a maximum of 30 hops:

  1     2 ms     2 ms     5 ms  192.168.1.1
  2     *        *        *     Request timed out.
  3    86 ms     9 ms     9 ms  dtr01monrmi-tge-0-1-1-3.monr.mi.charter.com [96.
34.34.172]
  4    18 ms    24 ms    34 ms  crr02sgnwmi-tge-0-6-0-4.sgnw.mi.charter.com [96.
34.34.137]
  5    25 ms    33 ms    39 ms  bbr01sgnwmi-bue-2.sgnw.mi.charter.com [96.34.2.5
8]
  6    27 ms    28 ms    28 ms  cer-edge-17.inet.qwest.net [63.234.116.9]
  7    47 ms    32 ms    30 ms  chp-brdr-03.inet.qwest.net [67.14.8.194]
  8    26 ms    32 ms    25 ms  xe-4-1-0.chi12.ip4.tinet.net [173.241.131.37]
  9   139 ms   142 ms   130 ms  xe-2-0-0.ams12.ip4.tinet.net [89.149.186.246]
 10   127 ms   129 ms   125 ms  core4-tc2.a2b-internet.com [46.244.0.4]
 11   126 ms   131 ms   132 ms  core5-alphen.a2b-internet.com [46.244.0.5]
 12   125 ms   124 ms   130 ms  mail.amiaworld.net [84.243.255.52]

Trace complete.

C:\Users\Gregory>

I've had major lag on both servers, but people say A is worse. I've been staying away for the most part, which sucks cause this started about when I wanted to start coming back :<

Definitely laggy on both, though B does seem less, and more frequently normal. Only noticed the extremely high Pings on A though (been seeing them either -1 or around 2k fairly often).

Massive lags on both second ago, and traceroute requests pass with 15 hops and 32 ms at the end, so not a connection issue I think.

It more looks like a addition or a script problem is happening which is slowing down response time.

I first noticed heavy lag when people where shifting out of shapes rapidly (and using powers associated with those shapes) couple weeks ago, may be unrelated.

I feel some lag on B, but not serious, on the othe hand the issues are on A, so could say is on that server since the start.

Lagspikes related to shifting tend to be local client recomputing the modules. Although we did run a module version from a lag-free period and it didnt improve.

Could be a worse case scenario, could be a sign of Hard Drive failure.

On the bright side, there are a lot of bugs on random stuff happening that is making me laugh out loud:

http://puu.sh/3cPdA.jpg

Also, the servers work awfully good, as it should, when they are mostly empty. COINCIDENCE? I think not, mister.
Beside the obvious: I am starting to despair.

To laggy to play.

during some massive lag on A today (2 times), pings and traceroutes looked fine (115 ish ms on both).

Halecta wrote:

Could be a worse case scenario, could be a sign of Hard Drive failure.

Might be worth some downtime to run smart disk diagnostics and also memtest.

I'd hope it's not the hard drive, I think Disco recently replaced/upgraded it haha.

edit: I'm curious about the merits of completely wiping NWN from the server, reinstalling it and getting it all up and running fresh? Possibly doing it on a secondary hard drive so they can just be swapped out, even, then the first checked out. Yay for redundancy/fast turnarounds! I know how annoying redoing a hard drive can be XD

Oddly, occasionally Amia seems to block out entirely for me such that I can't access the website, tracert returns no results. And just before that I lost the ability to connect on NWN for similar results (but I could still get on the forums). This happened twice for me in the past few hours.

A's so bad I time out on area transitions.

Oh well, gives me time to work on a little surprise for everyone.

serbiris wrote:

Oddly, occasionally Amia seems to block out entirely for me such that I can't access the website, tracert returns no results. And just before that I lost the ability to connect on NWN for similar results (but I could still get on the forums). This happened twice for me in the past few hours.

Have you checked other servers to see if it's you and not them? (I know, redundancy ftw)

I just got booted from B and now I can't connect. I can get to A just fine :<

It is not happening to other servers, only Amia (primarily Amia A)

Dev Disco wrote:

None of these tracerts show any spectacular nastiness. Well, the one from New Zealand does, but that's apparently being routed through a sheep's anus and I can't (or want to) do anything about that.

P Three wrote:

serbiris wrote:

Oddly, occasionally Amia seems to block out entirely for me such that I can't access the website, tracert returns no results. And just before that I lost the ability to connect on NWN for similar results (but I could still get on the forums). This happened twice for me in the past few hours.

Have you checked other servers to see if it's you and not them? (I know, redundancy ftw)

In the first case I couldn't access any multiplayer stuff and in the second case it was just the Amia servers and the website. The rest of my internet was working fine, and it fixed without me doing anything on my end. It's utterly bizarre and I do feel it must be connected in some way to the problems of late. I still think it's a problem with NWN somewhere along the line, but it could've just been a spontaneous error for me.

Also, today Amia seemed to be working fine (or it was when I was playing for a couple hours, not long ago)

I've had it happen too, for little to no reason (everything else worked fine) but hasn't happened for a long time, thankfully.

I haven't been on A much lately but the last few times I've been on B I haven't noticed any lag other than the very slight lag I always get when I'm using the family internet at home.

It really does seem like a slow data access time. I'm getting a pretty consistent lag of about two seconds on every action on A unless it's inventory loading, in which case once I start opening bags it becomes quick. However, when I log out and back in (to unload my character data and force a fresh read) it has about two seconds of lag pulling up my inventory and bag contents until everything seems to be loaded to memory.

Eurgiga's right. I am having a very same situation.

It's impossible to play on either server, really. They either lag to unplayable levels, or die for extended periods, making people lose XP/Gold every time it crashes, even if they save. Tempted to just leave playing here well alone until the issues are settled, since it's a pain to get a group assembled, then have the server die as soon as we touch the first monster.

This lag is insane.. B just crashed.

Sorry guys, I know it's frustrating. Frustrating for us too. We're trying to get to the bottom of it.

No worries. But in light of this, I suppose events will necessarily be postponed until after the issue is resolved? Seems logical but I've learned better than to make assumptions.

B just booted me and I can't get back in. I was on A, used the rift portal to Shadowscape, then a few minutes later B stopped responding to commands (rest menu wouldn't come up, etc) and I was booted. Was able to connect to A, I was still at the rift when I logged in, clicking the rift gave the message that the server timed out.

Results of the ping and tracert:

Code:

Pinging 84.243.255.52 with 32 bytes of data:
Reply from 84.243.255.52: bytes=32 time=128ms TTL=115
Reply from 84.243.255.52: bytes=32 time=129ms TTL=115
Reply from 84.243.255.52: bytes=32 time=131ms TTL=115
Reply from 84.243.255.52: bytes=32 time=132ms TTL=115

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

Code:

Tracing route to mail.amiaworld.net [84.243.255.52]
over a maximum of 30 hops:

  1     3 ms     2 ms     2 ms  192.168.1.1
  2    39 ms    30 ms    29 ms  71.205.184.1
  3    12 ms    11 ms    11 ms  xe-9-1-0-32767-sur01.wbloomfield.mi.michigan.comcast.net [68.87.184.
121]
  4    16 ms    15 ms    19 ms  te-0-11-0-9-ar01.pontiac.mi.michigan.comcast.net [69.139.254.121]
  5    19 ms    23 ms    23 ms  he-4-4-0-0-cr01.350ecermak.il.ibone.comcast.net [68.86.90.113]
  6    34 ms    35 ms    36 ms  ix-8-0-3-0.tcore1.CT8-Chicago.as6453.net [64.86.137.25]
  7   130 ms   130 ms     *     if-12-6.tcore2.NYY-NewYork.as6453.net [216.6.99.45]
  8   130 ms   133 ms   128 ms  if-20-2.tcore2.L78-London.as6453.net [216.6.99.14]
  9   132 ms   130 ms   147 ms  if-7-2.tcore2.AV2-Amsterdam.as6453.net [80.231.152.13]
 10   131 ms   154 ms   129 ms  if-11-2.tcore1.AD1-Amsterdam.as6453.net [80.231.152.26]
 11   130 ms   130 ms   131 ms  gin-ad1-unet1.as6453.net [195.219.150.6]
 12   130 ms   131 ms   131 ms  core5-alphen.a2b-internet.com [46.244.0.5]
 13   133 ms   130 ms   128 ms  mail.amiaworld.net [84.243.255.52]

Trace complete.

massive lag

Who is online