Easter Bunny special version for you people.
1.4.0 (24 march 2021)
- The “Launcher” log tab now has the date and time displayed for each entry in the log (local time)
- The RCon connection now has a 10 seconds timeout, to avoid the tool to stay stuck in case of bad connection (or server stuck), and the error messages are now properly sent to the launcher log instead of being printed to stderr
- A new “Zombie Check” checkboard and delay has been added: When enabled it will automatically try to kill the process if the monitored input/output data has not changed for a specified amount of time
Dedicated Server Launcher 1.4.0
First, a warning: I’m not able to get the server to freeze or get stuck like some of you got on shutdown, so all I did was to “simulate” using tools like SysInternals “Process Monitor” that has a “Suspend” feature, or getting the server stopped in the debugger, so that may or may not be representative of what happens when the server is stuck.
How’s it’s working:
- I regularly call a Win32 function called ‘GetProcessIoCounters’ which returns how many IO operations have been done by the process
- If two consecutive calls contains different values, then it means the server is at least “doing something”
- It the content has not changed in more than a specific amount of time, then it’s considered as a zombie.
Obviously this approach will fail horribly if the server is only half broken, like for example it still writes to disk, or still answers on the network, while being otherwise “not really working”, so we may have to work on the heuristics if that does not work.
So, how do you enable that?
DedicatedServerLauncher_1.4.01207×865 98.2 KBSo first, the “Start server if not running” has moved from the “Automatic Restart” to the top of the UI, and instead you get two new controls:
- A “Zombie Check” box
- A “Time Selector”
Using these two you can enable the automatic zombie check.
And in the “Launcher” tab, you have the messages that indicate when a Zombie process has been detected, and when the execution is planned for.
This information is also repeated in the status bar.
I wanted to spend more time on it, but since a long easter break is happening, it made sense to me to try to get you the version as fast as possible so you could enjoy a “stuckless” experience.
That’s assuming it works, and that’s where you come in: If you are one of the persons who had their server get stuck, please test the version and tell me if it works, and if not, then please tell what the problem is, if it’s the timing not working, spurious detection, or if simply the launcher never flag the process as “Zombie”.
Thanks!