Server stuck in restarting - healthcheck issue

[struppinet]

Hi,

server was working fine for a while but today I had the case that it didn't survive a restart and was then stuck in a restart loop until I manually changed the healthcheck.sh. Then the server was working fine after it had no timeout limit. It just took longer.

I assume it was some bandwidth issues with steam so the update check/client update took longer but I think there should be a case that handles steam issues as well if the server isn't even running yet.

Docker logs from the restart:

gaming_satisfactory.1.7fjd05mebwop@v2202201165783175348    | [  0%] Checking for available updates...
gaming_satisfactory.1.7fjd05mebwop@v2202201165783175348    | UpdateUI: skip show logo[----] !!! Fatal Error: Steamcmd needs to be online to update. Please confirm your network connection and try again.
gaming_satisfactory.1.7fjd05mebwop@v2202201165783175348    | src/tier0/threadtools.cpp (3601) : Assertion Failed: Illegal termination of worker thread 'Thread(0x0x5852f0c0/0x0xf76c9a'
gaming_satisfactory.1.tfmsbtjq8qoi@v2202201165783175348    | ===== Satisfactory Server 1.9.1 =====

Nevertheless: THANK YOU for your work! Really appreciate it to not have to handle the image myself :)

[wolveix]

Hey @struppinet, yeah this was a known concern when the healthcheck was first introduced. steamcmd. What you're suggesting isn't really possible unfortunately...perhaps we could just bump the initial grace period to 300s from 180s, and increase the timeout interval from 10s to 30s