Can the?

[godsmack]

Can the engine actually keep up with all the new options? Was running my server tonight with 20 out of 20 on it and it just lagged out. No errors reported in qconsole.

[Razo[R]apiD]

Yes it can, all in all everything will depend on your net connection and machine processor at the end. Most of the options aren't running all the time. Only few and we're constantly optimizing them.

[godsmack]

Looked through it again today and it was flooded with this.

SV packet 208.122.49.139:23124 : getstatus
SV packet 208.122.49.139:23124 : getstatus
SV packet 208.122.49.139:23124 : getstatus
SV packet 208.122.49.139:23124 : getstatus
SV packet 208.122.49.139:23124 : getstatus
SV packet 208.122.49.139:23124 : getstatus
SV packet 208.122.49.139:23124 : getstatus
SV packet 208.122.49.139:23124 : getstatus
SV packet 208.122.49.139:23124 : getstatus
SV packet 208.122.49.139:23124 : getstatus
SV packet 208.122.49.139:23124 : getstatus
SV packet 208.122.49.139:23124 : getstatus
SV packet 208.122.49.139:23124 : getstatus
SV packet 208.122.49.139:23124 : getstatus
SV packet 208.122.49.139:23124 : getstatus
SV packet 208.122.49.139:23124 : getstatus
SV packet 208.122.49.139:23124 : getstatus
SV packet 208.122.49.139:23124 : getstatus
SV packet 208.122.49.139:23124 : getstatus
SV packet 208.122.49.139:23124 : getstatus
SV packet 208.122.49.139:23124 : getstatus
SV packet 208.122.49.139:23124 : getstatus
SV packet 208.122.49.139:23124 : getstatus
SV packet 208.122.49.139:23124 : getstatus
SV packet 208.122.49.139:23124 : getstatus
SV packet 208.122.49.139:23124 : getstatus
SV packet 208.122.49.139:23124 : getstatus
SV packet 208.122.49.139:23124 : getstatus
SV packet 208.122.49.139:23124 : getstatus
SV packet 208.122.49.139:23124 : getstatus
SV packet 208.122.49.139:23124 : getstatus
SV packet 208.122.49.139:23124 : getstatus
SV packet 208.122.49.139:23124 : getstatus
SV packet 208.122.49.139:23124 : getstatus

That is not even half of it. Only looks like it happened once.

[armageddon]

I had this happen once too. Wasn't sure what caused it, but it didnt happen again. I kept restarting the server, and it continued. I couldn't connect to the server while it was doing this either. After awhile it stopped. No clue what was going on.

[JoTo]

Thats just a query from e.g. a client like Xfire or Rcon tool

[Drewski]

Not just a typical client like XFire or All Seeing Eye
Hackers now have the ability to 'get status' or scan a server a thousand times a minute, each time the server has to send the info back to the client, causing the lag

This is a malicious threat, and a way of 'pinging' out the server causing it to crash

I hope they rot in hell

[Drewski]

Actually, Isn't there like a 'Flood Protect' in built in most Hosts Servers to stop this?

[James]

you can setup a firewall to do this, but I suppose I';m not sure. I don't see why the patch can't include a fix for this though. If we can check for connection status, we should be able to check for get status too?..

[Razo[R]apiD]

Patch only fixes buffer overflow crash caused by getstatus/getinfo and so on. However it can still lag the server. I'll try to fix this.

[armageddon]

When this happened to me, it was from a member who was playing at the time, and they didn't have a clue anything was happening. All of a sudden we were all disconnected. I kept restarting the server, and it kept doing it. It didn't stop for about 5 minutes.