After Wedi's post and Nyr's reply this is the official. Unbearable lag thread. Whenever encountered with what you consider to be game affecting lag or an unintentional DC please include the following
1) PST/EST/GMT of the event or just say at the time of posting
2) IG time - early morning etc etc
3) On a scale of 1-10 how bad the lag is. 1 being one or two seconds sporadically, 5 being several seconds over a long peiod, and 10 being a full disconnect [not by the server].
We can fight lag, with data!
1) Last night, CST, late evening.
2) Can't recall the IG time.
3) 10. I had a few full disconnects and eventually just gave up went LD, even though I was just 2-3 rooms from a quit room. Moving from point A to point B was like molasses.
1) This morning, CST, 730-ish.
2) IG time ... morning-ish.
3) 2. Regular, noticeable, short lag. I haven't experienced lag on Arm in a very long time, so even this small amount stands out to me.
I bumped up a thread on the IDB to review the issue with the VPS host. We'll also see if ginka is causing some issues itself internally (seems unlikely, I've noted some lag in arm.org related tools).
1. Last night. Things were running okay until ~11:30pm CST.
2. I don't see how IG time could possibly be helpful. It lasted from mid-day until I managed to log off the next IG day.
3. 9. I didn't get DC'd, but the game would only respond to commands on 2-3 minute intervals.
It was bad on several occasions two days ago, too, but I don't remember the times.
The *lagmonster* Mangles you with its stupefyingly syrupy-slow sloth spell.
You watch helplessly as your clanmates try to regrasp reality by reconnecting repeatedly.
Strangers pass out using the unseen ways during long bouts of unnatural stillness.
Intimate situations become unbearably awkward as you begin to mount someone who seems to no longer be there.
The evil-carru defies the unnatural stillness despite the odds.
Those were word problem answers.
Seriously though:
1. I think the lag has been around the last few days CST
2. Any of the times of day, I generally play from 7am CST to after midnight CST
3. I've disconnected twice thinking the MUD was locked up because of lack of movements.
Some trouble here as well. So much lag last night, I gave up trying to play around 7PM MST.
1. The lag has been around the last few days MST
2. Any of the times of day, I generally play from 9am MST to 10PM MST
3. I've been disconnected numerous (more than 10) times over the last few days.
Shouldn't you all be fighting the lag with, you know, traceroutes?
Quote from: Marauder Moe on November 17, 2011, 03:20:13 PM
Shouldn't you all be fighting the lag with, you know, traceroutes?
The lag is on the game's side. So... traceroute doesn't do much to help.
Still lagged today when I was on at 11ish am pst
Quote from: Old Kank on November 17, 2011, 03:34:36 PM
Quote from: Marauder Moe on November 17, 2011, 03:20:13 PM
Shouldn't you all be fighting the lag with, you know, traceroutes?
The lag is on the game's side. So... traceroute doesn't do much to help.
While it is a possibility that it is something else, it's also important to note that traceroute would be a viable testing tool to either confirm or deny that fact.
We're looking into the matter.
Also, if you are finding that you are having trouble connecting, like every time you point your client to Armageddon it lags, please send a mail to morgenes (at) armageddon.org and cc mud (at) armageddon.org.
I've had consistent lag issues from 7-11PM PST for the last three days straight, along with lag connectivity client-side.
1. began 1:21 AM EST, seems ongoing (Edit: Seemed to stop sometime around 2:00-2:15 AM EST?)
2. happened during the early morning tick, possibly on the turnover from dawn to early morning?
3. I originally pegged it at around 6 on the bad scale, but right now I'd almost put it more about 8-9.
1:24 AM EST, Nov 18. Lag is about a 7 or 8 right now. My screen has been still for a good 20-30 seconds, and it crops up every few minutes or so, with "aftershocks" of 5s of lag every 10-15 seconds between the big spikes.
Quote from: Celest on November 18, 2011, 01:25:59 AM
1:24 AM EST, Nov 18. Lag is about a 7 or 8 right now. My screen has been still for a good 20-30 seconds, and it crops up every few minutes or so, with "aftershocks" of 5s of lag every 10-15 seconds between the big spikes.
Confirmed on my end too, my internet speed is fine.
1:32 AM EST, early morning in game right now. Definite lag.
Yup. definite crazy lag. Starting at about 1:00am EST, got really, really bad.
24 hrs ago. Increasing amounts of 20 sec + . Seemed to take half the morning to get across town.
(was hoping to hitch to someone without lag to take me there)
Today. Yep. Still lagging each step of the load in. Try again tomorrow.
Another series of pretty bad spikes at 1:40 EST :(
Yar. Bad lag spikes started around 1:00 am EST.
Quote from: Jeshin on November 17, 2011, 09:00:31 AM
After Wedi's post and Nyr's reply this is the official. Unbearable lag thread. Whenever encountered with what you consider to be game affecting lag or an unintentional DC please include the following
1) PST/EST/GMT of the event or just say at the time of posting
2) IG time - early morning etc etc
3) On a scale of 1-10 how bad the lag is. 1 being one or two seconds sporadically, 5 being several seconds over a long peiod, and 10 being a full disconnect [not by the server].
We can fight lag, with data!
1) 12:47 CST
2) High Sun
3) Pretty damn bad. I input a command at 12:45:10 and it finally returned to me at 12:46:33 -
That's a 1 minute 23 second lag.It also lagged getting the mantis to come up. For logging in. Not dying. Although that probably also lags.
Another at 1:50. I think whenever time "rolls over" an hour, it causes a huge lag spike. It seems to fit the intervals.
I'm getting the same lag as everyone else.
pinging ginka gives me:
Ping statistics for 209.159.155.236
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 90ms, Maximum = 91ms, Average = 90ms.
tracert didn't show much. Most of my hops average 60-90ms, but a couple servers 3-4 hops away from ginka occasionally give me ~150-200ms. These two:
ae1d0.mcr1.nyc-ny.us.xo.net
207.239.51.86
Edit: It's now 1:15 CST and the lag seems to have gone away.
Time: 2:32pm EST
Duration: About 5-10 seconds of no response from game after typing command.
Ping went through no timeouts... about 50ms average.
Tracert completed fine, no lag on trace.
Quote from: JustAnotherGuy on November 18, 2011, 02:32:49 PM
Time: 2:32pm EST
Duration: About 5-10 seconds of no response from game after typing command.
Ping went through no timeouts... about 50ms average.
Tracert completed fine, no lag on trace.
Experienced the same lag on the request tool, on my end, exactly one hour later (four mins from time posted).
Yeah, actually three of us were online trying to talk about important stuff, so we are very clear on the timestamps on this latest spike. Got some good data to look at at least to rule out some things, I hope.
More lag hit around 4:30 PM EST. Remains ongoing, time now at 5:08 pm EST. It comes and goes in spikes.
Lag at 4:35 EST.
Lasted about half a minute to a minute, wasn't really timing.
Hitting on and off a bit still, five minutes later.
Time: 5PM EST
Lag has been consistant for about 5 mins now, and it takes about 45 sec (which seems an hour! lol) To move between rooms or enter commands such as "Look Bow"
edit: just ended at 5:07 pm est
Lag was bad between 6PM and 7PM EST. Missed most of the Tuluki RPT.
right now, 7:22 PM Mountain time, really bad.
Which is 6:22 PST
Large spike at 6:15 PM PST.
Any word on what's going on from the provider?
Still. 9:50 P.M. EST. Late at night on Abid, the 157th Year of the Descending Sun. Anywhere from 3 to 20 second delay on all commands.
For the past couple hours or so, so from around 5pm PST through to nearly 7pm. So bad, I ended up logging out. It's unplayably bad. Nothing else seems to be lagging (other webpages). Just Arm.
Same here. Logged out. Lag was going to get someone killed. Same time as above.
Cruel lag, from 9:15 EST til now (10p EST)..
Oh, how I miss ranger quit right now.
By my diagnosis, the GAME itself is actually lagging. As in, combat, commands, everything. It freezes. Combat does not stack, and then spit at you, the entire game will literally freeze up and when the lag falls off, combat resumes as normal. That is my experience. I can't say how NPCs are acting.
Quote from: evilcabbage on November 20, 2011, 11:46:54 PM
By my diagnosis, the GAME itself is actually lagging. As in, combat, commands, everything. It freezes. Combat does not stack, and then spit at you, the entire game will literally freeze up and when the lag falls off, combat resumes as normal. That is my experience. I can't say how NPCs are acting.
Agreed. It doesn't seem that you are missing time to act, just that the whole thing slows to a crawl.
I don't believe this is a net issue, but rather an issue with the box that is running the game.
My co player disconnected a couple of times though.
Quote from: Iiyola on November 21, 2011, 02:02:08 AM
My co player disconnected a couple of times though.
Usually to fix lag people will discon/recon because often times it's a client-side issue.
However, this is not one of those times.
During a bout of serious lag this AM:
Tracing route to ginka.armageddon.org [209.159.155.236]
over a maximum of 30 hops:
1 2 ms 1 ms <1 ms 10.0.0.1
2 1 ms 1 ms 1 ms <super secret>
3 9 ms 10 ms 10 ms Springfield-NPEG1-2.vermontel.net [216.66.108.198]
4 10 ms 9 ms 9 ms vtelinet-216-66-108-206.vermontel.net [216.66.108.206]
5 11 ms 10 ms 12 ms vtelinet-216-66-108-10.vermontel.net [216.66.108.10]
6 14 ms 13 ms 14 ms vtelinet-216-66-105-18.vermontel.net [216.66.105.18]
7 14 ms 13 ms 14 ms te0-6-0-5.ccr21.bos01.atlas.cogentco.com [38.99.222.137]
8 23 ms 20 ms 20 ms te0-3-0-2.mpd21.jfk02.atlas.cogentco.com [154.54.44.13]
9 20 ms 18 ms 19 ms te0-0-0-0.ccr21.jfk07.atlas.cogentco.com [154.54.27.210]
10 19 ms 19 ms 20 ms abovenet.jfk07.atlas.cogentco.com [154.54.10.146]
11 409 ms 404 ms 407 ms 64.124.44.213.interserver.com [64.124.44.213]
12 21 ms 20 ms 20 ms edge-08-teb1.us.as19318.net [64.20.32.9]
13 20 ms 20 ms 21 ms openvz3.trouble-free.net [64.20.62.226]
14 20 ms 19 ms 20 ms ginka.armageddon.org [209.159.155.236]
Trace complete.
Seems the Lag is back in action.
1:03 pm pst
Yep, same.
Anyone else notice the lag spike around 1:15ish AM EST tonight?
Yuppers, still happening
Yes.
Brutal, like a kick between the legs.
Just checking in to mention the lag!
1:40 p.m., lasted for 2 minutes and about 30-40 seconds. INTENSE lag.
Question: Could a memory leak somewhere cause this much lag?
Lag horribly here as well PST 10:45 am
11:28 PM PST, over a minute.
Yep!
Game is chugging again now. Also had a hard time visiting the forums this morning around 2AM?
tracert armageddon.org
Tracing route to armageddon.org [209.159.155.236]
over a maximum of 30 hops:
1 1 ms 1 ms <1 ms zyxel.com [192.168.1.1]
2 6 ms 8 ms 9 ms cm1.eta244.maxonline.com.sg [116.88.244.1]
3 9 ms 8 ms 8 ms 172.20.52.17
4 7 ms 7 ms 10 ms 172.26.52.1
5 9 ms 10 ms 23 ms 172.20.7.86
6 7 ms 22 ms 12 ms 172.20.7.50
7 16 ms 11 ms 14 ms 203.116.245.101
8 82 ms 84 ms 79 ms p16-7-3-3.r23.tokyjp01.jp.bb.gin.ntt.net [129.250.12.141]
9 198 ms 78 ms 82 ms ae-4.r24.tokyjp01.jp.bb.gin.ntt.net [129.250.3.159]
10 150 ms 102 ms 86 ms ae-3.r22.osakjp01.jp.bb.gin.ntt.net [129.250.3.220]
11 88 ms 96 ms 86 ms ae-2.r21.osakjp01.jp.bb.gin.ntt.net [129.250.2.68]
12 203 ms 210 ms 216 ms as-1.r21.snjsca04.us.bb.gin.ntt.net [129.250.3.197]
13 * * * Request timed out.
14 212 ms 214 ms 204 ms 207.88.14.225.ptr.us.xo.net [207.88.14.225]
15 297 ms 298 ms 288 ms te-2-0-0.rar3.washington-dc.us.xo.net [207.88.12.70]
16 279 ms 286 ms 278 ms ae0d0.mcr1.newark-nj.us.xo.net [216.156.0.22]
17 286 ms 280 ms 285 ms ae1d0.mcr1.nyc-ny.us.xo.net [216.156.1.9]
18 272 ms 277 ms 269 ms 207.239.51.86
19 270 ms 280 ms 269 ms edge-08-teb1.us.as19318.net [64.20.32.9]
20 293 ms 290 ms 301 ms openvz3.trouble-free.net [64.20.62.226]
21 268 ms 278 ms 277 ms ginka.armageddon.org [209.159.155.236]
Trace complete.
Wow. 21 steps. :S
5 minutes ago, with a very very very long lag, it was like the game disconnected on me. My connection is finez.
Bad right now (maybe an 8 on the 1-10), 1:40pm-ish Pacific Time (IG early afternoon, but bad all day)
I never realized what you guys were talking about till I had a chance to play on peak a little.
The lag does not happen off peak.
6:39pm EST - been getting lag spikes since maybe just after 4pm. Sometimes it's fine, and sometimes there will be a lag spike.
Central Texas. 10:07 PM central time.
Tracing route to ginka.armageddon.org [209.159.155.236]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms . [192.168.2.1]
2 51 ms 25 ms 37 ms 10.31.32.1
3 15 ms 25 ms 29 ms host-173-45-192-1.tvmax.net [173.45.192.1]
4 23 ms 15 ms 9 ms ge-11-3-4.mpr1.iah63.us.above.net [64.125.194.10
9]
5 23 ms 31 ms 34 ms xe-3-1-0.cr2.iah1.us.above.net [64.125.30.38]
6 70 ms 48 ms 55 ms xe-2-1-0.cr2.dca2.us.above.net [64.125.28.49]
7 61 ms * 99 ms xe-3-2-0.cr2.lga5.us.above.net [64.125.26.110]
8 47 ms 48 ms 46 ms xe-0-0-1.er2.lga5.us.above.net [64.125.27.65]
9 105 ms 200 ms 219 ms 64.124.44.213.interserver.com [64.124.44.213]
10 41 ms 54 ms 43 ms edge-08-teb1.us.as19318.net [64.20.32.9]
11 69 ms 61 ms 46 ms openvz3.trouble-free.net [64.20.62.226]
12 56 ms 56 ms 54 ms ginka.armageddon.org [209.159.155.236]
Trace complete.
HO
LY
SHIT
It's been like 20-30 minutes now of NON STOP lag!
I'm barely lagging at all now. Woo!
Clearly we all logged off, thus no lag!
Was lagging intermittantly in small starts and stops from about 4:30pm until about 9:45ishpm (all times PST) when the HOLY WALL OF LAG hit, rendering it impossible to play.
Unpassable walls of lag at 3am-3:20am PST ... logged out rather than deal with it.
Biggest chug of a lag. 8.15pm GMT+8. I'm going to log out....unplayable. @_@
64.124.44.213.interserver.com [64.124.44.213] seems to be a common problem in at least two of the metrics.
Quote from: DustMight on November 23, 2011, 07:59:55 AM
64.124.44.213.interserver.com [64.124.44.213] seems to be a common problem in at least two of the metrics.
I ran my trace multiple times last night as I would get bits of lag lasting about 10 minutes at a time roughly every hour to every hour and a half. This was indeed the culprit for me.
maybe a 6.5 on the 1-10 around 11:00am Pacific time here in California.
TraceRoute to 209.159.155.236 [ginka.armageddon.org]
Hop (ms) (ms) (ms) IP Address Host name
1 12 0 0 206.123.64.154 jbdr2.0.dal.colo4.com
2 26 0 0 64.124.196.225 xe-4-2-0.er2.dfw2.us.above.net
3 29 0 0 64.125.27.81 xe-0-1-0.cr2.dfw2.us.above.net
4 5 5 5 64.125.26.134 xe-1-2-0.cr2.iah1.us.above.net
5 32 32 32 64.125.28.49 xe-2-1-0.cr2.dca2.us.above.net
6 37 46 65 64.125.26.106 xe-2-2-0.cr2.lga5.us.above.net
7 37 37 37 64.125.26.166 xe-1-0-1.er2.lga5.us.above.net
8 359 53 404 64.124.44.213 64.124.44.213.interserver.com
9 37 37 37 64.20.32.9 edge-08-teb1.us.as19318.net
10 37 37 37 64.20.62.226 openvz3.trouble-free.net
11 37 37 37 209.159.155.236 ginka.armageddon.org
Yeah, interserver is the host of Ginka from what I can tell. Pretty decent VPS packages.
Been lagging for a couple of minutes now. Nothing works.
It's been lagging for the past couple of hours (since around 11am PST) with horrible lag spikes continuously since around 12pm pst. Lag can last up to a few minutes at a time.
THE LAG GAAAH
According to their website, there was a root exploit patch implemented on 10/20/2011 and they asked customers to contact support to get the patch updated onto their assigned server.
There was also a set of patched updates on 10/23 and they asked customers to contact support to ensure that their server got patched.
No other "news" for non-customers to access, I couldn't find any outage page. That might be only accessible by logged in customers.
Not healthy at the moment?
Fight lag & crashes with metrics.
Quote from: Jeshin on November 29, 2011, 09:35:47 AM
Fight lag & crashes with metrics.
Fortunately, the game has not crashed. There was either a reboot or a crash 4 days ago.
4:30 EST and I'm getting a ton of lag.
5.30 GMT+8/+16
Right noooowww.
I've noticed that stamina and HPS don't regen during lag - but time SEEMS to continue on. Does thirst continue as normal while the lag goes on?
Perhaps people are going to get annoyed, but there are two lags going on, system lag and other lag. The system lag is what stalls everything in game. Game time is based on the machine time so it advances when the system time does, creating hikkups. During these hickups you will not regen stamina stun, but also wont loose it, but time moves normally. The other lag thats going on, well I'm sure you can all see where that is happening already, :)
La
_ __ _____ _ ag.
Seriously though, are we seeing any kind of diagnostic pattern here?
Quote from: Yasbusta on November 29, 2011, 04:53:30 PM
Perhaps people are going to get annoyed, but there are two lags going on, system lag and other lag. The system lag is what stalls everything in game. Game time is based on the machine time so it advances when the system time does, creating hikkups. During these hickups you will not regen stamina stun, but also wont loose it, but time moves normally. The other lag thats going on, well I'm sure you can all see where that is happening already, :)
During the system lag we were having last week, I checked and game time was running pretty close to normal (~10 minutes per ZT hour), but regeneration seemed
really slow. It's possible that was just lag anxiety affecting my perception, but at one point it took close to a RL hour for my character to regen their hp, and that seems excessively slow. Hard to really judge a consistent regen rate, though.
Quote from: Yasbusta on November 29, 2011, 04:53:30 PM
Perhaps people are going to get annoyed, but there are two lags going on, system lag and other lag. The system lag is what stalls everything in game. Game time is based on the machine time so it advances when the system time does, creating hikkups. During these hickups you will not regen stamina stun, but also wont loose it, but time moves normally. The other lag thats going on, well I'm sure you can all see where that is happening already, :)
I sort of figured, but that still doesn't answer whether thirst depletes, because I don't know if it's tied to the time mechanism (where every time the hour passes, I lose X thirst) or if it's tied to the system which is lagging. I ask because if it's the former, then you could basically get "trapped" in the lag outside and potentially dehydrate yourself to death (or strong impairment) without really being able to do much about it.
If you have a lag that lasts, basically, from Late Morning to High Sun, and then another that lasts between High Sun to Early Afternoon, then you've basically stood in the desert for two hours without drinking. You can see how this could quickly become a problem if thirst is tied to time, instead of the same system as health/stamina/movement, especially because you can get locked out of some areas at dusk.
As it is now I'm almost positive that the system (health/stamina/stun) regeneration is lagged with the rest of things, as is combat, but I still have concerns about thirst.
Yea, whats up with the sudden return of Lagzilla.
Internet Tokyo watch out.
(https://encrypted-tbn2.google.com/images?q=tbn:ANd9GcT5tTvwB3RyA2ZdMQjLnPnc6Sccd7v_GJRbiMOs3mudxUTpxSu5)
I got it, Ginka's new system has constipated itself after eating to many brainz.
ExLax for your moments of unbearable Lag:
(http://farm8.staticflickr.com/7007/6427279355_50aa584963_z.jpg)
Quote from: Celest on November 29, 2011, 05:01:38 PM
Quote from: Yasbusta on November 29, 2011, 04:53:30 PM
Perhaps people are going to get annoyed, but there are two lags going on, system lag and other lag. The system lag is what stalls everything in game. Game time is based on the machine time so it advances when the system time does, creating hikkups. During these hickups you will not regen stamina stun, but also wont loose it, but time moves normally. The other lag thats going on, well I'm sure you can all see where that is happening already, :)
I sort of figured, but that still doesn't answer whether thirst depletes, because I don't know if it's tied to the time mechanism (where every time the hour passes, I lose X thirst) or if it's tied to the system which is lagging. I ask because if it's the former, then you could basically get "trapped" in the lag outside and potentially dehydrate yourself to death (or strong impairment) without really being able to do much about it.
If you have a lag that lasts, basically, from Late Morning to High Sun, and then another that lasts between High Sun to Early Afternoon, then you've basically stood in the desert for two hours without drinking. You can see how this could quickly become a problem if thirst is tied to time, instead of the same system as health/stamina/movement, especially because you can get locked out of some areas at dusk.
As it is now I'm almost positive that the system (health/stamina/stun) regeneration is lagged with the rest of things, as is combat, but I still have concerns about thirst.
Fairly certain that thirst is based on both time and character, an issue you have to watch closely.
In his belly OF LAG, you will find a new definition of pain and suffering, as you are slowly digested over a thousand years.
Code-wise, I believe regeneration/degeneration of anything (hp, thirst, etc) is not tied to time, rather it's semi-random but requires the game's code processor to actually be ticking over. So if the game is lagging and missing ticks, yes, it will affect your regen. That should mean that thirst/hunger go more slowly, as will hp/stun/mana regen.
I'm getting so pissed off at the lag.
Meh. Unable to play on a rare day off this month. Alas.
Has the cause of the lag been determined yet?
Seems like it went away completely over the holiday weekend, and now it's back.
Yeah, very bad atm
Quote from: Talia on November 29, 2011, 05:32:30 PM
Code-wise, I believe regeneration/degeneration of anything (hp, thirst, etc) is not tied to time, rather it's semi-random but requires the game's code processor to actually be ticking over. So if the game is lagging and missing ticks, yes, it will affect your regen. That should mean that thirst/hunger go more slowly, as will hp/stun/mana regen.
That's really good to know, thank you :)
Also, it's baaaaaaack! Early Morning was the starting time IG, just like last time.
A change has been made server side, please speak up if you notice any more lag.
Morgenes, please tell me that the main event loop was doing a callback for every dung object.
Quote from: brytta.leofa on November 30, 2011, 03:41:04 PM
Morgenes, please tell me that the main event loop was doing a callback for every dung object.
No, in this case we don't believe the issue to be due to any changes or issues with Armageddon. It appears to be (have been hopefully) a server issue with our virtual server.
Seemed like there was a spot of lag just now, ~6:00-6:02 PM EST.
Alright, I went through the log I was keeping and couldn't correlate it, but it was 4 hours ago, so I might have missed it. I've added a time stamp to the log so hopefully if you can give me a time again when it happens, I'll be able to find it.
bilbo laggins, spotted 10:42 PM est
Ok, well if there was lag (not saying it wasn't), it appears to be different, as we aren't seeing the same symptoms in our server side as we were seeing before.
Just played for 4(ish) hours, didn't have any lag. Think the fix may be working!
*finds a piece of wood to knock on*
Oh, it might have been me. :-[
Getting lag surges at the moment. It will be fine for a bit and then suddenly lag, fine for a bit, then some lag again. 11:38 EST.
Caught a lag last night for a couple of seconds, but then had a strange and awesome echo.. is the Lag because staff is tinkering with something?
Probably important to run tracert's with new lag to confirm whether or not it's system or network lag.
Terrible lag and disconnects for the last quarter of an hour or so. 4pm Gmt, 11am EST I think.
I was having problems also with lag and connectivity.
If you experience a lag, please include a tracert to ginka in your post. Looking over the last two reports I am unable to correlate it to issues that we were seeing earlier.
How do you do a traceat to ginka?
Quote from: Booya on December 02, 2011, 02:18:16 PM
How do you do a traceat to ginka?
At your prompt:
> tracert ginka.armageddon.org
Tried it in my client and and it didn't work. :-[
Which prompt?
search for cmd.exe if you're using windows.
terminal, on mac.
I think you confused your mud prompt with command prompt.
Click your window's button (if you're using windows) then go to all programs, and under accessories you should see the command prompt.
Open it and then you can >tracert.
EDIT: Or better yet, do what Delirium said and search for cmd or terminal. After I figured out tracert, I don't think my lag is ginka, because the ginka.armageddon.org is only about ~47 milliseconds. Maybe it's our connections.
EDIT EDIT: My lag is, indeed, on my side. :/
Start > Run > cmd
Hokay thanks. Next question, is there a way to copy it or do you have to write it out by hand? It won't let me copy the usual ways.
Select all, then copy it. It's a pain but it's the only way.
3 pm pst, Lag-zilla rears its ugly head.
Quote from: Potaje on December 04, 2011, 06:02:37 PM
3 pm pst, Lag-zilla rears its ugly head.
I just went through the logs for the 6pm EST hour yesterday and didn't see anything that would indicate it from our side. Did you try a tracert?
Just after midnight, EST, 12-6-11..
The lag beastie cometh.
9:09 pm pst
Right now. Bad.
Mon Dec 5 22:11:25 MST 2011
traceroute to ginka.armageddon.org (209.159.155.236), 64 hops max, 4050 byte packets
1 192.168.1.1 (192.168.1.1) 5.343 ms 2.703 ms 2.421 ms
2 76.120.80.1 (76.120.80.1) 32.083 ms 57.835 ms 191.171 ms
3 te-7-4-ur04.arvada.co.denver.comcast.net (68.86.129.229) 15.402 ms 16.045 ms 36.671 ms
4 te-0-5-0-2-ar02.aurora.co.denver.comcast.net (68.86.179.245) 21.868 ms 27.428 ms 56.031 ms
5 pos-3-7-0-0-cr01.denver.co.ibone.comcast.net (68.86.91.101) 20.886 ms 62.134 ms 26.101 ms
6 pos-2-13-0-0-cr01.dallas.tx.ibone.comcast.net (68.86.86.210) 55.899 ms 93.913 ms 41.234 ms
7 pos-0-5-0-0-pe01.1950stemmons.tx.ibone.comcast.net (68.86.85.26) 54.753 ms 56.067 ms 55.624 ms
8 xe-5-1-0.er1.dfw2.us.above.net (64.125.13.185) 72.030 ms 64.778 ms 32.695 ms
9 xe-1-1-0.cr1.dfw2.us.above.net (64.125.26.209) 39.685 ms 73.747 ms 35.960 ms
10 xe-1-2-0.cr1.iah1.us.above.net (64.125.26.130) 60.250 ms 36.609 ms 57.743 ms
11 xe-0-0-0.cr2.iah1.us.above.net (64.125.30.66) 57.410 ms 62.393 ms 40.342 ms
12 xe-3-1-0.cr2.dca2.us.above.net (64.125.30.54) 71.455 ms 83.809 ms 89.859 ms
13 xe-2-2-0.cr2.lga5.us.above.net (64.125.26.106) 74.189 ms 76.566 ms 73.617 ms
14 xe-0-2-1.er2.lga5.us.above.net (64.125.30.210) 73.449 ms 76.490 ms 77.467 ms
15 64.124.44.213.interserver.com (64.124.44.213) 91.360 ms 91.937 ms 73.715 ms
16 edge-08-teb1.us.as19318.net (64.20.32.9) 89.547 ms 90.358 ms 134.374 ms
17 openvz3.trouble-free.net (64.20.62.226) 491.638 ms 381.069 ms 383.560 ms
18 ginka.armageddon.org (209.159.155.236) 362.043 ms !Z 409.321 ms !Z 409.856 ms !Z
For reference:
traceroute: Warning: www.google.com has multiple addresses; using 74.125.224.112
traceroute to www.l.google.com (74.125.224.112), 64 hops max, 52 byte packets
1 192.168.1.1 (192.168.1.1) 3.829 ms 1.347 ms 1.256 ms
2 76.120.80.1 (76.120.80.1) 42.229 ms 29.677 ms 25.186 ms
3 te-7-4-ur04.arvada.co.denver.comcast.net (68.86.129.229) 17.089 ms 36.389 ms 70.537 ms
4 te-0-8-0-1-ar02.aurora.co.denver.comcast.net (68.86.103.41) 19.881 ms 17.565 ms 15.435 ms
5 pos-3-8-0-0-cr01.denver.co.ibone.comcast.net (68.86.94.153) 16.588 ms 17.204 ms 16.340 ms
6 pos-2-13-0-0-cr01.dallas.tx.ibone.comcast.net (68.86.86.210) 31.928 ms 30.969 ms 31.923 ms
7 pos-0-9-0-0-pe01.1950stemmons.tx.ibone.comcast.net (68.86.88.198) 74.116 ms 30.758 ms 31.980 ms
8 75.149.231.70 (75.149.231.70) 88.084 ms 61.496 ms 64.048 ms
9 72.14.233.85 (72.14.233.85) 63.937 ms 62.460 ms
72.14.233.77 (72.14.233.77) 92.248 ms
10 72.14.237.219 (72.14.237.219) 67.622 ms
72.14.237.221 (72.14.237.221) 102.098 ms
72.14.237.215 (72.14.237.215) 65.853 ms
11 64.233.174.142 (64.233.174.142) 86.542 ms 64.705 ms 65.574 ms
12 64.233.174.205 (64.233.174.205) 67.939 ms
64.233.174.207 (64.233.174.207) 65.938 ms
64.233.174.205 (64.233.174.205) 112.310 ms
13 209.85.250.65 (209.85.250.65) 71.785 ms 66.648 ms 70.111 ms
14 64.233.174.109 (64.233.174.109) 79.496 ms 65.039 ms 66.751 ms
15 nuq04s08-in-f16.1e100.net (74.125.224.112) 62.508 ms 70.285 ms 136.587 ms
Ran these at 12:10AM EST. Also getting lag spikes in a constant ping... typically around 150-170ms. Looks to be Host again.
C:\Users\Knoxx>tracert www.armageddon.org
Tracing route to ginka.armageddon.org [209.159.155.236]
over a maximum of 30 hops:
1 1 ms <1 ms 1 ms 192.168.1.1
2 70 ms 24 ms 22 ms cpe-173-168-160-1.tampabay.res.rr.com [173.168.1
60.1]
3 19 ms 13 ms 14 ms gig12-0-0-2007.tampfledc-rtr2.tampflrdc.rr.com [
65.32.37.38]
4 11 ms 12 ms 12 ms 653213hfc142.tampabay.res.rr.com [65.32.13.142]
5 36 ms 37 ms 35 ms ae-5-10.cr0.dfw10.tbone.rr.com [66.109.6.106]
6 39 ms 41 ms 69 ms ae-1-0.pr0.dfw10.tbone.rr.com [66.109.6.179]
7 36 ms 38 ms 41 ms ip65-47-204-109.z204-47-65.customer.algx.net [65
.47.204.109]
8 68 ms 66 ms 71 ms 207.88.14.238.ptr.us.xo.net [207.88.14.238]
9 70 ms 70 ms 67 ms vb24.rar3.washington-dc.us.xo.net [207.88.12.34]
10 65 ms 121 ms 63 ms ae0d0.mcr1.newark-nj.us.xo.net [216.156.0.22]
11 64 ms 69 ms 66 ms ae1d0.mcr1.nyc-ny.us.xo.net [216.156.1.9]
12 212 ms 207 ms 199 ms 207.239.51.86
13 67 ms 66 ms 67 ms edge-08-teb1.us.as19318.net [64.20.32.9]
14 66 ms 67 ms 64 ms openvz3.trouble-free.net [64.20.62.226]
15 64 ms 82 ms 66 ms ginka.armageddon.org [209.159.155.236]
Trace complete.
C:\Users\Knoxx>tracert www.armageddon.org
Tracing route to ginka.armageddon.org [209.159.155.236]
over a maximum of 30 hops:
1 1 ms 2 ms 1 ms 192.168.1.1
2 26 ms 43 ms 30 ms cpe-173-168-160-1.tampabay.res.rr.com [173.168.1
60.1]
3 13 ms 30 ms 19 ms gig12-0-0-2007.tampfledc-rtr2.tampflrdc.rr.com [
65.32.37.38]
4 14 ms 28 ms 11 ms 653213hfc142.tampabay.res.rr.com [65.32.13.142]
5 37 ms 37 ms 60 ms ae-11-11.cr0.dfw10.tbone.rr.com [66.109.10.12]
6 35 ms 38 ms 34 ms ae-1-0.pr0.dfw10.tbone.rr.com [66.109.6.179]
7 41 ms 38 ms 40 ms ip65-47-204-109.z204-47-65.customer.algx.net [65
.47.204.109]
8 68 ms 65 ms 66 ms 207.88.14.238.ptr.us.xo.net [207.88.14.238]
9 70 ms 66 ms 70 ms vb24.rar3.washington-dc.us.xo.net [207.88.12.34]
10 68 ms 65 ms 69 ms ae0d0.mcr1.newark-nj.us.xo.net [216.156.0.22]
11 69 ms 64 ms 66 ms ae1d0.mcr1.nyc-ny.us.xo.net [216.156.1.9]
12 71 ms 203 ms 216 ms 207.239.51.86
13 67 ms 66 ms 68 ms edge-08-teb1.us.as19318.net [64.20.32.9]
14 66 ms 67 ms 65 ms openvz3.trouble-free.net [64.20.62.226]
15 66 ms 66 ms 68 ms ginka.armageddon.org [209.159.155.236]
Trace complete.
Veeeery bad lagspike atm
Yep, they are coming in spurts...
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Mike>tracert ginka.armageddon.org
Tracing route to ginka.armageddon.org [209.159.155.236]
over a maximum of 30 hops:
1 6 ms 2 ms 2 ms 192.168.1.1
2 40 ms 20 ms 29 ms 69.253.24.1
3 8 ms 9 ms 8 ms te-1-2-ur02.rt202.de.panjde.comcast.net [68.85.1
53.61]
4 9 ms 11 ms 11 ms te-8-4-ar02.wallingford.pa.panjde.comcast.net [6
8.86.211.230]
5 13 ms 10 ms 11 ms te-0-3-0-5-ar01.newcastle.de.panjde.comcast.net
[68.85.158.245]
6 10 ms 9 ms 9 ms xe-6-1-0-0-ar03.newcastle.de.panjde.comcast.net
[69.139.193.138]
7 13 ms 17 ms 14 ms pos-5-14-0-0-cr01.ashburn.va.ibone.comcast.net [
68.86.95.145]
8 * * * Request timed out.
9 16 ms 16 ms 16 ms xe-5-2-0.er2.iad10.us.above.net [64.125.12.77]
10 17 ms 18 ms 18 ms xe-2-0-0.cr2.dca2.us.above.net [64.125.31.209]
11 21 ms 20 ms 21 ms xe-2-2-0.cr2.lga5.us.above.net [64.125.26.106]
12 23 ms 22 ms 20 ms xe-0-2-1.er2.lga5.us.above.net [64.125.30.210]
13 21 ms 21 ms 21 ms 64.124.44.213.interserver.com [64.124.44.213]
14 38 ms 38 ms 37 ms edge-08-teb1.us.as19318.net [64.20.32.9]
15 227 ms 229 ms 231 ms openvz3.trouble-free.net [64.20.62.226]
16 274 ms 274 ms 271 ms ginka.armageddon.org [209.159.155.236]
Trace complete.
Big numbers on steps 15 and 16.
Flat out unplayable at the moment. Had to Still waiting to quit out.
*grunt*
C:\Documents and Settings\Aaron>Tracert 209.159.155.236
Tracing route to ginka.armageddon.org [209.159.155.236]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.0.1
2 39 ms 39 ms 39 ms ptld-dsl-gw44-236.ptld.qwest.net [207.225.84.236
]
3 39 ms 38 ms 38 ms ptld-agw1.inet.qwest.net [207.225.86.89]
4 43 ms 43 ms 43 ms sea-brdr-02.inet.qwest.net [67.14.41.18]
5 44 ms 43 ms 43 ms 206.111.7.153.ptr.us.xo.net [206.111.7.153]
6 46 ms 47 ms 47 ms vb2000d1.rar3.seattle-wa.us.xo.net [207.88.13.14
2]
7 126 ms 126 ms 123 ms te-4-0-0.rar3.denver-co.us.xo.net [207.88.12.82]
8 132 ms 131 ms 132 ms te-4-1-0.rar3.chicago-il.us.xo.net [207.88.12.21
]
9 127 ms 124 ms 126 ms vb24.rar3.washington-dc.us.xo.net [207.88.12.34]
10 145 ms 120 ms 120 ms ae0d0.mcr1.newark-nj.us.xo.net [216.156.0.22]
11 120 ms 120 ms 120 ms ae1d0.mcr1.nyc-ny.us.xo.net [216.156.1.9]
12 119 ms 119 ms 119 ms 207.239.51.86
13 122 ms 120 ms 121 ms edge-08-teb1.us.as19318.net [64.20.32.9]
14 119 ms 120 ms 120 ms openvz3.trouble-free.net [64.20.62.226]
15 121 ms 121 ms 121 ms ginka.armageddon.org [209.159.155.236]
Trace complete.
C:\Documents and Settings\Aaron>
Gave it one last ditch attempt, and the lag appears to have cleared up out of nowhere.
traceroute to ginka.armageddon.org (209.159.155.236), 64 hops max, 4050 byte packets
1 192.168.1.1 (192.168.1.1) 5.459 ms 2.322 ms 2.770 ms
2 76.120.80.1 (76.120.80.1) 32.366 ms 78.165 ms 159.681 ms
3 te-7-4-ur04.arvada.co.denver.comcast.net (68.86.129.229) 31.332 ms 36.901 ms 39.102 ms
4 te-0-5-0-2-ar02.aurora.co.denver.comcast.net (68.86.179.245) 21.641 ms 66.540 ms 47.964 ms
5 pos-3-7-0-0-cr01.denver.co.ibone.comcast.net (68.86.91.101) 45.751 ms 25.114 ms 39.697 ms
6 pos-2-13-0-0-cr01.dallas.tx.ibone.comcast.net (68.86.86.210) 54.163 ms 36.306 ms 77.128 ms
7 pos-0-5-0-0-pe01.1950stemmons.tx.ibone.comcast.net (68.86.85.26) 33.929 ms 35.252 ms 37.283 ms
8 xe-5-1-0.er1.dfw2.us.above.net (64.125.13.185) 53.730 ms 41.104 ms 72.037 ms
9 xe-0-1-0.cr1.dfw2.us.above.net (64.125.27.73) 41.967 ms 43.006 ms 68.247 ms
10 xe-2-1-0.cr1.iah1.us.above.net (64.125.30.57) 47.689 ms 41.206 ms 42.148 ms
11 xe-5-0-0.cr1.dca2.us.above.net (64.125.31.214) 73.537 ms 87.743 ms 92.875 ms
12 xe-1-0-0.cr2.dca2.us.above.net (64.125.28.250) 69.549 ms 71.627 ms 94.077 ms
13 xe-2-2-0.cr2.lga5.us.above.net (64.125.26.106) 105.931 ms 127.987 ms 75.655 ms
14 xe-0-2-1.er2.lga5.us.above.net (64.125.30.210) 116.909 ms 112.499 ms 78.408 ms
15 64.124.44.213.interserver.com (64.124.44.213) 84.867 ms 75.990 ms 78.556 ms
16 edge-08-teb1.us.as19318.net (64.20.32.9) 92.420 ms 90.870 ms 95.186 ms
17 openvz3.trouble-free.net (64.20.62.226) 396.214 ms 305.419 ms 304.355 ms
18 ginka.armageddon.org (209.159.155.236) 307.531 ms !Z 305.121 ms !Z 409.391 ms !Z
Perfect guys, I was able to correlate it to my log and have sent it off to our host to see if they can figure out what is going on.
Pinging 209.159.155.236 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 209.159.155.236:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
As of 12:45 PM EST, I am unable to connect to either the site or the mud through armageddon.org or 209.159.155.236: 4050. I can still connect through mudconnector, though.
Aaaand another bad lag spike.
Deleted mine, realized me being on a public hospital network is causing weird issues with repeated requests like ping or traceroute.
tracert ginka.armageddon.org
Tracing route to ginka.armageddon.org [209.159.155.236]
over a maximum of 30 hops:
1 194 ms 167 ms 166 ms nas7.2ny1.Level3.net [63.215.27.61]
2 166 ms 169 ms 167 ms ge-6-2-2.car2.Boston1.Level3.net [63.212.202.3]
3 179 ms 167 ms 177 ms ae-2-7.bar1.Boston1.Level3.net [4.69.132.242]
4 176 ms 167 ms 169 ms ae-8-8.ebr1.NewYork1.Level3.net [4.69.140.98]
5 181 ms 177 ms 177 ms ae-8-8.ebr1.NewYork1.Level3.net [4.69.140.98]
6 179 ms 177 ms 194 ms ae-3-3.ebr2.Washington1.Level3.net [4.69.132.89]
7 206 ms 177 ms 194 ms ae-3-3.ebr2.Washington1.Level3.net [4.69.132.89]
8 250 ms 187 ms 185 ms ae-1-60.edge1.Washington4.Level3.net [4.69.149.1
5]
9 185 ms 185 ms 187 ms ae-1-60.edge1.Washington4.Level3.net [4.69.149.1
5]
10 188 ms 177 ms 187 ms xe-5-1-0.cr2.dca2.us.above.net [64.125.29.77]
11 205 ms 194 ms 176 ms xe-5-1-0.cr2.dca2.us.above.net [64.125.29.77]
12 188 ms 204 ms 194 ms xe-1-0-1.er2.lga5.us.above.net [64.125.26.166]
13 188 ms 194 ms 195 ms xe-1-0-1.er2.lga5.us.above.net [64.125.26.166]
14 189 ms 194 ms 195 ms edge-08-teb1.us.as19318.net [64.20.32.9]
15 186 ms 195 ms 187 ms edge-08-teb1.us.as19318.net [64.20.32.9]
16 199 ms 185 ms 187 ms ginka.armageddon.org [209.159.155.236]
Trace complete.
Here's mine:
Ping:
~$ ping 209.159.155.236
PING 209.159.155.236 (209.159.155.236) 56(84) bytes of data.
64 bytes from 209.159.155.236: icmp_req=1 ttl=53 time=50.9 ms
64 bytes from 209.159.155.236: icmp_req=2 ttl=53 time=49.9 ms
64 bytes from 209.159.155.236: icmp_req=3 ttl=53 time=51.3 ms
64 bytes from 209.159.155.236: icmp_req=4 ttl=53 time=51.9 ms
64 bytes from 209.159.155.236: icmp_req=5 ttl=53 time=52.3 ms
Traceroute:
traceroute to 209.159.155.236 (209.159.155.236), 30 hops max, 60 byte packets
1 unknown (192.168.1.1) 2.981 ms 3.659 ms 5.824 ms
2 10.229.64.1 (10.229.64.1) 34.750 ms 39.435 ms 47.509 ms
3 network-024-029-002-149.cinci.rr.com (24.29.2.149) 51.632 ms 55.551 ms 58.779 ms
4 * tge7-1-1.tr00.clmkohpe.mwrtn.rr.com (65.25.137.85) 81.383 ms *
5 * * *
6 * 107.14.17.147 (107.14.17.147) 29.429 ms ae-1-0.pr0.chi10.tbone.rr.com (66.109.6.155) 25.489 ms
7 te1-2-0d0.cir1.chicago2-il.us.xo.net (216.156.72.5) 51.549 ms 216.156.72.133.ptr.us.xo.net (216.156.72.133) 53.655 ms te1-2-0d0.cir1.chicago2-il.us.xo.net (216.156.72.5) 51.902 ms
8 207.88.14.201.ptr.us.xo.net (207.88.14.201) 58.511 ms 60.033 ms 60.584 ms
9 ae0d0.mcr1.nyc-ny.us.xo.net (216.156.0.18) 54.965 ms 55.620 ms 56.811 ms
10 207.239.51.86 (207.239.51.86) 50.927 ms 54.720 ms 55.915 ms
11 edge-08-teb1.us.as19318.net (64.20.32.9) 57.819 ms 57.160 ms 58.394 ms
12 openvz3.trouble-free.net (64.20.62.226) 48.834 ms 52.415 ms 53.840 ms
13 ginka.armageddon.org (209.159.155.236) 56.733 ms !X 55.967 ms !X 54.476 ms !X
Yay! I've been wanting to do it.
1 1 ms 1 ms 1 ms 192.168.1.1
2 8 ms 29 ms 25 ms 10.122.220.1
3 14 ms 12 ms 31 ms brig-cam-1a-v109.network.virginmedia.net [80.3.66.73]
4 34 ms 11 ms 11 ms brig-core-1a-ge-011-0.network.virginmedia.net [195.182.174.29]
5 7 ms 8 ms 7 ms brig-core-2a-ae2-0.network.virginmedia.net [212.43.162.221]
6 9 ms 11 ms 31 ms glfd-bb-1a-ae6-0.network.virginmedia.net [213.105.159.153]
7 16 ms 13 ms 11 ms popl-bb-1b-ae7-0.network.virginmedia.net [213.105.159.62]
8 183 ms 123 ms 113 ms xe-1-0-0-xcr1.lsw.cw.net [166.63.211.129]
9 17 ms 15 ms 12 ms xe-5-1-0-xcr1.lnd.cw.net [195.2.25.133]
10 87 ms 87 ms 102 ms xe-5-3-0-xcr1.nyk.cw.net [195.2.25.197]
11 102 ms 87 ms 110 ms 198.32.118.45
12 85 ms 91 ms 117 ms edge-08-teb1.us.as19318.net [64.20.32.9]
13 87 ms 95 ms 103 ms openvz3.trouble-free.net [64.20.62.226]
14 112 ms 95 ms 84 ms ginka.armageddon.org [209.159.155.236]
Trace complete.
It's 5:55pm EST and my toon has been walking through [LOCATION REDACTED]. It takes 45 seconds to take a step.
It took me five minutes to get a round in at the bar.
Yar, so far, from 5:45 EST onward.. (now 6:P EST)
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Mike>tracert ginka.armageddon.org
Tracing route to ginka.armageddon.org [209.159.155.236]
over a maximum of 30 hops:
1 6 ms 2 ms 2 ms 192.168.1.1
2 30 ms 9 ms 10 ms 69.253.24.1
3 9 ms 9 ms 8 ms te-1-2-ur02.rt202.de.panjde.comcast.net [68.85.1
53.61]
4 9 ms 10 ms 9 ms te-8-4-ar02.wallingford.pa.panjde.comcast.net [6
8.86.211.230]
5 11 ms 10 ms 11 ms te-0-3-0-5-ar01.newcastle.de.panjde.comcast.net
[68.85.158.245]
6 9 ms 9 ms 9 ms xe-6-1-0-0-ar03.newcastle.de.panjde.comcast.net
[69.139.193.138]
7 14 ms 13 ms 13 ms pos-5-12-0-0-cr01.ashburn.va.ibone.comcast.net [
68.86.95.137]
8 15 ms 15 ms 13 ms pos-0-4-0-0-pe01.ashburn.va.ibone.comcast.net [6
8.86.86.146]
9 14 ms 13 ms 14 ms xe-5-2-0.er2.iad10.us.above.net [64.125.12.77]
10 16 ms 14 ms 16 ms xe-5-1-0.cr2.dca2.us.above.net [64.125.29.77]
11 20 ms 18 ms 24 ms xe-3-2-0.cr2.lga5.us.above.net [64.125.26.110]
12 22 ms 18 ms 21 ms xe-1-0-1.er2.lga5.us.above.net [64.125.26.166]
13 37 ms 28 ms 18 ms 64.124.44.213.interserver.com [64.124.44.213]
14 19 ms 19 ms 17 ms edge-08-teb1.us.as19318.net [64.20.32.9]
15 17 ms 18 ms 19 ms openvz3.trouble-free.net [64.20.62.226]
16 17 ms 18 ms 19 ms ginka.armageddon.org [209.159.155.236]
Trace complete.
Woah, lucky you.
We are taking action based on these so far, so now that we have a plan, it may be a better idea to hold off on data til after the move.
Roger. Even I got to provide a little bit of help!
I feel fuzzy.
I haven't been able to connect at all using 206.72.207.140. Is it still port 4050?
That is correct.
So far so good.
Quote from: Booya on December 07, 2011, 03:32:34 PM
I haven't been able to connect at all using 206.72.207.140. Is it still port 4050?
Can you ping it? Can you telnet it? Can you traceroute it?
tracert 206.72.207.140
Tracing route to 206.72.207.140 over a maximum of 30 hops
1 6 ms 1 ms 2 ms 192.168.1.1
2 23 ms 28 ms 23 ms 10.122.220.1
3 9 ms 7 ms 37 ms brig-cam-1b-v109.network.virginmedia.net [80.3.66.201]
4 12 ms 33 ms 20 ms brig-core-1b-ge-012-0.network.virginmedia.net [195.182.178.161]
5 37 ms 40 ms 9 ms brig-core-2b-ae2-0.network.virginmedia.net [212.43.162.225]
6 21 ms 14 ms 57 ms popl-bb-1b-ae14-0.network.virginmedia.net [213.105.159.157]
7 34 ms 20 ms 15 ms popl-bb-1a-ae0-0.network.virginmedia.net [213.105.174.229]
8 11 ms 11 ms 22 ms brnt-bb-1b-as4-0.network.virginmedia.net [62.255.81.238]
9 28 ms 11 ms 27 ms brnt-tmr-1-ae5-0.network.virginmedia.net [213.105.159.50]
10 40 ms 22 ms 12 ms telc-ic-1-as0-0.network.virginmedia.net [62.253.185.74]
11 30 ms 33 ms 30 ms te1-3.ccr01.lon04.atlas.cogentco.com [130.117.15.69]
12 29 ms 36 ms 23 ms te7-7.mpd02.lon01.atlas.cogentco.com [154.54.38.69]
13 104 ms 109 ms 111 ms te0-2-0-4.mpd22.lon13.atlas.cogentco.com [154.54.57.165]
14 97 ms 93 ms 95 ms te0-2-0-4.ccr22.bos01.atlas.cogentco.com [154.54.43.57]
15 111 ms 153 ms 119 ms te0-0-0-3.ccr22.jfk02.atlas.cogentco.com [154.54.6.10]
16 133 ms 207 ms 207 ms te2-3.ccr02.jfk01.atlas.cogentco.com [154.54.24.149]
17 98 ms 132 ms 102 ms te7-2.mag02.jfk01.atlas.cogentco.com [154.54.80.98]
18 89 ms 94 ms 95 ms vl3907.na31.b017536-1.jfk01.atlas.cogentco.com [38.20.42.66]
19 108 ms 99 ms 101 ms 38.105.245.50
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.
Looks like your trace is way different from mine. You're getting bogged down by a server I don't hit.
What does that mean? Might it be because i'm in England, UK?
Quote from: Booya on December 07, 2011, 04:06:36 PM
What does that mean? Might it be because i'm in England, UK?
Most people will have different traceroutes based on exactly that (different locations means that you go through different connections/different servers to reach your destination). I am assuming here that perhaps the next hop that you can't reach is another server prior to reaching the VPS host we use. I could be wrong, though...
No connecting for me either, also UK
traceroute 206.72.207.140
traceroute to 206.72.207.140 (206.72.207.140), 64 hops max, 52 byte packets
1 192.168.1.1 (192.168.1.1) 1.174 ms 0.882 ms 0.855 ms
2 10.121.28.1 (10.121.28.1) 9.939 ms 7.995 ms 7.444 ms
3 nrwh-cam-1b-ge92.network.virginmedia.net (81.100.32.129) 18.921 ms 9.421 ms 7.364 ms
4 pete-core-1b-ge-013-0.network.virginmedia.net (195.182.178.217) 12.522 ms 13.165 ms 20.655 ms
5 popl-bb-1b-as6-0.network.virginmedia.net (212.43.163.221) 16.583 ms 20.377 ms 16.931 ms
6 popl-bb-1a-ae0-0.network.virginmedia.net (213.105.174.229) 17.952 ms 29.247 ms 36.878 ms
7 brnt-bb-1b-as4-0.network.virginmedia.net (62.255.81.238) 27.942 ms 36.509 ms 25.113 ms
8 brnt-tmr-1-ae5-0.network.virginmedia.net (213.105.159.50) 20.116 ms 17.422 ms 31.832 ms
9 telc-ic-1-as0-0.network.virginmedia.net (62.253.185.74) 19.381 ms 19.233 ms 21.394 ms
10 te1-3.ccr01.lon04.atlas.cogentco.com (130.117.15.69) 38.427 ms 19.609 ms 20.123 ms
11 te7-7.mpd02.lon01.atlas.cogentco.com (154.54.38.69) 24.942 ms
te9-7.ccr01.lon01.atlas.cogentco.com (154.54.38.81) 34.861 ms
te7-7.mpd02.lon01.atlas.cogentco.com (154.54.38.69) 20.557 ms
12 * te0-0-0-4.mpd21.lon13.atlas.cogentco.com (154.54.57.102) 95.858 ms
te0-2-0-4.mpd22.lon13.atlas.cogentco.com (154.54.57.165) 98.178 ms
13 te0-6-0-3.mpd21.jfk02.atlas.cogentco.com (154.54.45.229) 94.838 ms
te0-3-0-4.ccr22.bos01.atlas.cogentco.com (154.54.5.122) 97.470 ms
te0-3-0-4.ccr21.bos01.atlas.cogentco.com (154.54.30.129) 101.187 ms
14 * te2-3.mpd01.jfk01.atlas.cogentco.com (154.54.24.145) 94.807 ms
te9-1.mpd01.jfk01.atlas.cogentco.com (154.54.1.173) 96.358 ms
15 te2-3.ccr02.jfk01.atlas.cogentco.com (154.54.24.149) 99.490 ms
te3-3.mpd01.jfk01.atlas.cogentco.com (154.54.1.210) 97.078 ms
te2-3.ccr02.jfk01.atlas.cogentco.com (154.54.24.149) 101.414 ms
16 vl3907.na31.b017536-1.jfk01.atlas.cogentco.com (38.20.42.66) 96.804 ms
te7-2.mag02.jfk01.atlas.cogentco.com (154.54.80.98) 96.933 ms
te7-1.mag02.jfk01.atlas.cogentco.com (154.54.80.94) 98.210 ms
17 vl3907.na31.b017536-1.jfk01.atlas.cogentco.com (38.20.42.66) 107.226 ms
vl3607.na31.b017536-1.jfk01.atlas.cogentco.com (38.20.42.62) 97.741 ms
vl3907.na31.b017536-1.jfk01.atlas.cogentco.com (38.20.42.66) 102.444 ms
18 38.105.245.50 (38.105.245.50) 92.946 ms * 93.222 ms
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
My next-to-last hop is 206.72.207.130. Try to tracert to that.
actually here's my tracert out of FL:
6 29 ms 29 ms 30 ms pos3-1.gw3.orl1.alter.net [157.130.86.145]
7 30 ms 31 ms 30 ms 0.so-2-0-3.xl3.orl4.alter.net [152.63.81.34]
8 58 ms 59 ms 58 ms 0.xe-8-0-0.xl1.mia19.alter.net [152.63.85.114]
9 60 ms 58 ms 66 ms 0.xe-10-0-0.br1.mia19.alter.net [152.63.85.82]
10 68 ms 73 ms 72 ms 204.255.168.238
11 53 ms 54 ms 56 ms ge-1-0-0.mpr1.mia1.us.above.net [64.125.30.193]
12 79 ms 80 ms 98 ms xe-4-3-0.cr1.dca2.us.above.net [64.125.30.198]
13 114 ms 113 ms 114 ms xe-2-2-0.cr1.lga5.us.above.net [64.125.26.98]
14 75 ms 76 ms 102 ms xe-1-0-0.cr2.lga5.us.above.net [64.125.29.46]
15 75 ms 75 ms 76 ms xe-1-0-1.er2.lga5.us.above.net [64.125.26.166]
16 89 ms 95 ms 75 ms 64.124.44.213.interserver.com [64.124.44.213]
17 75 ms 76 ms 76 ms edge-12-teb1.us.as19318.net [64.20.32.78]
18 81 ms 75 ms 76 ms openvz17.interserver.net [206.72.207.130]
19 76 ms 75 ms 77 ms 206.72.207.140
Trace complete.
Try to hit any of the server addresses between 11 and 19.
I didn't try them all from 11, but the ones I tried were fine until your 18th hop:
Tracing route to openvz17.interserver.net [206.72.207.130]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 192.168.1.1
2 44 ms 36 ms 30 ms 10.122.220.1
3 8 ms 29 ms 8 ms brig-cam-1a-v109.network.virginmedia.net [80.3.66.73]
4 28 ms 7 ms 16 ms brig-core-1a-ge-012-0.network.virginmedia.net [195.182.178.157]
5 10 ms 11 ms 12 ms brig-core-2a-ae2-0.network.virginmedia.net [212.43.162.221]
6 13 ms 11 ms 10 ms glfd-bb-1a-ae6-0.network.virginmedia.net [213.105.159.153]
7 75 ms 37 ms 58 ms brnt-bb-1b-ae2-0.network.virginmedia.net [212.43.163.90]
8 69 ms 39 ms 32 ms brnt-tmr-1-ae5-0.network.virginmedia.net [213.105.159.50]
9 25 ms 10 ms 18 ms telc-ic-1-as0-0.network.virginmedia.net [62.253.185.74]
10 41 ms 32 ms 32 ms te1-3.ccr01.lon04.atlas.cogentco.com [130.117.15.69]
11 15 ms 12 ms 14 ms te7-7.mpd02.lon01.atlas.cogentco.com [154.54.38.69]
12 106 ms 92 ms 115 ms te0-1-0-4.ccr22.lon13.atlas.cogentco.com [154.54.57.177]
13 95 ms 113 ms 90 ms te0-5-0-1.ccr22.jfk02.atlas.cogentco.com [154.54.30.134]
14 93 ms 112 ms 88 ms te2-3.ccr02.jfk01.atlas.cogentco.com [154.54.24.149]
15 91 ms 102 ms 122 ms te7-2.mag02.jfk01.atlas.cogentco.com [154.54.80.98]
16 92 ms 101 ms 91 ms vl3907.na31.b017536-1.jfk01.atlas.cogentco.com [38.20.42.66]
17 196 ms 143 ms 102 ms 38.105.245.50
18 * * * Request timed out.
19 * * * Request timed out.
etc.
This is all on mac terminal just in case anyone was wondering about the format:
traceroute 206.72.207.130
traceroute to 206.72.207.130 (206.72.207.130), 64 hops max, 52 byte packets
1 192.168.1.1 (192.168.1.1) 1.474 ms 0.894 ms 0.836 ms
2 10.121.28.1 (10.121.28.1) 8.930 ms 17.228 ms 11.085 ms
3 nrwh-cam-1b-ge92.network.virginmedia.net (81.100.32.129) 7.737 ms 11.453 ms 9.449 ms
4 pete-core-1b-ge-013-0.network.virginmedia.net (195.182.178.217) 11.497 ms 30.280 ms 28.686 ms
5 popl-bb-1b-as6-0.network.virginmedia.net (212.43.163.221) 16.901 ms 20.538 ms 20.713 ms
6 popl-bb-1a-ae0-0.network.virginmedia.net (213.105.174.229) 27.455 ms 22.046 ms 17.673 ms
7 brnt-bb-1b-as4-0.network.virginmedia.net (62.255.81.238) 19.438 ms 35.132 ms 19.911 ms
8 brnt-tmr-1-ae5-0.network.virginmedia.net (213.105.159.50) 20.561 ms 20.777 ms 98.868 ms
9 telc-ic-1-as0-0.network.virginmedia.net (62.253.185.74) 47.724 ms 25.558 ms 20.655 ms
10 te1-3.ccr01.lon04.atlas.cogentco.com (130.117.15.69) 22.233 ms 25.643 ms 20.478 ms
11 te9-7.ccr01.lon01.atlas.cogentco.com (154.54.38.81) 32.576 ms
te7-7.mpd02.lon01.atlas.cogentco.com (154.54.38.69) 40.286 ms
te9-7.ccr01.lon01.atlas.cogentco.com (154.54.38.81) 37.467 ms
12 te0-0-0-4.ccr21.lon13.atlas.cogentco.com (154.54.57.110) 102.254 ms
te0-1-0-4.ccr22.lon13.atlas.cogentco.com (154.54.57.177) 99.715 ms
te0-0-0-4.ccr21.lon13.atlas.cogentco.com (154.54.57.110) 98.375 ms
13 te0-1-0-4.ccr22.bos01.atlas.cogentco.com (130.117.0.185) 112.147 ms
te0-0-0-4.ccr21.bos01.atlas.cogentco.com (154.54.5.161) 98.578 ms
te0-5-0-1.ccr22.jfk02.atlas.cogentco.com (154.54.30.134) 121.557 ms
14 te9-1.ccr02.jfk01.atlas.cogentco.com (154.54.40.33) 97.759 ms
te0-0-0-3.ccr22.jfk02.atlas.cogentco.com (154.54.6.10) 100.625 ms
te9-8.ccr02.jfk01.atlas.cogentco.com (154.54.40.37) 97.676 ms
15 te7-2.mag01.jfk01.atlas.cogentco.com (154.54.80.90) 106.714 ms
te9-8.ccr02.jfk01.atlas.cogentco.com (154.54.40.37) 106.618 ms
te2-3.mpd01.jfk01.atlas.cogentco.com (154.54.24.145) 99.356 ms
16 te7-2.mag02.jfk01.atlas.cogentco.com (154.54.80.98) 99.565 ms
vl3907.na31.b017536-1.jfk01.atlas.cogentco.com (38.20.42.66) 96.032 ms
vl3607.na31.b017536-1.jfk01.atlas.cogentco.com (38.20.42.62) 97.076 ms
17 vl3907.na31.b017536-1.jfk01.atlas.cogentco.com (38.20.42.66) 99.658 ms 121.189 ms
38.105.245.50 (38.105.245.50) 90.930 ms
18 * 38.105.245.50 (38.105.245.50) 99.227 ms 104.904 ms
19 * * *
20 * * *
21 *
100% loss over here. Could give ya' a tracert, doubt it will be more helpful than what you've got.
(Vermont, btw)
Ah, here it is:
Tracing route to 206.72.207.140 over a maximum of 30 hops
1 2 ms 1 ms <1 ms 10.0.0.1
2 1 ms 1 ms <1 ms <supersecret>
3 10 ms 9 ms 10 ms Springfield-NPEG1-2.vermontel.net [216.66.108.198]
4 10 ms 10 ms 10 ms vtelinet-216-66-108-206.vermontel.net [216.66.108.206]
5 10 ms 10 ms 9 ms vtelinet-216-66-108-10.vermontel.net [216.66.108.10]
6 14 ms 15 ms 14 ms vtelinet-216-66-105-18.vermontel.net [216.66.105.18]
7 15 ms 13 ms 14 ms te0-6-0-5.ccr21.bos01.atlas.cogentco.com [38.99.222.137]
8 20 ms 19 ms 19 ms te0-2-0-1.mpd22.jfk02.atlas.cogentco.com [154.54.44.21]
9 20 ms 21 ms 20 ms te3-3.mpd01.jfk01.atlas.cogentco.com [154.54.1.210]
10 20 ms 20 ms 20 ms te7-1.mag01.jfk01.atlas.cogentco.com [154.54.80.86]
11 21 ms 20 ms 22 ms vl3607.na31.b017536-1.jfk01.atlas.cogentco.com [38.20.42.62]
12 20 ms 20 ms 19 ms 38.105.245.50
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 *
Same server as Spoon.
Tracing route to 206.72.207.140 over a maximum of 30 hops
3 * 1167 ms 1220 ms mdr-fid-int.akbr5.global-gateway.net.nz [202.37.
244.222]
4 43 ms 43 ms 44 ms ae4-10.akbr5.global-gateway.net.nz [202.37.244.2
21]
5 43 ms 44 ms 43 ms ae1-2.akbr4.global-gateway.net.nz [202.50.232.77
]
6 44 ms 43 ms 44 ms ae1-10.tkbr9.global-gateway.net.nz [202.50.232.3
7]
7 170 ms 168 ms 168 ms ae2-3.labr5.global-gateway.net.nz [203.96.120.14
2]
8 170 ms 167 ms 199 ms ae0-3.lebr6.global-gateway.net.nz [203.96.120.86
]
9 170 ms 168 ms 168 ms 205.158.79.141.ptr.us.xo.net [205.158.79.141]
10 168 ms 199 ms 167 ms te1-0-0d0.cir1.la3-ca.us.xo.net [207.88.15.29]
11 173 ms 223 ms 170 ms 207.88.14.217.ptr.us.xo.net [207.88.14.217]
12 242 ms 243 ms 248 ms vb15.rar3.dallas-tx.us.xo.net [207.88.12.45]
13 281 ms 276 ms 251 ms te-4-0-0.rar3.atlanta-ga.us.xo.net [207.88.12.1]
14 248 ms 252 ms 251 ms te-11-0-0.rar3.washington-dc.us.xo.net [207.88.1
2.10]
15 240 ms 262 ms 240 ms ae0d0.mcr1.newark-nj.us.xo.net [216.156.0.22]
16 241 ms 240 ms 241 ms ae1d0.mcr1.nyc-ny.us.xo.net [216.156.1.9]
17 240 ms 239 ms 238 ms 207.239.51.86
18 239 ms 238 ms 239 ms edge-12-teb1.us.as19318.net [64.20.32.78]
19 241 ms 270 ms 238 ms openvz17.interserver.net [206.72.207.130]
20 239 ms 238 ms 238 ms 206.72.207.140
Trace complete.
Well this looks like it's getting there?
But I'm not...
traceroute to 206.72.207.140 (206.72.207.140), 30 hops max, 60 byte packets
1 unknown (192.168.1.1) 13.047 ms 14.064 ms 14.045 ms
2 10.229.64.1 (10.229.64.1) 40.562 ms 40.562 ms 40.542 ms
3 network-024-029-002-149.cinci.rr.com (24.29.2.149) 40.523 ms 40.504 ms 40.539 ms
4 tge8-1-1.tr00.clmkohpe.mwrtn.rr.com (65.25.137.225) 40.517 ms 40.505 ms 40.486 ms
5 ae-4-0.cr0.chi30.tbone.rr.com (66.109.6.68) 51.348 ms 51.335 ms 51.313 ms
6 107.14.17.147 (107.14.17.147) 51.292 ms ae-1-0.pr0.chi10.tbone.rr.com (66.109.6.155) 51.709 ms 73.888 ms
7 216.156.72.157.ptr.us.xo.net (216.156.72.157) 73.822 ms 216.156.72.133.ptr.us.xo.net (216.156.72.133) 99.321 ms 99.314 ms
8 207.88.14.201.ptr.us.xo.net (207.88.14.201) 73.799 ms 74.891 ms 74.873 ms
9 ae0d0.mcr1.nyc-ny.us.xo.net (216.156.0.18) 73.719 ms 73.702 ms 73.737 ms
10 207.239.51.86 (207.239.51.86) 99.158 ms 77.086 ms 77.063 ms
11 edge-12-teb1.us.as19318.net (64.20.32.78) 77.057 ms 77.021 ms 77.016 ms
12 openvz17.interserver.net (206.72.207.130) 72.117 ms 72.160 ms 72.018 ms
13 206.72.207.140 (206.72.207.140) 72.033 ms !X 72.029 ms !X 72.101 ms !X
Same thing?
DNS is working for me now.
What happens when you try to connect, and what client are you trying to connect with?
Tried to connect with Mushclient, doesn't work. I could connect through this though: http://www.mudconnect.com/fmud/ (http://www.mudconnect.com/fmud/)
Also can't access the homepage. DNS is ginka.armageddon.org right?
Tracing route to ginka.armageddon.org [206.72.207.140]
over a maximum of 30 hops:
1 3 ms 1 ms 1 ms 192.168.1.1
2 6 ms 7 ms 19 ms 10.122.220.1
3 8 ms 8 ms 8 ms brig-cam-1b-v109.network.virginmedia.net [80.3.66.201]
4 23 ms 13 ms 10 ms brig-core-1b-ge-012-0.network.virginmedia.net[195.182.178.161]
5 7 ms 9 ms 9 ms brig-core-2b-ae2-0.network.virginmedia.net [212.43.162.225]
6 13 ms 12 ms 12 ms popl-bb-1b-ae14-0.network.virginmedia.net [213.105.159.157]
7 11 ms 11 ms 11 ms popl-bb-1a-ae0-0.network.virginmedia.net [213.105.174.229]
8 11 ms 15 ms 11 ms brnt-bb-1b-as4-0.network.virginmedia.net [62.255.81.238]
9 35 ms 11 ms 11 ms brnt-tmr-1-ae5-0.network.virginmedia.net [213.105.159.50]
10 24 ms 12 ms 12 ms telc-ic-1-as0-0.network.virginmedia.net [62.253.185.74]
11 11 ms 12 ms 13 ms te1-3.ccr01.lon04.atlas.cogentco.com [130.117.15.69]
12 12 ms 12 ms 12 ms te7-7.mpd02.lon01.atlas.cogentco.com [154.54.38.69]
13 89 ms 105 ms 88 ms te0-2-0-4.mpd22.lon13.atlas.cogentco.com [154.54.57.165]
14 89 ms 88 ms 89 ms te0-2-0-4.ccr22.bos01.atlas.cogentco.com [154.54.43.57]
15 100 ms 102 ms 98 ms te0-0-0-3.ccr22.jfk02.atlas.cogentco.com [154.54.6.10]
16 108 ms 91 ms 89 ms te2-3.ccr02.jfk01.atlas.cogentco.com [154.54.24.149]
17 93 ms 96 ms 91 ms te7-2.mag02.jfk01.atlas.cogentco.com [154.54.80.98]
18 90 ms 90 ms 106 ms vl3907.na31.b017536-1.jfk01.atlas.cogentco.com [38.20.42.66]
19 87 ms 99 ms 92 ms 38.105.245.50
20 * * * Request timed out.
21 * * * Request timed out.
etc.
Trace complete.
Quote from: Booya on December 08, 2011, 09:09:53 AM
...stuff...
Same here. Exactly, down to the IP where everything is dying.
Update at 0903 EST - unable to connect via mudconnector now also. Poor character is link dead!
We are engaging in discussion with the ISP that is having issues routing to our new IP.
Getting 100% pings back here in VT. FYI.
Morg and team - you are all great. Considering, especially, you are working for free!
Yup, working for me now too :)
Here's a tracert just for the hell of it:
Tracing route to 206.72.207.140 over a maximum of 30 hops
1 3 ms 1 ms 1 ms 192.168.1.1
2 7 ms 8 ms 41 ms 10.122.220.1
3 9 ms 27 ms 18 ms brig-cam-1b-v109.network.virginmedia.net [80.3.66.201]
4 38 ms 23 ms 7 ms brig-core-1b-ge-012-0.network.virginmedia.net [195.182.178.161]
5 38 ms 11 ms 19 ms brig-core-2b-ae2-0.network.virginmedia.net [212.43.162.225]
6 37 ms 11 ms 12 ms popl-bb-1b-ae14-0.network.virginmedia.net [213.105.159.157]
7 90 ms 10 ms 29 ms popl-bb-1a-ae0-0.network.virginmedia.net [213.105.174.229]
8 15 ms 15 ms 51 ms brnt-bb-1b-as4-0.network.virginmedia.net [62.255.81.238]
9 38 ms 11 ms 11 ms brnt-tmr-1-ae5-0.network.virginmedia.net [213.105.159.50]
10 37 ms 13 ms 35 ms telc-ic-1-as0-0.network.virginmedia.net [62.253.185.74]
11 33 ms 21 ms 13 ms te1-3.ccr01.lon04.atlas.cogentco.com [130.117.15.69]
12 * 34 ms 14 ms te7-7.mpd02.lon01.atlas.cogentco.com [154.54.38.69]
13 89 ms 90 ms 90 ms te0-2-0-4.mpd22.lon13.atlas.cogentco.com [154.54.57.165]
14 90 ms 91 ms 95 ms te0-2-0-4.ccr22.bos01.atlas.cogentco.com [154.54.43.57]
15 102 ms 100 ms 122 ms te0-0-0-3.ccr22.jfk02.atlas.cogentco.com [154.54.6.10]
16 94 ms 102 ms 106 ms te2-3.ccr02.jfk01.atlas.cogentco.com [154.54.24.149]
17 111 ms 96 ms 92 ms te7-2.mag02.jfk01.atlas.cogentco.com [154.54.80.98]
18 106 ms 110 ms 103 ms vl3907.na31.b017536-1.jfk01.atlas.cogentco.com [38.20.42.66]
19 101 ms 87 ms 111 ms 38.105.245.50
20 99 ms 113 ms 91 ms vl569.cr2.teb1.us.as19318.net [64.20.32.181]
21 100 ms 89 ms 93 ms 64.20.32.8
22 93 ms 86 ms 90 ms vl521.cr1.teb1.us.as19318.net [64.20.32.1]
23 100 ms 86 ms 87 ms edge-12-teb1.us.as19318.net [64.20.32.78]
24 95 ms 97 ms 87 ms openvz17.interserver.net [206.72.207.130]
25 87 ms 108 ms 95 ms 206.72.207.140
Thanks guys.
Our provider has fixed the issue. Thank you ALL for your willingness to help sort this out.
(http://i.huffpost.com/gen/263452/thumbs/s-BILL-AND-TED-large.jpg)
Quote from: Nyr on December 08, 2011, 08:33:14 AM
DNS is working for me now.
What happens when you try to connect, and what client are you trying to connect with?
KildClient and hitting a performing a SSL handshake.
I can connect with Mudlet, but not with KClient.
Quote from: Barsook on December 08, 2011, 07:36:28 PM
Quote from: Nyr on December 08, 2011, 08:33:14 AM
DNS is working for me now.
What happens when you try to connect, and what client are you trying to connect with?
KildClient and hitting a performing a SSL handshake.
Your telnet client is trying to work over SSL? ???
Dunno, I think that's how KClient is programed.
(To staff: I think this bit of topic needs to be split and made into another in Ask the Players -B)
Arm 1 does not work with SSL.
I figured. I dunno what's the problem. I just switched to Mudlet and I will stay on that one.
If you're having lag, remember. Metrics.
(http://i.imgur.com/nEmbg.jpg)
Having a lag / timeout connection at 2:22 pm EST
What she said below me!
What Jeshin said, only at 2:22pm EST with the clocks ahead.
Quote from: Jeshin on November 17, 2011, 09:00:31 AM
After Wedi's post and Nyr's reply this is the official. Unbearable lag thread. Whenever encountered with what you consider to be game affecting lag or an unintentional DC please include the following
1) PST/EST/GMT of the event or just say at the time of posting
2) IG time - early morning etc etc
3) On a scale of 1-10 how bad the lag is. 1 being one or two seconds sporadically, 5 being several seconds over a long peiod, and 10 being a full disconnect [not by the server].
We can fight lag, with data!
Started around or before 5:20 AM EST. Problem persists; it's 6:00 AM now and still going.
It was Dawn or Early Morning when it started. Dusk at the time of this post, and the lag continues.
On a scale of 1-10: 9. 5+ minutes to return output from commands, though no disconnect.
Output from commands has just gotten noticeably faster but its nothing to rp with. about a forty seconds to ninety to get commands returned, maybe?
Edit: Its like 6:14 now.
Does anyone have any actual metrics like traceroutes or ping results that back this up? That would be helpful!
traceroute to 206.72.207.140 (206.72.207.140), 30 hops max, 60 byte packets
1 unknown (192.168.1.1) 1.983 ms 1.976 ms 2.399 ms
2 10.169.64.1 (10.169.64.1) 17.962 ms 18.006 ms 18.313 ms
3 ae0-1030.cr02.dytnoh55.swo.rr.com (184.59.244.114) 22.261 ms 22.241 ms 22.632 ms
4 ae1.tr00.clevohek.mwrtn.rr.com (65.189.140.130) 29.997 ms 30.047 ms ae0.tr00.clevohek.mwrtn.rr.com (65.189.140.144) 30.451 ms
5 ae-3-0.cr0.dca20.tbone.rr.com (66.109.6.70) 43.516 ms 107.14.19.58 (107.14.19.58) 42.123 ms ae10-0.cr0.dca20.tbone.rr.com (107.14.19.14) 38.221 ms
6 107.14.19.135 (107.14.19.135) 38.842 ms 31.607 ms 31.194 ms
7 3-3.r1.dc.hwng.net (69.16.190.113) 59.513 ms 36.204 ms 36.217 ms
8 e1-4.r1.ny.hwng.net (209.197.0.34) 53.645 ms e4-2.r1.ny.hwng.net (209.197.0.42) 36.201 ms e1-4.r1.ny.hwng.net (209.197.0.34) 53.886 ms
9 209.197.17.198 (209.197.17.198) 54.185 ms 53.841 ms 54.538 ms
10 edge-12-teb1.us.as19318.net (64.20.32.78) 54.916 ms 36.775 ms 54.873 ms
11 openvz17.interserver.net (206.72.207.130) 54.048 ms 40.750 ms 40.652 ms
12 206.72.207.140 (206.72.207.140) 41.135 ms !X 41.513 ms !X 57.433 ms !X
What does !X stand for for traceroute on Linux?
Uh, I'm going to go out on a limb (and talk out my ass) and assume it's the same as an asterisks on DOS.
Packet loss.
Quote from: Barsook on June 12, 2012, 08:30:55 AM
traceroute to 206.72.207.140 (206.72.207.140), 30 hops max, 60 byte packets
1 unknown (192.168.1.1) 1.983 ms 1.976 ms 2.399 ms
2 10.169.64.1 (10.169.64.1) 17.962 ms 18.006 ms 18.313 ms
3 ae0-1030.cr02.dytnoh55.swo.rr.com (184.59.244.114) 22.261 ms 22.241 ms 22.632 ms
4 ae1.tr00.clevohek.mwrtn.rr.com (65.189.140.130) 29.997 ms 30.047 ms ae0.tr00.clevohek.mwrtn.rr.com (65.189.140.144) 30.451 ms
5 ae-3-0.cr0.dca20.tbone.rr.com (66.109.6.70) 43.516 ms 107.14.19.58 (107.14.19.58) 42.123 ms ae10-0.cr0.dca20.tbone.rr.com (107.14.19.14) 38.221 ms
6 107.14.19.135 (107.14.19.135) 38.842 ms 31.607 ms 31.194 ms
7 3-3.r1.dc.hwng.net (69.16.190.113) 59.513 ms 36.204 ms 36.217 ms
8 e1-4.r1.ny.hwng.net (209.197.0.34) 53.645 ms e4-2.r1.ny.hwng.net (209.197.0.42) 36.201 ms e1-4.r1.ny.hwng.net (209.197.0.34) 53.886 ms
9 209.197.17.198 (209.197.17.198) 54.185 ms 53.841 ms 54.538 ms
10 edge-12-teb1.us.as19318.net (64.20.32.78) 54.916 ms 36.775 ms 54.873 ms
11 openvz17.interserver.net (206.72.207.130) 54.048 ms 40.750 ms 40.652 ms
12 206.72.207.140 (206.72.207.140) 41.135 ms !X 41.513 ms !X 57.433 ms !X
What does !X stand for for traceroute on Linux?
but it's not lagging now I assume?
It's fine now, and my tracert looks normal.
It's fine.
I checked back to the times folks were posting in this thread this morning. There was definitely some strange stuff going on, but it is above my head. We will let you know once we have more information.
Quote from: Nyr on June 12, 2012, 09:21:06 AM
There was definitely some strange stuff going on
(http://orokos.com/odam/gremlins/511161.jpg)
Please continue to post here when you notice it, and use the 'traceroute ginka.armageddon.org' command with it so that we can verify if it is a network problem.
My roommate says there is a big lag going on right now, 8:45 pst.
Tracing route to 206.72.207.140 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms 192.168.0.1
2 39 ms 39 ms 39 ms ptld-dsl-gw44-236.ptld.qwest.net [207.225.84.236
]
3 39 ms 39 ms 39 ms ptld-agw1.inet.qwest.net [207.225.86.89]
4 43 ms 43 ms 43 ms sea-brdr-02.inet.qwest.net [67.14.41.18]
5 44 ms 44 ms 44 ms 63.146.26.82
6 44 ms 44 ms 45 ms xe-0-0-0.mpr2.sea1.us.above.net [64.125.31.10]
7 98 ms 98 ms 98 ms xe-1-2-0.cr2.ord2.us.above.net [64.125.31.2]
8 121 ms 121 ms 122 ms xe-4-0-0.cr2.lga5.us.above.net [64.125.31.73]
9 120 ms 121 ms 128 ms xe-0-0-1.er2.lga5.us.above.net [64.125.27.65]
10 121 ms 121 ms 121 ms 64.124.44.213.interserver.com [64.124.44.213]
11 122 ms 121 ms 121 ms edge-12-teb1.us.as19318.net [64.20.32.78]
12 121 ms 123 ms 123 ms openvz17.interserver.net [206.72.207.130]
13 121 ms 121 ms 122 ms 206.72.207.140
Trace complete.
I've been actively chatting on the game port with another staffer. Haven't seen any lag here. Can you be more specific? Big lag? What happened? How long?
Quote from: Nyr on June 12, 2012, 11:57:50 AM
I've been actively chatting on the game port with another staffer. Haven't seen any lag here. Can you be more specific? Big lag? What happened? How long?
Has happened 2 times over the last few days.
Game runs fine. Then at around 11am GMT +1, it slows to a crawl. Slow meaning.. You can look. But can't do actions (unless you want for about 30+ seconds). Disconnect from the game. Try to reconnect. Mud prompt says "connected" then hangs before the entry screen of arm shows up. Hangs for.. minutes usually before you get in.
This lasts for about 1-2 hours it seems.
I log in and it seems from my end its evened out, he said that about an hour ago he was lagging between 1 min and two.
To clarify, I didn't mean in general, I was responding to Potaje's post referring to lag just now.
When it happens again please have the other person do the ping/tracert, since it didn't seem to show anything when you did it.
Quote from: Nyr on June 12, 2012, 12:16:49 PM
To clarify, I didn't mean in general, I was responding to Potaje's post referring to lag just now.
When it happens again please have the other person do the ping/tracert, since it didn't seem to show anything when you did it.
Will do, thank you.
Getting lag spikes. Probably my internet even though my traceroute seems fine. Because the forums got a lag spike too.
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Rogue Gunslinger>tracert armageddon.org
Tracing route to armageddon.org [206.72.207.140]
over a maximum of 30 hops:
1 1 ms 2 ms 2 ms 192.168.0.1
2 42 ms 43 ms 42 ms phnx-dsl-gw66.phnx.qwest.net [67.40.227.66]
3 43 ms 42 ms 44 ms phnx-agw1.inet.qwest.net [75.160.238.9]
4 54 ms 54 ms 55 ms lap-brdr-03.inet.qwest.net [67.14.22.78]
5 54 ms 55 ms 54 ms xe-0-1-0.mpr1.lax12.us.above.net [64.125.12.25]
6 82 ms 54 ms 57 ms xe-3-0-0.cr2.lax112.us.above.net [64.125.30.29]
7 82 ms 82 ms 81 ms xe-2-3-0.cr2.iah1.us.above.net [64.125.25.17]
8 138 ms 122 ms 114 ms xe-3-1-0.cr2.dca2.us.above.net [64.125.30.54]
9 116 ms 115 ms 116 ms xe-2-2-0.cr2.lga5.us.above.net [64.125.26.106]
10 115 ms 115 ms 115 ms xe-0-2-1.er2.lga5.us.above.net [64.125.30.210]
11 115 ms 116 ms 115 ms 64.124.44.213.interserver.com [64.124.44.213]
12 116 ms 116 ms 116 ms edge-12-teb1.us.as19318.net [64.20.32.78]
13 116 ms 116 ms 116 ms openvz17.interserver.net [206.72.207.130]
14 116 ms 116 ms 116 ms 206.72.207.140
I've been getting some too, but didn't get any tracerts.
hitting some lag spikes.
Tracing route to 206.72.207.140 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms 192.168.0.1
2 39 ms 39 ms 39 ms ptld-dsl-gw44-236.ptld.qwest.net [207.225.84.236
]
3 39 ms 40 ms 39 ms ptld-agw1.inet.qwest.net [207.225.86.89]
4 42 ms 77 ms 43 ms sea-brdr-02.inet.qwest.net [67.14.41.18]
5 43 ms 43 ms 43 ms 63.146.26.82
6 44 ms 44 ms 44 ms xe-1-0-0.mpr2.sea1.us.above.net [64.125.31.14]
7 98 ms 98 ms 98 ms xe-1-2-0.cr2.ord2.us.above.net [64.125.31.2]
8 120 ms 121 ms 121 ms xe-4-0-0.cr2.lga5.us.above.net [64.125.31.73]
9 121 ms 120 ms 120 ms xe-0-0-1.er2.lga5.us.above.net [64.125.27.65]
10 317 ms 125 ms 189 ms 64.124.44.213.interserver.com [64.124.44.213]
11 122 ms 121 ms 120 ms edge-12-teb1.us.as19318.net [64.20.32.78]
12 122 ms 122 ms 122 ms openvz17.interserver.net [206.72.207.130]
13 121 ms 121 ms 122 ms 206.72.207.140
Trace complete.
Its just horrid right now. I can't even reconnect.
Same:
1 5 ms 5 ms 7 ms 192.168.1.1
2 8 ms 11 ms 11 ms 10.123.32.1
3 13 ms 11 ms 12 ms ten0-1-0-7.orld14-ser2.bhn.net [72.31.194.40]
4 20 ms 23 ms 22 ms ten0-11-0-4.orld71-car2.bhn.net [97.69.193.190]
5 18 ms 16 ms 15 ms hun0-7-0-0.orld71-cbr3.bhn.net [72.31.193.24]
6 23 ms 35 ms 24 ms ae-4-11.cr1.atl20.tbone.rr.com [66.109.10.14]
7 39 ms 39 ms 48 ms 107.14.19.36
8 42 ms 47 ms 55 ms ae-4-0.cr0.dca10.tbone.rr.com [66.109.6.33]
9 68 ms 39 ms 48 ms 107.14.19.133
10 38 ms 44 ms 37 ms 3-3.r1.dc.hwng.net [69.16.190.113]
11 61 ms 68 ms 64 ms e1-4.r1.ny.hwng.net [209.197.0.34]
12 61 ms 60 ms 73 ms 209.197.17.198
13 72 ms 79 ms 59 ms edge-12-teb1.us.as19318.net [64.20.32.78]
14 68 ms 66 ms 70 ms openvz17.interserver.net [206.72.207.130]
15 67 ms 60 ms 58 ms 206.72.207.140
Trace complete.
Looks like uh... nothing's wrong with the trace. Gremlins in the pipes somewhere deeper, me thinks.
Edit: On the plus side, now we can all figure out what cities we all live in based on our traces. Whee.
Lagspike atm.
The request tool seemed a bit laggy too.
The lag is fighting back Ohgod!
3 or 4 minute delays on commands going through
Tracing route to 206.72.207.140 over a maximum of 30 hops
1 8 ms 21 ms 7 ms xx.x.xxx.xx
2 11 ms 11 ms 14 ms rd1cv-ge3-3-1.gv.shawcable.net [64.59.166.114]
3 12 ms 15 ms 16 ms 66.163.78.90
4 29 ms 27 ms 27 ms 66.163.78.174
5 26 ms 26 ms 27 ms rc2ar-ge9-2.ed.shawcable.net [66.163.70.9]
6 49 ms 56 ms 48 ms 66.163.78.138
7 69 ms 76 ms 69 ms rc1sh-pos13-0.mt.shawcable.net [66.163.76.73]
8 80 ms 94 ms 88 ms rc1hu-pos1-0.ny.shawcable.net [66.163.76.14]
9 81 ms 77 ms 82 ms rd1ny-ge5-0-0.ny.shawcable.net [66.163.74.21]
10 150 ms 212 ms 199 ms 198.32.118.45
11 81 ms 77 ms 82 ms edge-12-teb1.us.as19318.net [64.20.32.78]
12 88 ms 108 ms 94 ms openvz17.interserver.net [206.72.207.130]
13 92 ms 81 ms 80 ms 206.72.207.140
This is what the King's Age brings! I say BLAH to it then!
In the grim darkness of the present... there is only lag.
Quote from: jstorrie on June 14, 2012, 08:10:22 PM
In the grim darkness of the present... there is only lag.
+1 for the reference.
Tracing route to ginka.armageddon.org [206.72.207.140]
over a maximum of 30 hops:
5 17 ms 31 ms 19 ms 12.249.212.21
6 18 ms 19 ms 19 ms cr1.cgcil.ip.att.net [12.122.99.22]
7 20 ms 12 ms 19 ms cgcil02jt.ip.att.net [12.122.81.17]
8 13 ms 17 ms 19 ms 192.205.36.30
9 13 ms 15 ms 14 ms xe-1-3-0.cr2.ord2.us.above.net [64.125.30.146]
10 301 ms 234 ms 193 ms xe-4-0-0.cr2.lga5.us.above.net [64.125.31.73]
11 180 ms 90 ms 36 ms xe-0-2-1.er2.lga5.us.above.net [64.125.30.210]
12 40 ms 38 ms 37 ms 64.124.44.213.interserver.com [64.124.44.213]
13 40 ms 54 ms 42 ms edge-12-teb1.us.as19318.net [64.20.32.78]
14 48 ms 37 ms 50 ms openvz17.interserver.net [206.72.207.130]
15 35 ms 44 ms 37 ms 206.72.207.140
Trace complete.
traceroute to ginka.armageddon.org (206.72.207.140), 64 hops max, 52 byte packets
1 192.168.1.254 (192.168.1.254) 1.758 ms 8.149 ms 1.638 ms
2 d66-183-96-254.bchsia.telus.net (66.183.96.254) 18.148 ms 18.068 ms 9.087 ms
3 173.182.196.1 (173.182.196.1) 9.042 ms 26.282 ms 18.447 ms
4 vancbc01gr01.bb.telus.com (154.11.10.10) 18.977 ms 14.929 ms 12.122 ms
5 205.185.218.69 (205.185.218.69) 11.191 ms 14.831 ms 23.443 ms
6 unknown.hwng.net (209.197.0.249) 94.162 ms 89.995 ms 97.211 ms
7 unknown.hwng.net (209.197.0.38) 122.503 ms 123.367 ms 123.136 ms
8 209.197.17.198 (209.197.17.198) 77.473 ms 83.457 ms 78.888 ms
9 edge-12-teb1.us.as19318.net (64.20.32.78) 79.209 ms
209.197.17.198 (209.197.17.198) 85.553 ms 91.150 ms
10 edge-12-teb1.us.as19318.net (64.20.32.78) 83.287 ms 85.559 ms 82.648 ms
11 openvz17.interserver.net (206.72.207.130) 88.370 ms 85.054 ms 83.717 ms
12 206.72.207.140 (206.72.207.140) 83.289 ms !Z 91.992 ms !Z 76.097 ms !Z
traceroute to ginka.armageddon.org (206.72.207.140), 64 hops max, 52 byte packets
1 192.168.1.254 (192.168.1.254) 1.758 ms 8.149 ms 1.638 ms
2 d66-183-96-254.bchsia.telus.net (66.183.96.254) 18.148 ms 18.068 ms 9.087 ms
3 173.182.196.1 (173.182.196.1) 9.042 ms 26.282 ms 18.447 ms
4 vancbc01gr01.bb.telus.com (154.11.10.10) 18.977 ms 14.929 ms 12.122 ms
5 205.185.218.69 (205.185.218.69) 11.191 ms 14.831 ms 23.443 ms
6 unknown.hwng.net (209.197.0.249) 94.162 ms 89.995 ms 97.211 ms
7 unknown.hwng.net (209.197.0.38) 122.503 ms 123.367 ms 123.136 ms
8 209.197.17.198 (209.197.17.198) 77.473 ms 83.457 ms 78.888 ms
9 edge-12-teb1.us.as19318.net (64.20.32.78) 79.209 ms
209.197.17.198 (209.197.17.198) 85.553 ms 91.150 ms
10 edge-12-teb1.us.as19318.net (64.20.32.78) 83.287 ms 85.559 ms 82.648 ms
11 openvz17.interserver.net (206.72.207.130) 88.370 ms 85.054 ms 83.717 ms
12 206.72.207.140 (206.72.207.140) 83.289 ms !Z 91.992 ms !Z 76.097 ms !Z
Experiencing heavy lag in-game.
Tracing route to armageddon.org over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 192.168.1.1
2 36 ms 31 ms 25 ms mta-76-176-48-1.san.rr.com [76.176.48.1]
3 8 ms 8 ms 10 ms 76.166.18.165
4 37 ms 15 ms 15 ms tge0-8-0-3.sndhcaax-ccr02.socal.rr.com [72.129.1
.48]
5 21 ms 23 ms 22 ms agg22.tustca1-rtr1.socal.rr.com [72.129.1.2]
6 16 ms 13 ms 15 ms 107.14.19.30
7 85 ms 81 ms 87 ms ae-5-0.cr0.dca20.tbone.rr.com [66.109.6.3]
8 79 ms 78 ms 78 ms ae-1-0.pr0.dca10.tbone.rr.com [66.109.6.165]
9 79 ms 79 ms 78 ms 3-3.r1.dc.hwng.net [69.16.190.113]
10 102 ms 111 ms 103 ms e1-4.r1.ny.hwng.net [209.197.0.34]
11 102 ms 101 ms 118 ms 209.197.17.198
12 100 ms 102 ms 118 ms edge-12-teb1.us.as19318.net [64.20.32.78]
13 104 ms 101 ms 101 ms openvz17.interserver.net [206.72.207.130]
14 101 ms 102 ms 103 ms 206.72.207.140
Trace complete.
C:\>
Tracing route to 206.72.207.140 over a maximum of 30 hops
1 1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 9 ms 9 ms 8 ms klsmt001hb6-GE-0-0-0-U144.int.bresnan.net [69.144.26.145]
4 12 ms 11 ms 12 ms host-72-175-111-98.bln-mt.client.bresnan.net [72.175.111.98]
5 14 ms 11 ms 12 ms mslmt001cr5-GE-3-0-0-U0.int.bresnan.net [72.175.110.5]
6 28 ms 26 ms 25 ms klsmt002hb6-SO-0-3-1-U0.int.bresnan.net [69.144.26.2]
7 27 ms 25 ms 25 ms blnmtdc1dr5-GE-4-0-3-U0.int.bresnan.net [72.175.110.68]
8 26 ms 28 ms 28 ms sesix.r1.se.hwng.net [206.81.80.194]
9 79 ms 80 ms 84 ms unknown.hwng.net [209.197.0.249]
10 110 ms 116 ms 112 ms unknown.hwng.net [209.197.0.38]
11 112 ms 119 ms 124 ms 2-3.r1.ny.hwng.net [69.16.191.93]
12 114 ms 128 ms 115 ms 209.197.17.198
13 113 ms 112 ms 114 ms edge-12-teb1.us.as19318.net [64.20.32.78]
14 114 ms 114 ms 114 ms openvz17.interserver.net [206.72.207.130]
15 113 ms 112 ms 114 ms 206.72.207.140
Trace complete.
Lagging just trying to pick selections on the log in screen really bad. Best not to log in at all.
How long does it take to fix this kind of thing? I'm not hurrying, I'm just curious...I don't know a whole lot about how the server works and stuffz.
My guess would be a reboot of the server would resolve the issue maybe. But maybe not, it really depends on whats causing the issue. Looks like Local Host though from my estimations. I'd laugh if a virus scan is running now though.
It really really depends on what's wrong. If it's the machine, then it needs someone to reboot it. That means someone at the building where the host server is, needs to be made aware that it's a problem, and needs to be available to do something about it.
If it's not the machine, then it could be the building where the server is hosted (I remember the staff saying it's a virtual machine now - but even so, a virtual machine has to have some link to a real machine, somewhere.) Or it could be a router at a central office in the same town where the virtual server is hosted. Or it could be a satellite dish on the fritz. Or aliens.
In summary, and to reiterate, it depends on what's wrong. Anywhere from "within an hour" to "Arm is broken, thanks for playing, look forward to Halo 4 coming in November." Likely it'll be somewhere between the two.
Lets start killing some aliens! Those bastards are finally trying to get at us.....working from our deepest fears.
1) EST 10:17
2) high sun on cingel the 4th day of the descending sun year 1 of the 22nd age
3) 9, it hasn't booted me yet but it was nearly impossible to connect and I'm experiancing up to a full 30 seconds of lag per command. [not by the server].
Geez, this game is broken.
Here I was about to log in.. :-[
I'm going to try rebooting, please stop trying to log in until I post. If I can't get it to clear nicely, I may have to bring it down hard.
Quote from: Morgenes on June 14, 2012, 10:54:13 PM
I'm going to try rebooting, please stop trying to log in until I post. If I can't get it to clear nicely, I may have to bring it down hard.
I got on when it had quickened up for a bit, and now I can't get out again. Sorry Morgenes. :(
Note that we are back up, but even after completely rebooting our entire server, it doesn't seem to have done anything. I'm opening a trouble ticket with our host to see if they can see/do anything about it.
I apologize, but you may want to find something else to do if you can't handle the lag.
actually, it seems to be working fine atm.
Minor blips but it's fairly quick.
Lag.
Thu Jun 14 23:33:30 MDT 2012
traceroute to ginka.armageddon.org (206.72.207.140), 64 hops max, 4050 byte packets
1 192.168.1.1 (192.168.1.1) 2.442 ms 2.498 ms 3.078 ms
2 76.120.80.1 (76.120.80.1) 50.122 ms 62.185 ms 180.416 ms
3 te-7-4-ur03.arvada.co.denver.comcast.net (68.86.129.225) 15.444 ms 13.337 ms 19.263 ms
4 te-0-6-0-6-ar02.denver.co.denver.comcast.net (68.86.179.57) 20.608 ms 43.957 ms 19.151 ms
5 pos-0-1-0-0-ar02.aurora.co.denver.comcast.net (68.86.128.242) 21.679 ms 22.701 ms 39.260 ms
6 pos-3-6-0-0-cr01.denver.co.ibone.comcast.net (68.86.91.1) 22.567 ms 22.386 ms 33.099 ms
7 pos-2-7-0-0-cr01.dallas.tx.ibone.comcast.net (68.86.85.54) 35.761 ms 49.735 ms 37.819 ms
8 pos-0-4-0-0-pe01.1950stemmons.tx.ibone.comcast.net (68.86.87.218) 34.720 ms 54.234 ms 35.889 ms
9 xe-5-1-0.er1.dfw2.us.above.net (64.125.13.185) 51.417 ms 55.835 ms 31.911 ms
10 xe-3-1-0.cr1.dfw2.us.above.net (64.125.30.82) 31.540 ms 35.751 ms 34.299 ms
11 xe-2-1-0.cr1.iah1.us.above.net (64.125.30.57) 41.602 ms 39.131 ms 65.552 ms
12 xe-1-0-0.cr2.iah1.us.above.net (64.125.30.70) 58.950 ms 60.535 ms 38.275 ms
13 * xe-3-1-0.cr2.dca2.us.above.net (64.125.30.54) 88.632 ms 99.533 ms
14 xe-3-2-0.cr2.lga5.us.above.net (64.125.26.110) 70.831 ms 86.823 ms 92.413 ms
15 xe-1-0-1.er2.lga5.us.above.net (64.125.26.166) 74.261 ms 70.761 ms 73.413 ms
16 64.124.44.213.interserver.com (64.124.44.213) 87.983 ms 68.689 ms 69.786 ms
17 edge-12-teb1.us.as19318.net (64.20.32.78) 66.960 ms 105.756 ms 90.896 ms
18 openvz17.interserver.net (206.72.207.130) 68.333 ms 71.451 ms 70.086 ms
19 206.72.207.140 (206.72.207.140) 74.633 ms !Z 70.633 ms !Z 69.548 ms !Z
*shaking a fist* dang lag!
Oh, it's back with a vengeance!
It's those focking aliens again! Git 'um, git 'um!
it is 1:38 AM EST right now, and it is currently taking me minutes to send an emote. I have just tried reconnecting and am now sitting here staring at the screen as it struggles to connect to host.
Anyone else? Or is this me?
Everyone else, Karleith.
Yup, I'm just trying to get in so I can quit out and not get eaten for my bootz. I just want to go to sleep. >:(
Kind of wish we'd get a server reboot so the people who need to quit can do so without needing to fear getting pwned while linkdead.
Not to be ignorant, but uh... I don't see anyone with the sole exception of A Large Bag dropping packets enroute to the server, and she dropped her packets on the second hip-hop (the hippie the hippie (http://www.youtube.com/watch?v=tUqvPJ3cbUQ&feature=related)). There's no one even showing any major upticks in ping between hops that would imply a connectivity issue.
Correct me if I'm wrong, but the way I'm translating that information is that there's no issue with the routes we're hitting the server at (IE, the host).
Are we sure there aren't like.... 30,000 carru in one room somewhere?
Quote from: Akaramu on June 15, 2012, 01:54:47 AM
Kind of wish we'd get a server reboot so the people who need to quit can do so without needing to fear getting pwned while linkdead.
Quote from: Morgenes on June 14, 2012, 11:30:20 PM
Note that we are back up, but even after completely rebooting our entire server, it doesn't seem to have done anything. I'm opening a trouble ticket with our host to see if they can see/do anything about it.
I apologize, but you may want to find something else to do if you can't handle the lag.
Quote from: Gunnerblaster on June 15, 2012, 02:06:23 AM
Quote from: Akaramu on June 15, 2012, 01:54:47 AM
Kind of wish we'd get a server reboot so the people who need to quit can do so without needing to fear getting pwned while linkdead.
Quote from: Morgenes on June 14, 2012, 11:30:20 PM
Note that we are back up, but even after completely rebooting our entire server, it doesn't seem to have done anything. I'm opening a trouble ticket with our host to see if they can see/do anything about it.
I apologize, but you may want to find something else to do if you can't handle the lag.
I don't care if the lag persists after the reboot, I just want to be able to leave the house without my character dying of hunger and thirst in the meantime. :'(
Just to be logged out of the game yanno?
Well, if I remember correctly - Staff set it up to where if a PC is idle/disconnected/etc. for over a certain period of time - They'll stop getting hungry/thirsty.
When was that? Must of been in the last two months or so.
Not sure that works with me trying to reconnect every minute. :-\
Take a deep breath, relax, go read a book and do something else while the problem's figured out. Your PC will be fine, and we'll figure out what's up.
Quote from: Namino on June 15, 2012, 02:04:33 AM
Are we sure there aren't like.... 30,000 carru in one room somewhere?
There's a huge Gith Orgy going on off the shield wall. Sorry you weren't invited but you're welcome to show up.
Nevermind. I feel a little stupid now.
There's a myriad of stuff that could be causing the issue. Anything from a runaway script, memory leaks, or some rogue process. That would be server side and something the staff could address directly once they understood the issue causing it. Then we have stuff that the staff can't fix like an issue with the hardware which is hosting the virtual server, latency between users and server via hops, and the virtual server provider/source having their own difficulties.
It kind of feels like it might be a memory leak issue or something, but with a game as old as Armageddon it's pretty unlikely unless it's a new issue.
Is it still going on? :(
Quote from: Eurynomos on June 15, 2012, 02:30:10 AM
Take a deep breath, relax, go read a book and do something else while the problem's figured out. Your PC will be fine, and we'll figure out what's up.
That's like telling junkies to go take a paracetemol. :p
Lag's been gone for a little bit now.
There are 2 players currently in the world, other than yourself.
I hope you two are enjoying it!
Lies. It's still lagging.
Naw, it was actually okay for a while. I can vouch for that.
Quote from: Gunnerblaster on June 15, 2012, 02:23:41 AM
Well, if I remember correctly - Staff set it up to where if a PC is idle/disconnected/etc. for over a certain period of time - They'll stop getting hungry/thirsty.
People over 60 minutes idle no longer get hunger/thirsty. Yep.
Now even the GDB is lagging. Nyr....why haven't you fixed it with your super powers? :(
Quote from: Nyr on June 15, 2012, 08:30:51 AM
Quote from: Gunnerblaster on June 15, 2012, 02:23:41 AM
Well, if I remember correctly - Staff set it up to where if a PC is idle/disconnected/etc. for over a certain period of time - They'll stop getting hungry/thirsty.
People over 60 minutes idle no longer get hunger/thirsty. Yep.
Since when?
November 27, 2008. It went live in the next reboot.
Quote from: http://www.armageddon.org/general/updates/view.php?week=48&year=2008Full people can eat tablets after next reboot -- Nessalin.
People over 1hr idle will no longer lose hunger/thirst (treated as linkdead) -- Nessalin.
Has the lag been fixed up and all that?
No. Read the millions of posts complaining about it....
It's the change of the Kings Age. It's like the Millenium Bug all over again. :(
It's been fine for me this afternoon.
It's still definitely really really shit.
Fuck the lag!!!!
Hmm, weird. Just came up all of a sudden.
Can anyone confirm that it's laggy out of in the wilderness?
It's laggy everywhere.
Guess I'm just lucky then.
TraceRoute to 206.72.207.140 [armageddon.org]
Hop (ms) (ms) (ms) IP Address Host name
1 1 1 0 206.123.64.42 -
2 0 0 0 64.124.196.225 xe-4-2-0.er2.dfw2.us.above.net
3 0 0 0 64.125.27.81 xe-0-1-0.cr2.dfw2.us.above.net
4 5 5 5 64.125.26.134 xe-1-2-0.cr2.iah1.us.above.net
5 32 32 32 64.125.28.49 xe-2-1-0.cr2.dca2.us.above.net
6 45 90 45 64.125.26.110 xe-3-2-0.cr2.lga5.us.above.net
7 36 36 36 64.125.27.65 xe-0-0-1.er2.lga5.us.above.net
8 47 47 47 64.124.44.213 64.124.44.213.interserver.com
9 93 91 92 64.20.32.78 edge-12-teb1.us.as19318.net
10 47 47 47 206.72.207.130 openvz17.interserver.net
11 44 46 44 206.72.207.140 -
Trace complete
Whew, at least it waited until my PC wasn't locked in mortal combat. Thanks, lag!
I really doubt staff needs more tracerts.
FFfffffuuuuuuuuuuu...
Another blip. Completely stuck.
Quote from: Iiyola on June 16, 2012, 12:05:04 AM
FFfffffuuuuuuuuuuu...
Another blip. Completely stuck.
Same, lagged out - now I can connect but after I get "Connected to host armageddon.org" I get no login screen or output to my client AT AL ??? >:( :o ??? :-[ :-\ :'( :'(
Running to a safequit room in bullettime right now. :P Still in, though that's more evidence of sheer bloody mindedness on my part.
Quote from: Namino on June 16, 2012, 12:12:30 AM
Running to a safequit room in bullettime right now. :P Still in, though that's more evidence of sheer bloody mindedness on my part.
Lucky you, can't even get in now -- if any staff sees this... PLEASE log out
[REMOVED]-- 15 minutes of being unable to login at all ARGGHH what's going on....
Wonder if a reboot would help as a quick fix for the time being. I've had lag / connection trouble in the past (as many people have and have stated in this thread) but I've never seen it this bad where I can't login to the MUD at ALL!
:'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'(
EDIT: Yeah sorry... removed...
You probably don't want to tell people your characters name. Might want to edit that out.
QuoteCome back soon!
(http://2.bp.blogspot.com/_wuSqJG5bIKE/TAPCkf6H--I/AAAAAAAAAfA/w-DTRthYKac/s1600/baseball+umpire.jpg)
(http://images.clipartof.com/small/63593-Baseball-Umpire-Signaling-An-Out-Poster-Art-Print.jpg)
Not safe, I'm out! Wish I could get in, my luck I'm probably already dead... ???
Choose thy fate: x
((Disconnected.))
YAAAAAYYYYY
Quote from: jstorrie on June 16, 2012, 12:28:53 AM
Choose thy fate: x
((Disconnected.))
YAAAAAYYYYY
Congrats, now pray to the MUD gods for me so that I can actually log in and do the same :'(
Come on, the lag isn't even all that bad.
For bards.
I'm guessing someone has put in a ticket for this issue. Any sort of response from the hosting company?
Quote from: The Lonely Hunter on June 16, 2012, 01:09:31 AM
I'm guessing someone has put in a ticket for this issue. Any sort of response from the hosting company?
How do yo know? Is this the standard procedure for staff when stuff like this happens? Do they not have RPD / Remote access to the server with the website & MUD on it to reboot it? Or possibly a remote reboot tool through a UPS? Sorry I'm new here and just curious... ??? Server is in desperate need of a reboot...
Quote from: Morgenes on June 14, 2012, 11:30:20 PM
Note that we are back up, but even after completely rebooting our entire server, it doesn't seem to have done anything. I'm opening a trouble ticket with our host to see if they can see/do anything about it.
I apologize, but you may want to find something else to do if you can't handle the lag.
Didn't we already have the same lag issue several months ago and then it went away suddenly? ???
Seems okay now.
Quote from: Akaramu on June 16, 2012, 01:39:47 AM
Didn't we already have the same lag issue several months ago and then it went away suddenly? ???
Yep.
We had similar issues 6 months ago and they moved us to a different, newer, faster server with more RAM.
A few weeks ago the issues came back after we had a strange outage where the server was stuck then just came back up with less RAM than we had, but still more than we are paying for.
They have responded to the ticket by increasing our I/O priority and increasing our 'lockpages' due to an error they were seeing in the logs. I still need to get back to them and tell them it hasn't helped. (Sorry, it's Father's Day weekend, and I'm not able to concentrate on it)
Today seems a lot better.
Quote from: KankWhisperer on June 16, 2012, 09:20:20 PM
Today seems a lot better.
It gets worse with more people online, it seems. I'm noticing small spikes at the moment. nothing like yesterday.
There's the lag monster again!
Uh oh
The malevolent entity know as lag rears its ugly head.
*Ginka raises its a shield shaped from the skins of slain badasses
The fight is on!
Lag casts firaga. It's over.
Did several traces, they all look the same. Only bumps are my router and when trying to resolve the game's IP.
Tracing route to ginka.armageddon.org [206.72.207.140]
over a maximum of 30 hops:
1 3 ms 1 ms 2 ms 10.0.0.1
2 * * * Request timed out.
3 12 ms 25 ms 17 ms te-5-1-ur01.hinsdale.nh.boston.comcast.net [68.8
7.154.101]
4 24 ms 18 ms 16 ms be-57-ar01.woburn.ma.boston.comcast.net [68.87.1
46.198]
5 13 ms 14 ms 18 ms pos-3-0-0-0-ar01.needham.ma.boston.comcast.net [
68.87.146.14]
6 43 ms 43 ms 42 ms pos-2-2-0-0-cr01.newyork.ny.ibone.comcast.net [6
8.86.93.185]
7 40 ms 45 ms 42 ms pos-1-6-0-0-pe01.111eighthave.ny.ibone.comcast.n
et [68.86.87.110]
8 39 ms 40 ms 42 ms xe-2-0-0.er2.lga5.us.above.net [64.125.12.209]
9 41 ms 41 ms 39 ms 64.124.44.213.interserver.com [64.124.44.213]
10 44 ms 42 ms 44 ms edge-12-teb1.us.as19318.net [64.20.32.78]
11 45 ms 40 ms 40 ms openvz17.interserver.net [206.72.207.130]
12 39 ms 39 ms 44 ms 206.72.207.140
Trace complete.
Don't have any trouble connecting the the server, it just hangs:
Connected to host armageddon.org
Connected to host armageddon.org
Tuluk, stop having fun, you're ruining this for everyone. ;)
It is taking me whole minutes to move from one room to the next.
Right about now I'm struggling just to log out. Good thing I'm not standing in front of a large hungry insect.
Woooooooooooooooooooooow! Talk about ruining all the fun.
Quote from: janeshephard on June 16, 2012, 09:56:21 PM
Right about now I'm struggling just to log out. Good thing I'm not standing in front of a large hungry insect.
:(
getting HEAVY lag at this point, a minute or two before "choose thy fate" comes up, gonna disconnect so i'm not putting commands into it, and hopefully this lag will clear up, im gonna try to let people know if I see the lag has mostly cleared up, do post on here about it if you come on too and find that's it's substantially less lagged
Quote from: KankWhisperer on June 16, 2012, 09:20:20 PM
Today seems a lot better.
Now I can't log in. Jinxed it.
Did I say Firaga? Because I meant Blizzaga. Because that shit is...
(http://upload.wikimedia.org/wikipedia/en/thumb/4/46/Horatio_Caine.jpg/250px-Horatio_Caine.jpg)
...frozen.
This is awesome. My screen saver comes on in between the commands I input.
I just thought of something. How about the game force sends "stop" to everyone when it starts detecting this shit coming? There were signs before the inevitable total-hang, lots of slowing. I could queue up a command, it just waited to go. I could do... 3 commands. Then, three were sent. Groups of actions were taking place. In between groupings of 4-5 simeultaneously presented actions, there were 20-30 second gaps.
this would give an imm the ability, if watching this unfold, to force send a universal "stop" command to all PCs.
Then, the imm could force-send "save" to everyone, and then "quit" to everyone as well. Then, it could reboot, there being no more commands effectively queued for all pcs. Reboot.
Just an idea.
The burning sun rises high into the sky, searing the earth.
In game time is still going.
Yup, sure is pretty.
\/\/\/\/
She's enjoying the scenery.
Do not post about what your current character is doing in game or any past characters until a year has passed.
1 1 ms 1 ms 1 ms bob.iad [10.1.1.1]
2 62 ms 16 ms 16 ms nexthop.wa.iinet.net.au [203.215.5.244]
3 17 ms 17 ms 18 ms te7-1.per-qv1-bdr1.iinet.net.au [203.215.4.18]
4 71 ms 71 ms 70 ms xe-3-3-0-0.syd-ult-core1.iinet.net.au [203.215.2
0.6]
5 68 ms 68 ms 67 ms te3-1-0.bdr1.syd7.internode.on.net [150.101.197.
185]
6 253 ms 269 ms 253 ms po3-0-0.bdr1.sjc2.internode.on.net [203.16.213.1
58]
7 226 ms 226 ms 225 ms eqx-sv.4-3.r2.sj.hwng.net [206.223.116.234]
8 251 ms 250 ms 250 ms 1-3.r2.ch.hwng.net [209.197.1.210]
9 296 ms 331 ms 293 ms unknown.hwng.net [209.197.0.249]
10 331 ms 324 ms 325 ms unknown.hwng.net [209.197.0.38]
11 314 ms 317 ms 322 ms 2-3.r1.ny.hwng.net [69.16.191.93]
12 321 ms 317 ms 318 ms 209.197.17.198
13 319 ms 318 ms 318 ms edge-12-teb1.us.as19318.net [64.20.32.78]
14 327 ms 376 ms 393 ms openvz17.interserver.net [206.72.207.130]
15 322 ms 319 ms 318 ms 206.72.207.140
Well, looks like I will be getting in bed at a decent hour.
Noooo! I was waiting all day to come home and play... I was so excited... :'(
Heart = Broken
Doing my part.
Tracing route to armageddon.org [206.72.207.140]
over a maximum of 30 hops:
1 1240 ms 1587 ms 1 ms buffalo.setup [192.168.11.1]
2 1273 ms 16 ms 16 ms 220.220.253.6
3 3455 ms 31 ms 22 ms 220.220.253.1
4 1851 ms 2064 ms 942 ms 118.21.174.145
5 98 ms 718 ms 913 ms i118-21-178-3.s99.a049.ap.plala.or.jp [118.21.17
8.3]
6 549 ms 779 ms 352 ms 218.43.251.129
7 1092 ms 1004 ms 1484 ms 118.23.146.49
8 1415 ms 1056 ms 49 ms 60.37.27.155
9 167 ms 15 ms 7 ms ae-11.r21.tokyjp01.jp.bb.gin.ntt.net [129.250.12
.201]
10 618 ms 123 ms 132 ms as-2.r21.snjsca04.us.bb.gin.ntt.net [129.250.4.4
4]
11 206 ms 126 ms 306 ms equinixexchange.ir1.sanjose-ca.us.xo.net [206.22
3.116.85]
12 330 ms 130 ms 327 ms 207.88.14.225.ptr.us.xo.net [207.88.14.225]
13 191 ms 460 ms 225 ms te-2-0-0.rar3.washington-dc.us.xo.net [207.88.12
.70]
14 1074 ms 2256 ms 2423 ms ae0d0.mcr1.newark-nj.us.xo.net [216.156.0.22]
15 1392 ms 3030 ms 1925 ms ae1d0.mcr1.nyc-ny.us.xo.net [216.156.1.9]
16 1368 ms 185 ms * 207.239.51.86
17 1626 ms 2131 ms 889 ms edge-12-teb1.us.as19318.net [64.20.32.78]
18 1371 ms 187 ms 204 ms openvz17.interserver.net [206.72.207.130]
19 676 ms 199 ms 1708 ms 206.72.207.140
Trace complete.
Someone IM me when it's back to decent.
/me grumbles drunkenly!
Maaaan. This shit's still down? I've been patiently biding my time until the weekend/my day off to ARM it up and I can't even connect.
This blows.
I wonder if it would be possible to give everyone 'quit anywhere' privileges until the nightly lag passes.
I don't think the game has ever been down this long since the weekly maintenance days...
Quote from: adrift on June 16, 2012, 11:31:52 PM
I don't think the game has ever been down this long since the weekly maintenance days...
Yeah, this is like the first time.
I makes me sad that my time zone / schedule permits me to play almost exclusively during this time of night..
How do I get these stats everyone is posting so I can help too?
For Linux, you type in traceroute 206.72.207.140 in term
You may need to do apt-get traceroute first.
Actually, I think it's the same for all OS's.
QuoteQuote from: adrift on Today at 07:31:52 PM
I don't think the game has ever been down this long since the weekly maintenance days...
Yeah, this is like the first time.
Untrue, we have had such since then...hell, I'm pretty sure, more then once it was a bad router.
But, since we are not hosted on ginka anymore...who knows what it is.
Quote from: X-D on June 16, 2012, 11:37:56 PM
QuoteQuote from: adrift on Today at 07:31:52 PM
I don't think the game has ever been down this long since the weekly maintenance days...
Yeah, this is like the first time.
Untrue, we have had such since then...hell, I'm pretty sure, more then once it was a bad router.
But, since we are not hosted on ginka anymore...who knows what it is.
Oh duh, was this before they moved the sever (that time).
Is it safe to assume that we'll be logged out eventually? I really can't wait any longer and I'm fairly certain my PC would die if I just continued to be where I happen to be.
Yeah, my main play time is during our downtime now. Sucks. Hopefully after the weekend the issue will be resolved. It seems to be machine lag and always at the same time which would lead me to believe they are running backups, scans, or using the machine for more than just hosting Arm.
"HostingCompany offers 30 day money back guarantee on shared hosting, 99.5% uptime guarantee, 100% power guarantee, fast and easy setups, easy to use control panel choices, and much more. Come see why thousands have used HostingCompany to make their website happy!"
(Real name withheld so people don't take it upon themselves to contact the host)
99.5%?
Quote from: Barsook on June 16, 2012, 11:37:38 PM
For Linux, you type in traceroute 206.72.207.140 in term
You may need to do apt-get traceroute first.
Actually, I think it's the same for all OS's.
..I use the flash applet. Is there anything I can use in that?
If you're using Windows XP, 2000 or Me click start, run, type in cmd then type tracert ginka.armageddon.org
If you're using Windows 7, easiest way is to search cmd "" "" ""
Sat Jun 16 22:12:45 MDT 2012
traceroute to ginka.armageddon.org (206.72.207.140), 64 hops max, 4050 byte packets
1 192.168.1.1 (192.168.1.1) 4.478 ms 2.055 ms 2.037 ms
2 76.120.80.1 (76.120.80.1) 48.160 ms 77.977 ms 156.180 ms
3 te-7-4-ur03.arvada.co.denver.comcast.net (68.86.129.225) 15.814 ms 27.234 ms 36.869 ms
4 te-0-6-0-6-ar02.denver.co.denver.comcast.net (68.86.179.57) 24.627 ms 18.552 ms 41.481 ms
5 pos-0-1-0-0-ar02.aurora.co.denver.comcast.net (68.86.128.242) 22.149 ms 58.862 ms 29.968 ms
6 pos-3-6-0-0-cr01.denver.co.ibone.comcast.net (68.86.91.1) 20.031 ms 43.872 ms 27.772 ms
7 pos-2-7-0-0-cr01.dallas.tx.ibone.comcast.net (68.86.85.54) 36.261 ms 54.984 ms 39.526 ms
8 pos-0-4-0-0-pe01.1950stemmons.tx.ibone.comcast.net (68.86.87.218) 43.204 ms 37.529 ms 58.746 ms
9 xe-5-1-0.er1.dfw2.us.above.net (64.125.13.185) 81.835 ms 32.821 ms 51.518 ms
10 xe-3-2-0.cr1.dfw2.us.above.net (64.125.30.86) 37.233 ms 53.105 ms 33.080 ms
11 xe-1-0-0.cr2.dfw2.us.above.net (64.125.30.78) 38.260 ms 42.745 ms 54.553 ms
12 xe-4-2-0.cr2.iah1.us.above.net (64.125.31.122) 58.635 ms 39.319 ms 62.957 ms
13 xe-5-0-0.cr2.dca2.us.above.net (64.125.31.250) 67.558 ms 67.572 ms *
14 xe-3-2-0.cr2.lga5.us.above.net (64.125.26.110) 88.141 ms 69.889 ms 66.916 ms
15 xe-0-0-1.er2.lga5.us.above.net (64.125.27.65) 66.645 ms 67.008 ms 66.667 ms
16 64.124.44.213.interserver.com (64.124.44.213) 67.503 ms 66.478 ms 94.987 ms
17 edge-12-teb1.us.as19318.net (64.20.32.78) 97.830 ms 89.496 ms 67.252 ms
18 openvz17.interserver.net (206.72.207.130) 91.836 ms 74.706 ms 70.479 ms
19 206.72.207.140 (206.72.207.140) 75.273 ms !Z 69.168 ms !Z 93.683 ms !Z
...and on a mac?
Quote from: greasygemo on June 17, 2012, 12:14:13 AM
...and on a mac?
On a mac, open up Applications -> Utilities -> Terminal
At the prompt, type 'traceroute ginka.armageddon.org 4050'
I think that at this point it has been pretty well established that it isn't a hop to the hosting company but the box we are running on.
traceroute to ginka.armageddon.org (206.72.207.140), 64 hops max, 4050 byte packets
1 192.168.2.1 (192.168.2.1) 3.579 ms 2.775 ms 2.900 ms
2 142.166.182.7 (142.166.182.7) 48.119 ms 47.467 ms 91.296 ms
3 irb-84.dr02.fctn.nb.aliant.net (142.166.211.17) 90.903 ms 47.400 ms 91.888 ms
4 xe-0-0-0.cr02.stjh.nb.aliant.net (142.166.185.145) 99.737 ms 48.507 ms 91.755 ms
5 xe-1-0-0.bx01.mtrl.pq.aliant.net (207.231.227.58) 103.579 ms 61.537 ms 92.802 ms
6 xe-7-2-0.bx01.toro.on.aliant.net (207.231.227.66) 101.310 ms 67.330 ms
xe-7-2-1.bx01.toro.on.aliant.net (207.231.227.70) 92.217 ms
7 xe-1-1-0.bx01.chcg.il.aliant.net (207.231.227.101) 85.101 ms
xe-0-1-0.bx01.chcg.il.aliant.net (207.231.227.97) 91.979 ms
xe-1-1-0.bx01.chcg.il.aliant.net (207.231.227.101) 85.268 ms
8 eqx-ch.3-2.r1.ch.hwng.net (206.223.119.96) 97.227 ms 87.831 ms 97.439 ms
9 e1-4.r1.ny.hwng.net (209.197.0.34) 94.067 ms 88.452 ms 97.432 ms
10 209.197.17.198 (209.197.17.198) 90.066 ms 86.908 ms 91.652 ms
11 edge-12-teb1.us.as19318.net (64.20.32.78) 92.319 ms 88.101 ms 101.978 ms
12 openvz17.interserver.net (206.72.207.130) 155.233 ms 150.888 ms 158.425 ms
13 206.72.207.140 (206.72.207.140) 151.670 ms !Z 171.689 ms !Z 152.212 ms !Z
Even so... here is my two-cents
Why are people posting traces for
Arm doesn't own their own box so all infrastructure involved is not fixable by anybody reading this forum
Like Morgenes said, it's Father's Day weekend. Relax, get a beer, invite a friend over. Watch Rome on HBO Go. Read a book. We'll fix the problem. Maybe. If you're good.
Quote from: Case on June 17, 2012, 12:26:53 AM
Why are people posting traces for
Arm doesn't own their own box so all infrastructure involved is not fixable by anybody reading this forum
In the past, when lag issues surfaced, it has been requested by the staff. While it may not be fixable by anyone reading this forum, there are staffers on this forum that can take the information to people that
can fix it...and the more information you present those people with, the better.
Presenting these people with full traces from 10+ different origins certainly can't hurt, and may be infinitely more useful than "Shit's runnin' slow."
Quote from: Case on June 17, 2012, 12:26:53 AM
Why are people posting traces for
Arm doesn't own their own box so all infrastructure involved is not fixable by anybody reading this forum
Quote from: Jeshin on November 17, 2011, 09:00:31 AM
After Wedi's post and Nyr's reply this is the official. Unbearable lag thread. Whenever encountered with what you consider to be game affecting lag or an unintentional DC please include the following
1) PST/EST/GMT of the event or just say at the time of posting
2) IG time - early morning etc etc
3) On a scale of 1-10 how bad the lag is. 1 being one or two seconds sporadically, 5 being several seconds over a long peiod, and 10 being a full disconnect [not by the server].
We can fight lag, with data!
Quote from: drunkendwarf on June 17, 2012, 12:35:22 AM
Quote from: Case on June 17, 2012, 12:26:53 AM
Why are people posting traces for
Arm doesn't own their own box so all infrastructure involved is not fixable by anybody reading this forum
In the past, when lag issues surfaced, it has been requested by the staff. While it may not be fixable by anyone reading this forum, there are staffers on this forum that can take the information to people that can fix it...and the more information you present those people with, the better.
Presenting these people with full traces from 10+ different origins certainly can't hurt, and may be infinitely more useful than "Shit's runnin' slow."
Hosting company should be sorting that out because it's their job. Back when Ginka was a PC in somebody's house that made more sense.
Seems to be running smoother now.
12:48 EST
Quote from: Case on June 17, 2012, 12:47:11 AM
Quote from: drunkendwarf on June 17, 2012, 12:35:22 AM
Quote from: Case on June 17, 2012, 12:26:53 AM
Why are people posting traces for
Arm doesn't own their own box so all infrastructure involved is not fixable by anybody reading this forum
In the past, when lag issues surfaced, it has been requested by the staff. While it may not be fixable by anyone reading this forum, there are staffers on this forum that can take the information to people that can fix it...and the more information you present those people with, the better.
Presenting these people with full traces from 10+ different origins certainly can't hurt, and may be infinitely more useful than "Shit's runnin' slow."
Hosting company should be sorting that out because it's their job. Back when Ginka was a PC in somebody's house that made more sense.
?
Why do you give a shit? Staff asked us to. We do it. I realize this time it's looking like an issue on the box itself, but in the past that has not been the case.
Quote from: drunkendwarf on June 17, 2012, 12:50:11 AM
Quote from: Case on June 17, 2012, 12:47:11 AM
Quote from: drunkendwarf on June 17, 2012, 12:35:22 AM
Quote from: Case on June 17, 2012, 12:26:53 AM
Why are people posting traces for
Arm doesn't own their own box so all infrastructure involved is not fixable by anybody reading this forum
In the past, when lag issues surfaced, it has been requested by the staff. While it may not be fixable by anyone reading this forum, there are staffers on this forum that can take the information to people that can fix it...and the more information you present those people with, the better.
Presenting these people with full traces from 10+ different origins certainly can't hurt, and may be infinitely more useful than "Shit's runnin' slow."
Hosting company should be sorting that out because it's their job. Back when Ginka was a PC in somebody's house that made more sense.
?
Why do you give a shit? Staff asked us to. We do it. I realize this time it's looking like an issue on the box itself, but in the past that has not been the case.
Have fun wasting time I guess? Not sure why I'm a bad person for questioning something.
heh, yeah, I could have told ya'll your tracerts were meaningless.
ping armageddon.org
in a cmd window and see tons of beautiful pings.
and the fact that the website loaded meant this was not a network problem.
I said as much a while ago. All tracerts are going to tell is that the problem is not on our end. Which is pretty obvious by now.
^ +1 on ping, it's great, a for tracert being meaningless, not for me to decide, lag is gone now for me anyways
hello dawn, hello heavy lag
i recall my first heavy lag of the night came at around dawn too, maybe increased NPC walking around and shop opening activity, couple with increased player activity?
playtime interspersed with heavy lag .. hard to pin down, but when pinged in a normal state above 50ms to return, 200 ms during spikes. not going to be able to play long enough to wait for it to happen again and tracert, hope this helps
QuoteIs it safe to assume that we'll be logged out eventually? I really can't wait any longer and I'm fairly certain my PC would die if I just continued to be where I happen to be.
Actually staff does not log people out...unless asked, usually through wish.
Best you can hope for is that people are mature enough to not take advantage of LD PCs...Or, if you are in an unsafe area, maybe somebody will move you to a safe area...I've already done so with a couple PCs I found in the wilderness...I'm just an old softy that way.
Quote from: X-D on June 17, 2012, 05:34:26 AM
QuoteIs it safe to assume that we'll be logged out eventually? I really can't wait any longer and I'm fairly certain my PC would die if I just continued to be where I happen to be.
Actually staff does not log people out...unless asked, usually through wish.
Best you can hope for is that people are mature enough to not take advantage of LD PCs...Or, if you are in an unsafe area, maybe somebody will move you to a safe area...I've already done so with a couple PCs I found in the wilderness...I'm just an old softy that way.
It's true. Once when I went link dead due to power outage X-D sapped subdued and drug my PC back to safety, and put my weapons in my inventory.
I pay it forward now when I find PC's in similar circumstances.
Quote from: musashi on June 17, 2012, 05:39:56 AM
Quote from: X-D on June 17, 2012, 05:34:26 AM
QuoteIs it safe to assume that we'll be logged out eventually? I really can't wait any longer and I'm fairly certain my PC would die if I just continued to be where I happen to be.
Actually staff does not log people out...unless asked, usually through wish.
Best you can hope for is that people are mature enough to not take advantage of LD PCs...Or, if you are in an unsafe area, maybe somebody will move you to a safe area...I've already done so with a couple PCs I found in the wilderness...I'm just an old softy that way.
It's true. Once when I went link dead due to power outage X-D sapped subdued and drug my PC back to safety, and put my weapons in my inventory.
I pay it forward now when I find PC's in similar circumstances.
Thankfully bad situations were avoided this time around (for me, at least). But it does seem like there should be some sort of protocol in situations like this...game-wide logout with a reboot, just to purge players who couldn't wait 3 hours to find somewhere safe to quit. Granted, I don't think it's usually quite as bad as it was.
Personally, I handle it the same way and will either drag someone to a safe location or just wish up that they're link dead. Good to know I'm not the only one :)
Staff might be just as laggy and just as unable to issue commands with wish ups during global lag like the type we're facing now.
But I highly approve of sapping/subduing/wishing up/being nice to linkdead characters when it's not huge global lag.
Quote from: Karieith on June 17, 2012, 06:28:56 AM
Staff might be just as laggy and just as unable to issue commands with wish ups during global lag like the type we're facing now.
But I highly approve of sapping/subduing/wishing up/being nice to linkdead characters when it's not huge global lag.
Oh yes, of course! I mean more afterwards...when all the lag finally subsides.
IT BEGINS
Can a ping help?
PING 206.72.207.140 (206.72.207.140) 56(84) bytes of data.
64 bytes from 206.72.207.140: icmp_req=1 ttl=53 time=34.0 ms
64 bytes from 206.72.207.140: icmp_req=2 ttl=53 time=36.1 ms
64 bytes from 206.72.207.140: icmp_req=3 ttl=53 time=34.4 ms
64 bytes from 206.72.207.140: icmp_req=4 ttl=53 time=35.0 ms
64 bytes from 206.72.207.140: icmp_req=5 ttl=53 time=34.0 ms
Yup. Connects in half a second, and then I get no mantis head for many minutes.
Quote from: Barsook on June 17, 2012, 11:22:23 AM
Can a ping help?
PING 206.72.207.140 (206.72.207.140) 56(84) bytes of data.
64 bytes from 206.72.207.140: icmp_req=1 ttl=53 time=34.0 ms
64 bytes from 206.72.207.140: icmp_req=2 ttl=53 time=36.1 ms
64 bytes from 206.72.207.140: icmp_req=3 ttl=53 time=34.4 ms
64 bytes from 206.72.207.140: icmp_req=4 ttl=53 time=35.0 ms
64 bytes from 206.72.207.140: icmp_req=5 ttl=53 time=34.0 ms
Ping jis like traceroute lite - ust measures how long it takes to bounce from your machine to the server. In this case, having established it's not a network issue, ping isn't of much use.
Quote from: drunkendwarf on June 17, 2012, 11:23:11 AM
Yup. Connects in half a second, and then I get no mantis head for many minutes.
Same and here's the traceroute:
traceroute to 206.72.207.140 (206.72.207.140), 30 hops max, 60 byte packets
1 unknown (192.168.1.1) 1.694 ms 2.760 ms 3.890 ms
2 10.169.64.1 (10.169.64.1) 12.145 ms 12.732 ms 12.717 ms
3 ae0-1030.cr02.dytnoh55.swo.rr.com (184.59.244.114) 19.525 ms 23.147 ms 23.187 ms
4 ae0.tr00.clevohek.mwrtn.rr.com (65.189.140.144) 30.953 ms ae1.tr00.clevohek.mwrtn.rr.com (65.189.140.130) 31.378 ms 30.856 ms
5 107.14.19.58 (107.14.19.58) 40.769 ms ae-3-0.cr0.dca20.tbone.rr.com (66.109.6.70) 40.820 ms 107.14.19.58 (107.14.19.58) 50.857 ms
6 ae-1-0.pr0.dca10.tbone.rr.com (66.109.6.165) 43.154 ms 31.789 ms 107.14.19.135 (107.14.19.135) 28.597 ms
7 3-3.r1.dc.hwng.net (69.16.190.113) 29.236 ms 30.281 ms 44.192 ms
8 e4-2.r1.ny.hwng.net (209.197.0.42) 46.798 ms e1-4.r1.ny.hwng.net (209.197.0.34) 50.814 ms e4-2.r1.ny.hwng.net (209.197.0.42) 38.827 ms
9 209.197.17.198 (209.197.17.198) 74.745 ms 74.655 ms 75.170 ms
10 edge-12-teb1.us.as19318.net (64.20.32.78) 37.973 ms 55.270 ms 55.249 ms
11 openvz17.interserver.net (206.72.207.130) 41.508 ms 58.379 ms 41.537 ms
12 206.72.207.140 (206.72.207.140) 35.124 ms !X 51.989 ms !X 35.112 ms !X
I admire how many players tough out the lag in order to play.
Quote from: Morgenes on June 16, 2012, 08:46:46 PM
We had similar issues 6 months ago and they moved us to a different, newer, faster server with more RAM.
A few weeks ago the issues came back after we had a strange outage where the server was stuck then just came back up with less RAM than we had, but still more than we are paying for.
They have responded to the ticket by increasing our I/O priority and increasing our 'lockpages' due to an error they were seeing in the logs. I still need to get back to them and tell them it hasn't helped. (Sorry, it's Father's Day weekend, and I'm not able to concentrate on it)
Just reposting this for anyone that has skimmed over it.
P.S. - It's working now.
;D
(Hope I didn't just jinx it)
It comes and goes.
Please behave yourself game, now is not a good time!
Y'know, it got this terrible around this time yesterday too.
It's coming.
Here we go. (http://www.youtube.com/watch?v=3_gst-Ryh3g)
Awww, it missed me :3
It's either having to do with this time frame - as this is about the same time as yesterday - or it's when there's more than 50 people online... or at least that's all I can think of that makes sense...
Yep just came on now... nothing - nothing - nothing - running perfectly - BAM! - Lag.
Eeek... :'(
OMG, this is horrible.
I think it has to do with the time, it's been consistent the last three days. It also appears to happen at a similar time in the AM.
I don't mind it so much. I'm sitting here, drinking beer. I wonder if NPCs lag ...
I was going to post what Creslin said almost verbatim, except my sound effect would have been BLAM.
BLAM! Lag.
Usually with code it's whatever they changed last.
Wasn't it something about npc follow script , hidden script, and gate saves. Don't know how gate saves would do it, some kinda loop in the script to make them stop following maybe? Or the hide thing maybe?
Yep, the lag monster is rearing it's head... -_-
It almost feels like the server starts either running an anti-virus program or starts scheduled backups, thus taking two hours to complete.
Anyways we peaked at 60 people and then got hit with lag, kinda seems fair peak-time gets a taste of what off-peak has been going through.
Anyways, it is now officially a race to log off! :D
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Program Files\VentSrv>tracert 206.72.207.104
Tracing route to 206.72.207.104 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms 192.168.0.1
2 39 ms 39 ms 39 ms ptld-dsl-gw44-236.ptld.qwest.net [207.225.84.236
]
3 40 ms 39 ms 39 ms ptld-agw1.inet.qwest.net [207.225.86.89]
4 43 ms 42 ms 43 ms sea-brdr-02.inet.qwest.net [67.14.41.18]
5 43 ms 43 ms 43 ms 63.146.26.82
6 69 ms 44 ms 44 ms xe-1-0-0.mpr2.sea1.us.above.net [64.125.31.14]
7 98 ms 98 ms 100 ms xe-1-2-0.cr2.ord2.us.above.net [64.125.31.2]
8 122 ms 122 ms 122 ms xe-2-0-0.cr2.lga5.us.above.net [64.125.24.29]
9 160 ms 119 ms 120 ms xe-1-0-1.er2.lga5.us.above.net [64.125.26.166]
10 138 ms 122 ms 122 ms 64.124.44.213.interserver.com [64.124.44.213]
11 121 ms 120 ms 120 ms edge-12-teb1.us.as19318.net [64.20.32.78]
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * *
we got lag right now? im getting it, maybe others arent?
Seems to be getting better.
edit:
knock on wood.
It got better enough for me to get to a place where i can log out. That only took an hour :(
We went from 60 people down to 26 in that time which isn't too bad, though guessing the rest are stuck somewhere. Good luck to you!
Might be coming out on the other side of the tunnel now, not sure...
thanks for the tip dresan, i dont wanna be left holding the bag either
Quote from: Kismetic on June 17, 2012, 10:40:48 PM
I think it has to do with the time, it's been consistent the last three days. It also appears to happen at a similar time in the AM.
I don't mind it so much. I'm sitting here, drinking beer. I wonder if NPCs lag ...
If it's machine lag, NPCs generally are affected by it, because their scripts are suffering from the same underlying problem (lack of processing power).
If it's network lag, probably not.
Being vague, I am just going to say that it does appear the NPCs lag too.
Lag confirmed, 2 am EST, severity level 6, not fully logged out, 30 secs to 4 mins for a command.
Greasy, it's just you I think. I'm in game and seem to be unaffected.
Lag went away after about an hour.
Is this the time it usually hits in the mornings everyone was previously alluding to? Or is this just me?
It came back this morning it seems although not as bad as it was this weekend's Father's day.
and it's back
11:20 EST, Lag level 7 - 5-10 mins for a command
I just had to disconnect in the middle of a fight. The fight took 15 minutes to get through three rounds. Kept sending variations of "Stand" and "Flee," lag so bad none of the commands went through. Just going to send a rez request after my PC dies.
Nice. Looks like Arma is shutdown. Good call, until this gets sorted out :)
Woah, D/C and when trying to R/C Socket Error... and now it's saying Security error??
Quote from: greasygemo on June 18, 2012, 11:32:28 AM
Woah, D/C and when trying to R/C Socket Error... and now it's saying Security error??
The mud is off-line. Sounds like you're using a Java client.
This is better than it being on-line and people dying while linkdead.
EDIT: Looks like it's back up.
It just disconnected and won't reconnect.
So... What's going on with all the reboots?
Quote from: Evoru on June 18, 2012, 12:16:53 PM
It just disconnected and won't reconnect.
You can usually check to see if it's lag or a crash by going to www.armageddon.org (http://www.armageddon.org)
Toward the bottom of the page, it will say something like, "Armageddon is not running" or "Armageddon just booted 10 seconds ago" if it was a crash. If it was last booted 15 days ago, it's lag.
Anyone logged back in and found themselves back where they were?
Okay, I've figured this out.
Pyramid scheming the lag away!
Bear with me. The current theory is that the virtual server does not have enough RAM which could be causing the lag. Now as mentioned we already have more RAM than we're paying for. Clearly we should pay for more, so everyone send to Briarfox for character art and as per her arrangement you should donate any money you would have spent on character art to the Armageddon website for upkeep.
Thus everyone gets awesome character art -and- we have the potential of getting the server upgraded. Obviously this plan is contingent on reliable cashflow, so make sure to continue getting character art done at about 1 new portrait every month or so.
Thank you.
http://www.zalanthas.org/gdb/index.php/topic,43679.msg688918.html#new
Thank you for looking into this Morgenes, I hope you had a pleasant father's day.
(WARNING: Wilds Guesses and Speculation Ahead!)I doubt RAM is the issue. I've ran a few MUDs and I've never seen a process run (DikuMUD or CircleMUD) with more than 5MB to 20MB tops of RAM usage. (With all areas loaded into memory, character data, etc).
I have a feeling it has to do with the "heartbeat" code, all the updates and functions that need to run on the game heartbeat which could run as often as every second. (NPC movement, regen, NPC tracking, respawns, weather changes, time changes, shop updates, triggers like timed speech scripts, updating hunger/thirst, updating poisons, updating Psionic / Magical affects, and many many more things...)
It seems like the heartbeats run much slower, proof of this is that time doesn't pass at the rate it should be passing and all because the code that needs to run on each heartbeat is taking too long. :'(
This is just a wild guess based on past experiences and I have no real evidence as to whether or not this is ARMs problem to back up what I'm saying, but it's a possibility. ???
(/END of Wild Guesses and Speculation)Looks like they are trying to figure out the issue right now...
QuoteArmageddon last booted 16 minutes and 31 seconds ago.
QuoteConnected to host armageddon.org
Armageddon is full. There is currently a limit of 1 players.
I hope it gets resolved and the game is opened again soon... I am horribly and irredeemably addicted to ARM. :-[
Oh so addicted to ARM... :o
EDIT:Game is back up, wonder if the made any headway in getting this resolved... ???
Something I've noticed about the lag is it doesn't seem to be traditional lag, where your connection slows to a crawl but the game world moves on right as rain. It appears (to my view anyway) that the game world is slowing to a crawl and connectivity is fine. I've noticed that ticks of things that take time in the game seem virtually unaffected by the 'lag' leading my to believe that the entire game, not just players, are experiencing the same effect.
Yes, I was noticing the ic hours ticking off as normal (at least it appeared to me) but everything else going on was taking longer than normal.
Quote from: A Large Bag on June 18, 2012, 02:14:27 PM
Yes, I was noticing the ic hours ticking off as normal (at least it appeared to me) but everything else going on was taking longer than normal.
That's because in game time is normalized to real world time, which isn't affected by lag.
In this day and age with cheap ram and processing power I doubt its either. The lag is not so random, though its been a bit sporadic lately it was pretty consistent the other couple of days. It always lasts the same amount of time as well.
My computer can run three or so high graphical games at once before it begins slowing down, again high ram and processes (graphics card but that not applicable). You know what slows it noticeably though, running anti virus scan, and spybot scan at the same time, got forbid i defrag or scan the hard-drive. That is why i think it might not so much processing power but forcing the harddrive to begin doing multiple things at once, it can only do it so fast. Its really my harddrive that bottlenecks my computer. There could be a intensive scan or backup going on at certain times (lasting about an hour or two long) that are causing the slow down on a machine. That is my theory anyways, and it is just for the fun of theory-crafting. I'm sure it will be found and fixed soon enough, again the game is still running smoothly most of the time at least. :)
I say it's the new code or the fixes that are causing the problems.
It's happened around the same times during the morning hours and at night. Starts right around 9 EDT PM and then lasts like 2-3 hours. Then in the mornings it starts right around the sames times which would be 9 EDT AM. At least that has been when I've experienced it at its worst.
Quote from: UnderSeven on June 18, 2012, 01:58:43 PM
Something I've noticed about the lag is it doesn't seem to be traditional lag fire.
It's not traditional fire. (http://www.youtube.com/watch?v=H4w0_n1Yras#t=3m)
You are correct, it seems to be something binding up in the game loop. Time is tied to the real clock, not to the number of game loops run, so that is staying ok.
We are adding logging to try and narrow down where the problem is.
Quote from: Morgenes on June 18, 2012, 03:52:21 PM
You are correct, it seems to be something binding up in the game loop. Time is tied to the real clock, not to the number of game loops run, so that is staying ok.
We are adding logging to try and narrow down where the problem is.
You guys are superstars. :)
I've noticed the lag occurs after the game has been active for a while. As pure speculation, this would lead me to
believe it may be tied into the recent changes to hunt code. The problems began occuring about the same time
as this feature was modified. Again purely observation: As the game is up for a while then people seem
to reach rooms and perhaps trigger the code to become active.
Never thought I'd be happy to be kicked off the game, but here we are.
My money's on the quit-safe rooms outside city gates. I'm not trying to bash the updates; I'm just trying to guess which one it might be if its from the recent updates.
Quote from: Cind on June 18, 2012, 04:18:31 PM
My money's on the quit-safe rooms outside city gates.
This wasn't a code change, but a building change. Sorta like modifying the description of a room. It changes nothing about the code of the rest of the game itself.
Quote from: Morgenes on June 18, 2012, 03:52:21 PM
You are correct, it seems to be something binding up in the game loop.
Every raptor in the game is now permahunting herself.
More likely it's just me incessantly checking my Skills.
Edit: Fun Fact: I saw the April Fools Joke a full thirty seconds before the announcement because of my habit.
Bit of slowdown, not as bad as usual though.
Quote from: Karieith on June 18, 2012, 08:53:25 PM
Bit of slowdown, not as bad as usual though.
You know that just means it's on its way down, right?
Give or take an hour, it is remarkably consistent.
...I just started loving this game.. so much sadness over the lag it hurts.
Whyyyy! I'm almost tempted to avoid playing during these times...
Quote from: Semper on June 18, 2012, 10:35:40 PM
Whyyyy! I'm almost tempted to avoid playing during these times...
My soul dies a little, when I try to login after work..
I haven't been able to play at previous peak lag times. Did the server migration fix the lag, or is it still around?
Sure seems to have done so, yes.
I'm still hitting hiccups but at this point I'm pretty sure it's me and not the server.
Thanks for fixing this so quick guys.
Not sure if I'm the only one, but recently I've been getting some heavy lag spikes around this time. Other websites open without issue..
Anybody else?
Quote from: Vox on June 28, 2012, 07:51:31 PM
Not sure if I'm the only one, but recently I've been getting some heavy lag spikes around this time. Other websites open without issue..
Anybody else?
Newp. Solid, over here.
I've had a solid line to armageddon since I started.
solid here too.
Just had a bit of a lag spike.
Been getting them for the last thirty minutes or so myself.
Been having them, too.
Ha, I thought it was my internet.
I wonder if it's just me but I was getting brutal lag spikes today. :-[
Is it just me, or have others been kicked out?
I was logged in for like 2 seconds
I'm still unable to log in
Ping and trace say SCREW YOU BUDDY!!!
1 <1 ms <1 ms <1 ms 192.168.0.1
2 39 ms 39 ms 39 ms ptld-dsl-gw44-236.ptld.qwest.net [207.225.84.236
]
3 39 ms 39 ms 39 ms ptld-agw1.inet.qwest.net [207.225.86.89]
4 43 ms 43 ms 43 ms sea-brdr-02.inet.qwest.net [67.14.41.18]
5 43 ms 43 ms 42 ms 63.146.26.82
6 45 ms 44 ms 44 ms xe-0-0-0.mpr2.sea1.us.above.net [64.125.31.10]
7 98 ms 98 ms 98 ms xe-1-2-0.cr2.ord2.us.above.net [64.125.31.2]
8 122 ms 131 ms 122 ms xe-2-1-0.cr2.lga5.us.above.net [64.125.27.34]
9 118 ms 118 ms 118 ms xe-1-0-1.er2.lga5.us.above.net [64.125.26.166]
10 118 ms 117 ms 117 ms 64.124.44.213.interserver.com [64.124.44.213]
11 119 ms 118 ms 118 ms edge-12-teb1.us.as19318.net [64.20.32.78]
12 119 ms 119 ms 119 ms openvz1.trouble-free.net [69.10.46.218]
13 119 ms 119 ms 119 ms ginka.armageddon.org [209.159.155.76]
I had no problems at all.
The evil entity known as LAG has risen once more. Fight this beast with metrics, if this reboot doesn't fix it.
Hexxus LAG, the very spirit of destruction, rose up from the bowels of the earth, and rained down his poison...
(http://t0.gstatic.com/images?q=tbn:ANd9GcRdi7COvkPuOUPHx131nbv8a0EWp7Mn4rzSztSUg8iBqqj6fgvB)
Yeah, I don't know why I thought of Fern Gully, but I did.
How do I obtain metrics again? ..I use atlantis? :-[
EDIT: ^ I love you Delirium for using hexxus in this thread to represent lag
traceroute to armageddon.org (209.159.155.76), 30 hops max, 60 byte packets
1 unknown (192.168.1.1) 1.228 ms 1.171 ms 1.630 ms
2 * * *
3 ae0-1031.cr02.dytnoh55.swo.rr.com (184.59.244.116) 23.962 ms 24.722 ms 24.708 ms
4 network-065-029-001-046.midwest.rr.com (65.29.1.46) 34.825 ms 34.858 ms 34.793 ms
5 ae-3-0.cr0.dca20.tbone.rr.com (66.109.6.70) 38.932 ms 38.914 ms 38.891 ms
6 so-1-1-1.a0.alb75.tbone.rr.com (66.109.1.49) 38.751 ms 107.14.19.135 (107.14.19.135) 32.755 ms ae-2-0.c1.nyc90.tbone.rr.com (66.109.1.49) 33.969 ms
7 xe-0-1-1.er2.iad10.us.above.net (64.125.12.61) 33.925 ms 27.845 ms 31.455 ms
8 xe-5-1-0.cr2.dca2.us.above.net (64.125.29.77) 41.067 ms xe-4-1-0.cr2.dca2.us.above.net (64.125.29.214) 35.830 ms xe-5-1-0.cr2.dca2.us.above.net (64.125.29.77) 34.030 ms
9 xe-3-2-0.cr2.lga5.us.above.net (64.125.26.110) 43.372 ms xe-2-2-0.cr2.lga5.us.above.net (64.125.26.106) 40.800 ms 40.754 ms
10 xe-0-0-1.mpr2.ewr2.us.above.net (64.125.31.173) 39.274 ms 39.242 ms 41.460 ms
11 208.184.34.234.IPYX-069067-ZYO.above.net (208.184.34.234) 86.552 ms 86.509 ms 75.991 ms
12 openvz1.trouble-free.net (69.10.46.218) 37.707 ms 33.969 ms 34.756 ms
13 ginka.armageddon.org (209.159.155.76) 36.353 ms 33.246 ms 36.877 ms
****@****-AO722:~$ armageddon.org
and ping
***@****-AO722:~$ ping armageddon.org
PING armageddon.org (209.159.155.76) 56(84) bytes of data.
64 bytes from ginka.armageddon.org (209.159.155.76): icmp_req=1 ttl=52 time=34.9 ms
64 bytes from ginka.armageddon.org (209.159.155.76): icmp_req=2 ttl=52 time=40.2 ms
64 bytes from ginka.armageddon.org (209.159.155.76): icmp_req=3 ttl=52 time=82.2 ms
64 bytes from ginka.armageddon.org (209.159.155.76): icmp_req=4 ttl=52 time=34.6 ms
64 bytes from ginka.armageddon.org (209.159.155.76): icmp_req=5 ttl=52 time=37.7 ms
64 bytes from ginka.armageddon.org (209.159.155.76): icmp_req=6 ttl=52 time=34.0 ms
64 bytes from ginka.armageddon.org (209.159.155.76): icmp_req=7 ttl=52 time=39.7 ms
64 bytes from ginka.armageddon.org (209.159.155.76): icmp_req=8 ttl=52 time=46.2 ms
64 bytes from ginka.armageddon.org (209.159.155.76): icmp_req=9 ttl=52 time=52.8 ms
64 bytes from ginka.armageddon.org (209.159.155.76): icmp_req=10 ttl=52 time=62.0 ms
64 bytes from ginka.armageddon.org (209.159.155.76): icmp_req=11 ttl=52 time=74.1 ms
64 bytes from ginka.armageddon.org (209.159.155.76): icmp_req=12 ttl=52 time=85.6 ms
64 bytes from ginka.armageddon.org (209.159.155.76): icmp_req=13 ttl=52 time=94.4 ms
64 bytes from ginka.armageddon.org (209.159.155.76): icmp_req=14 ttl=52 time=36.2 ms
64 bytes from ginka.armageddon.org (209.159.155.76): icmp_req=15 ttl=52 time=33.9 ms
64 bytes from ginka.armageddon.org (209.159.155.76): icmp_req=16 ttl=52 time=34.6 ms
64 bytes from ginka.armageddon.org (209.159.155.76): icmp_req=17 ttl=52 time=32.8 ms
64 bytes from ginka.armageddon.org (209.159.155.76): icmp_req=18 ttl=52 time=32.8 ms
64 bytes from ginka.armageddon.org (209.159.155.76): icmp_req=19 ttl=52 time=33.2 ms
64 bytes from ginka.armageddon.org (209.159.155.76): icmp_req=20 ttl=52 time=33.3 ms
64 bytes from ginka.armageddon.org (209.159.155.76): icmp_req=21 ttl=52 time=33.4 ms
64 bytes from ginka.armageddon.org (209.159.155.76): icmp_req=22 ttl=52 time=34.9 ms
64 bytes from ginka.armageddon.org (209.159.155.76): icmp_req=23 ttl=52 time=34.6 ms
64 bytes from ginka.armageddon.org (209.159.155.76): icmp_req=24 ttl=52 time=32.5 ms
Once again for lag, the best way to assist staff is to do a trace route and a ping. Thus the thread! Knowledge is power. Whoosh!
Quote from: Jeshin on May 03, 2013, 02:49:55 AM
Once again for lag, the best way to assist staff is to do a trace route and a ping. Thus the thread! Knowledge is power. Whoosh!
This is misleading, because not all lag is due to latency. Recent lag seems to have more to do with the server itself, like a memory leak in the code or something. Which is why it cleared up after Morgenes' reboot but slowly came back.
Yes. The trace route and ping allows them to rule out network issues and focus on server issues or vice versa.
Here's mine:
Reply from 209.159.155.76: bytes=32 time=19ms TTL=57
Reply from 209.159.155.76: bytes=32 time=18ms TTL=57
Reply from 209.159.155.76: bytes=32 time=19ms TTL=57
Reply from 209.159.155.76: bytes=32 time=18ms TTL=57
Reply from 209.159.155.76: bytes=32 time=17ms TTL=57
Reply from 209.159.155.76: bytes=32 time=19ms TTL=57
Reply from 209.159.155.76: bytes=32 time=19ms TTL=57
Reply from 209.159.155.76: bytes=32 time=18ms TTL=57
Reply from 209.159.155.76: bytes=32 time=19ms TTL=57
Reply from 209.159.155.76: bytes=32 time=18ms TTL=57
Reply from 209.159.155.76: bytes=32 time=19ms TTL=57
Reply from 209.159.155.76: bytes=32 time=21ms TTL=57
Reply from 209.159.155.76: bytes=32 time=18ms TTL=57
Reply from 209.159.155.76: bytes=32 time=18ms TTL=57
Reply from 209.159.155.76: bytes=32 time=19ms TTL=57
Reply from 209.159.155.76: bytes=32 time=19ms TTL=57
Reply from 209.159.155.76: bytes=32 time=17ms TTL=57
Reply from 209.159.155.76: bytes=32 time=17ms TTL=57
Reply from 209.159.155.76: bytes=32 time=17ms TTL=57
Reply from 209.159.155.76: bytes=32 time=19ms TTL=57
Reply from 209.159.155.76: bytes=32 time=18ms TTL=57
Reply from 209.159.155.76: bytes=32 time=17ms TTL=57
Reply from 209.159.155.76: bytes=32 time=18ms TTL=57
Reply from 209.159.155.76: bytes=32 time=17ms TTL=57
Reply from 209.159.155.76: bytes=32 time=17ms TTL=57
Reply from 209.159.155.76: bytes=32 time=18ms TTL=57
Reply from 209.159.155.76: bytes=32 time=19ms TTL=57
Reply from 209.159.155.76: bytes=32 time=19ms TTL=57
Reply from 209.159.155.76: bytes=32 time=19ms TTL=57
Reply from 209.159.155.76: bytes=32 time=18ms TTL=57
Reply from 209.159.155.76: bytes=32 time=18ms TTL=57
Reply from 209.159.155.76: bytes=32 time=22ms TTL=57
Reply from 209.159.155.76: bytes=32 time=21ms TTL=57
Reply from 209.159.155.76: bytes=32 time=17ms TTL=57
Reply from 209.159.155.76: bytes=32 time=18ms TTL=57
Reply from 209.159.155.76: bytes=32 time=19ms TTL=57
Reply from 209.159.155.76: bytes=32 time=18ms TTL=57
Reply from 209.159.155.76: bytes=32 time=20ms TTL=57
Reply from 209.159.155.76: bytes=32 time=18ms TTL=57
Reply from 209.159.155.76: bytes=32 time=17ms TTL=57
Reply from 209.159.155.76: bytes=32 time=18ms TTL=57
Reply from 209.159.155.76: bytes=32 time=18ms TTL=57
Reply from 209.159.155.76: bytes=32 time=18ms TTL=57
Reply from 209.159.155.76: bytes=32 time=18ms TTL=57
Reply from 209.159.155.76: bytes=32 time=18ms TTL=57
Reply from 209.159.155.76: bytes=32 time=17ms TTL=57
Tracing route to ginka.armageddon.org [209.159.155.76]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms ELEMENTS [***.***.*.*]
2 * * * Request timed out.
3 11 ms 10 ms 11 ms ***.***.***.*
4 21 ms 22 ms 19 ms 216.113.122.98
5 18 ms 19 ms 19 ms eqix-ny2.interserver.com [198.32.118.45]
6 19 ms 19 ms 18 ms openvz1.trouble-free.net [69.10.46.218]
7 18 ms 18 ms 17 ms ginka.armageddon.org [209.159.155.76]
Trace complete.
Really really bad, right now.
Can't even log in properly at this point.
Hm, this is quite bad. Ping times still in the 18-20ms range. Definitely not network related. And with ~50 players online, it doesn't seem to have anything to do with current player populations.
My traces and pings seem to be coming back fairly clean, yet I am still experiencing bursts of frequent lag for hours on end.
I think this is actually the Ginka server stalling and not a connection issue.
I don't know, I'm not a network/pc guru to that extent.
Yeah my ping is coming back ~90-100ms but I am also experiencing significant lag in game.
.... been saying this for a few days, now.
Here's mine. This is all moonspeak to me but it doesn't look good.
Traceroute has started ...
traceroute to 209.159.155.76 (209.159.155.76), 64 hops max, 40 byte packets
1 192.168.4.1 (192.168.4.1) 18.606 ms 1.597 ms 1.476 ms
2 * * *
3 ip-86-49-52-1.net.upcbroadband.cz (86.49.52.1) 11.046 ms 27.336 ms 10.676 ms
4 84.116.221.225 (84.116.221.225) 109.462 ms 110.406 ms 110.551 ms
5 84.116.135.1 (84.116.135.1) 137.951 ms 135.289 ms 113.363 ms
6 uk-lon02a-rd2-xe-0-2-2.aorta.net (84.116.133.93) 130.538 ms 176.606 ms 84.116.133.214 (84.116.133.214) 106.913 ms
7 us-nyc01c-rd1-pos-3-0-0.aorta.net (213.46.160.126) 116.662 ms us-nyc01c-rd1-pos-1-0-0.aorta.net (213.46.160.206) 112.720 ms us-nyc01c-rd1-pos-3-0-0.aorta.net (213.46.160.126) 113.679 ms
8 84.116.135.98 (84.116.135.98) 111.552 ms 132.028 ms 112.204 ms
9 above.net (198.32.118.25) 112.222 ms 120.108 ms 142.055 ms
10 xe-4-1-0.cr2.lga5.us.above.net (64.125.30.209) 113.103 ms 117.103 ms 113.870 ms
11 xe-0-0-1.mpr2.ewr2.us.above.net (64.125.31.173) 108.962 ms 108.379 ms 105.221 ms
12 208.184.34.234.IPYX-069067-ZYO.above.net (208.184.34.234) 120.685 ms 119.995 ms 122.125 ms
13 openvz1.trouble-free.net (69.10.46.218) 119.565 ms 115.395 ms 115.204 ms
14 ginka.armageddon.org (209.159.155.76) 114.689 ms 120.688 ms 117.383 ms
Still bad. Yep.
Ok, the game is pretty much unplayable for me right now.
I'm experiencing pretty solid lag but I'm not seeing the cause....
C:\>tracert armageddon.org
Tracing route to armageddon.org [******************]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 192.168.1.1
2 37 ms 19 ms 30 ms cpe-76-176-32-1.san.res.rr.com [76.176.32.1]
3 10 ms 9 ms 8 ms tge1-1.crlscaij-cer02.socal.rr.com [76.166.18.10
1]
4 18 ms 14 ms 15 ms tge0-8-0-1.sndhcaax-ccr02.socal.rr.com [72.129.1
.118]
5 20 ms 16 ms 15 ms agg22.tustcaft-ccr01.socal.rr.com [72.129.1.2]
6 17 ms 23 ms 15 ms ae-6-0.cr0.lax30.tbone.rr.com [66.109.6.214]
7 13 ms 16 ms 14 ms ae-1-0.pr0.lax10.tbone.rr.com [66.109.6.131]
8 14 ms 16 ms 13 ms xe-1-3-0.mpr1.lax12.us.above.net [64.125.13.45]
9 19 ms 17 ms 21 ms xe-3-0-0.cr2.lax112.us.above.net [64.125.30.29]
10 53 ms 52 ms 51 ms xe-3-2-0.cr2.iah1.us.above.net [64.125.30.49]
11 78 ms 78 ms 79 ms xe-5-0-0.cr2.dca2.us.above.net [64.125.31.250]
12 82 ms 83 ms 87 ms xe-3-2-0.cr2.lga5.us.above.net [64.125.26.110]
13 126 ms 84 ms 82 ms xe-0-0-1.mpr2.ewr2.us.above.net [64.125.31.173]
14 82 ms 82 ms 82 ms 208.184.34.234.IPYX-069067-ZYO.above.net [208.18
4.34.234]
15 82 ms 82 ms 83 ms openvz1.trouble-free.net [69.10.46.218]
16 83 ms 82 ms 83 ms ginka.armageddon.org [209.159.155.76]
Trace complete.
I doubt we need any more trace route or ping logs.. I'm currently using some shitty internet connection from my local GSM provider and my ping 320 ms. But in game, I realized two things;
1. As visible, it's way too laggy.
2. Commands with no 'before' delay are getting a 'before' delay. For example; if I wait enough to ensure my character has no delay in progress, then type 'n;l n' it sometimes looks north - response coming nearly instantly - , then moves north in a second or two.
Damn.. I'm in the field in the middle of nowhere and I'm forced to stay here. There's nothing else to do here. I would be delighted if this could be fixed.
Edit: Not 32 ms ping of course.. It's 320 ms.. Sorry about the confusion, I seem to have forgotten the zero.
The last 2-3 weeks I have seen a performance hit. Did we switch providers? Can I help in anyway to resolve the game performance issues? I am willing to contribute knowledge, finical help, etc to help work on getting the user experience resolved.
Just let me know if you need anything.
Corey