[1.198.033] Dedicated server fails to restart on its own
Hello Keen Support,
When scheduling automated restart on dedicated server (8h in our case), sometimes the new session gets stuck and fails to start up properly, possibly indicating a previous server session fails to gracefully exit and still has a socket registered, listening to the TCP port. This seems to happen regularly once every 4 or 5 cycles. Our current fix is to kill all dedicated server tasks and start it up manually again. Please find attached an example startup log and let me know what additional info you need.
on the dedicated server GUI, this is the line the startup process is held up at:
Error binding server endpoint: Only one usage of each socket address (protocol/network address/port) is normally permitted
Community, I'm not interested in using Torch, don't bother suggesting that.