Nothing much you can do, the Server just locked up for unknown reason (no log, nothing, just locked up).
That's one of the major issues with IL-2 Great Battles: You just don't have any f*ckin' logs to see what happened, neither on Server nor Client side.
In 1946 we know every tiny fart the game makes, in IL-2 GB we hardly know it's there at all.
In the past, I've developed a "Watchdog" which would check whether the Server Process still responds to commands.
If not, it would simply take screenshots, collect logs (if available - in fact this only collected me a hundred of 0-byte files), kill the DServer process and restart it.
The issue now is that the process
does respond to commands (except for the "exit" command which will hang the process completely), it's just that the Server doesn't do anything anymore except for hogging the CPU with 100% load and fooling the admin into thinking it was still alive.
The only thing that gave me a clue today that something's fishy is that the "Tick delay" of the Server didn't match the CPU load anymore.
The "Tick delay" was at 13.5 and the CPU load at 100%. Normally, a CPU load of 100% equals a "Tick delay" of 20.
So it seems I will have to enhance the Watchdog in order to work around this issue.
Again.
The next workaround for issues brought to the game by large updates.
This, unfortunately, has a long lasting history in IL-2 Great Battles already...
Mike