COD4x Server Address
74.91.119.86:28960
I want to thank everyone for their patience in playing on the CoD4x server and suffering thru the crashes and reboots. I care deeply about our clan and everyone I play with, hence, my motivation to dedicate my time and put in the effort to make this happen.
Retrospect
When we first launched the CoD4x server it was on a managed NFO server, meaning all the server controls are with NFO, just put the mod files in there. The server was crashing due to fundamental changes in how the CoD4x code is re-written and how our mod handles player data. We had no way of figuring out what was wrong since we had no control over the server's internal behavior. I decided to launch the CoD4x server on a dedicated machine where I had absolute control over the server process. I recompiled the CoD4x server code and launch binary after binary. Each iteration informed by the logs collected when the server crashed. On the Linux machine I was able to capture the exact behavior of the server and put guard rails against crashing, but didn't address the root-cause. Until now.
I have strong confidence in the latest deployment that I have addressed the root-cause of the crashes. A bug in memory handling that becomes bigger and bigger as people join and leave the server. When a map changes it causes corruption and crashes the server. It took all of this to get to the bottom of this problem. The work arounds I put in, would delay the inevitable and one of the work arounds had a sever-side side effect. People with lossy connections @Icequeen@Dukoo @P1nh3ad or well high ping, would experience stuttering, this was real, caused by the bug, but made worse by the work around I put in to keep the server from crashing right away. I am confident that you will not experience this anymore.
If you know programming, I had to patch the disassembly of the stock COD4 server and recompile the CoD4x server code. Our mod does a double free of player data. This happens on the stock server too but the stock server is single threaded so while it never crashes it starts becoming laggy the longer it stays on. We change rotations every Friday so a server restart would clean the slate. The CoD4x server launches multiple threads, and does things in parallel, when the mod's code would try to delete player data upon disconnect, it would do that more than once in CoD4x, this would poison the memory heap. The only solution was to block the call in the server code. CoD4x automatically deletes all the pertinent player data on disconnect, the mod doesn't need to send that command in the script. This is in essence a two-part fix, put a check in the server code to don't let the memory get poisoned then remove all the player data delete from the mod's scripts/code. At the moment, I don't have the mod's source code so I did the only and the best thing I could.
I hope the server's clock-work like crashes are behind us and all my hard work and sleeplessness has paid off. There will still be small things here and there but we will address them as we go. Thank you for reading and happy gaming.