Server random crash

A good first start is not running your game server as root. If the KAG server gets hacked your entire box can get fucked. Is creating an extra user really that hard?

Additionally, KAG crashes randomly anyway. Just use a shell script to restart it when it fails.

 

It would be really nice of you if you could run your servers under gdb and provide us with backtrace which help us determine what the problem is. Here is short guide how to do it. https://forum.kag2d.com/threads/linux-how-to-run-a-server-and-help-the-devs-fix-crashes.5507/

 

Seems like it was directed at the OP, and the advice in it is good.


As Furai says, it would be good if you could run them under gdb and get a backtrace upon this crash happening so we can see where it's actually crashing and fix the issue. Seeing a name in a log and then your server crashing with a memory address dump is not enough information to even start debugging the issue. If the same user keeps doing this to servers we can ban him, but we need someone to be doing it to be able to catch and fix the vulnerability.

 

Do you have debug mode on?

 

Is this issue still prevalent? Did you run kagdedi under gdb and get a stacktrace?

Nice attitude.

 

There's a guy called C4Bios doing this on Aus servers as well - it could be that some weird install setup makes this happen on join, and the guy has no idea that he's crashing servers, or it could be an exploit. It would be really good to have a proper backtrace on where it's happening though - its clear that it's either a double or invalid free() call but not where it's being called or what it's being called on.
If you could do that (run in gdb, when it crashes type "bt full" and send output) that'd be great.

 

We've tried, he hasn't responded. It's not an "experiement", it just lets us get full info when the game crashes - applies to more crashes than just this one.