93 replies to this topic

[FUG!T!V3]

Hey guys!


It is 10:26 PM EST on Friday, October 18th, 2013 and tonight the server is lagging, usually my ping is at 48 and so is Saukra's and a few others, but tonight the server has been lagging, and one CI moment, and the lag-o-meter in green looked like the lawn has not been mowed ( meaning the green from the lag-o-meter ) looked a little big. This is our pings:  wet-20131018-220816.PNG   267.16KB   0 downloads

 

 

Just letting anyone who knows or if they can fix the situation (I know someone posted a similar topic a month ago but just wanted to post a most recent one)

Thanks,

FUG!T!V3

 

Edited by FUG!T!V3, 18 October 2013 - 04:53 PM.

[Jecoliah]

Me and Peyote have done all we can do with the access we have to the B1 server.

Sudden will have to do something about this.

 

With all the posts about lags and freezing i am afraid this might end up killing the B1 server.

If this "can't" be resolved i am all for moving the server to a better host but that is up to Sudden.

 

 

 

Jec

[djbo]

Has anyone informed Sudden of this problem? Else not much will happen

[G0rt]

I think its the NSA sniffing our packets..  Yes..  I think thats the problem..

[Bill]

Happening again right now.  Saturday at 7 PM ET.

[keisko]

Yep still lagging.. a reboot may help. There are enough players right now but we can't play ((

Edited by keisko, 19 October 2013 - 01:36 PM.

[Jecoliah]

Just seen the last 2 messages.

Peyote says he thinks he found the issue,  i can see he is on the server right now.

 

Lets see if it is resolved.

 

 

 

Jec

[Bill]

Yep he fixed it!

[keisko]

I didn't check it yet but thanks Pey!

btw what was the issue?

[peyote]

ET server was running twice

 

I can only guess why, we have 2 scripts for taking care of b1; an old and the other a fancy new initscript.

 

I suppose someone did restart the machine, and then started b1 with the old script.

At some later time crontab kicked in and started the initscript.

 

edit: did not discover that the first time I checked out b1, as its kinda unexpected.

Edited by peyote, 20 October 2013 - 02:23 AM.

[peyote]

No this should not happen again

I modified the old script, so it does just stop itself and tell to use the new script. So basically b1 won't start with the old one.

And the new script is 'smart' , it detects (yer not really , just looks for its own instance of ET ..)  if b1 is running or not and such things.

 

So unlikely it happens again. And if it does, I know what to look for. I am still wondering how long this has been going on....

Edited by peyote, 20 October 2013 - 03:33 AM.
fixed content missing .D

[Bill]

btw this is probably why we were having xpsave issues too.

[Jecoliah]

btw this is probably why we were having xpsave issues too.

 

Yes, we should not have that problem anymore and we should not have the freezing problem anymore.

 

But as far as you guys that are getting double ping on occasion, keep an eye on that.

It would be nice if that was resolved too but, it is doubtful as i believe it is an ISP routing issue.

 

 

 

Jec

[FUG!T!V3]

A big hats off to Peyote for his hard work he did to get everything resolved!

Edited by FUG!T!V3, 21 October 2013 - 03:58 PM.

[neurosis]

Just to put it out there, B1 lagging heavily tonight as well. Looked like it was going to crash out a couple of times.

[BangBang]

In case this helps. Seem to make it to Secaucus, NJ then dies.

 

Tracing route to bunker1.aaxxss.com [66.45.251.202]

over a maximum of 30 hops:

 

  1    <1 ms    <1 ms    <1 ms  Home950.lan [192.168.1.1]

  2    72 ms    39 ms    24 ms  cpe-24-193-184-1.nj.res.rr.com [24.193.184.1]

  3     9 ms    11 ms    10 ms  ten-0-2-1-0.nycmnyp-rtr1.nj.rr.com [24.168.128.2

34]

  4    10 ms    11 ms    11 ms  bun118.nyquny91-rtr001.nyc.rr.com [184.152.112.9

5]

  5    12 ms    11 ms    15 ms  ae-3-0.cr0.nyc20.tbone.rr.com [66.109.6.76]

  6    67 ms    11 ms    10 ms  107.14.17.216

  7    34 ms    37 ms    36 ms  209.220.18.33.ptr.us.xo.net [209.220.18.33]

  8    22 ms    11 ms    11 ms  207.88.13.58.ptr.us.xo.net [207.88.13.58]

  9    12 ms    11 ms    11 ms  ae0d0.mcr1.nyc-ny.us.xo.net [216.156.0.18]

 10    12 ms    12 ms    11 ms  207.239.51.86

 11    11 ms    11 ms    12 ms  64.20.32.214

 12     *        *        *     Request timed out.

 13     *        *        *     Request timed out.

 14     *       39 ms     *     bunker1.aaxxss.com [66.45.251.202]

 15     *        *        *     Request timed out.

 16    41 ms     *        *     bunker1.aaxxss.com [66.45.251.202]

 17     *        *       40 ms  bunker1.aaxxss.com [66.45.251.202]

[FUG!T!V3]

As we speak: 10:31 PM, I am using my xfire list and refreshing, still showed people on, when I got on, Liquid timed out, checked my lag-o-meter and one red block came on (along with CI - Connection Inturrupted), but when I refresh my xfire server list, the ping doesnt appear, and then it does, it refreshed not long ago with Peyote, Bill, B!O and Liquid playing, and I get on and it's just B!o, Bill, and Pey in spec, and liquid timed out, so I left, refreshed, and it's just Peyote, but he is in spec, so looks like the server or something is having some problems again tonight. Just thought I would post my experience from what I saw, cause the server ping showing from xfire would have none, then go to 70, then update, then still same people, and then updated for good with ping going to 70 then no ping showing.

[peyote]

 bunker1.aaxxss.com.png   52.45KB   0 downloads

 bunker1.aaxxss.com.zip   13.02KB   10 downloads <- download this to see the actualy image...

I have stopped the et-server for about half of the lower graph. And it did not have any effect on that packet loss.

TBH I have no clue whats the issue. If its ddos or network issues or hardware failure.

 

edit: d'oh this resizing image is really upsetting me..

 

edit: Tue Oct 22 22:57:36 EDT 2013

The packet loss stopped.

Edited by peyote, 22 October 2013 - 03:04 PM.

[BangBang]

Seems to have cleared up now. hopefully stays that way by tomm nite

[neurosis]

There is still an issue. We have all been clearing out early and going to IOW to get away from the lag.  I hope that its fixed soon.