Closed thetaiter closed 3 years ago
Do you have the complete log? From start to error.
What is the best way to do that? Supervisord splits the logs into stderr and stdout, so it is difficult to reconstruct the logs back in time order.
If this helps, it is happening during the nightly restart every night. Shutdown works successfully, but the server is never restarted.
Here are the relevant env variables I have set:
DISCORD_WEBHOOK: <redacted>
PRE_RESTART_HOOK: 'curl -sfSL -X POST -H "Content-Type: application/json" -d "{\"username\":\"Odin\",\"content\":\"Restarting server $SERVER_NAME in one minute!\"}" "$DISCORD_WEBHOOK" && sleep 60'
VALHEIM_LOG_FILTER_CONTAINS_Spawned: "Got character ZDOID from"
VALHEIM_LOG_FILTER_CONTAINS: 'Unity Log'
ON_VALHEIM_LOG_FILTER_CONTAINS_Spawned: '{ read l; l=${l//*ZDOID from /}; l=${l// :*/}; msg="Player **$l** joined server **$SERVER_NAME**\nIP: **$(curl ipinfo.io/ip):$SERVER_PORT**"; curl -sfSL -X POST -H "Content-Type: application/json" -d "{\"username\":\"Odin\",\"content\":\"$msg\"}" "$DISCORD_WEBHOOK"; }'
PRE_BOOTSTRAP_HOOK: 'curl -sfSL -X POST -H "Content-Type: application/json" -d "{\"username\":\"Odin\",\"content\":\"Starting server $SERVER_NAME.\nIP: **$(curl ipinfo.io/ip):$SERVER_PORT**\nThe server may take ~5 minutes to start up before you can connect.\"}" "$DISCORD_WEBHOOK"'
SERVER_PUBLIC: true
UPDATE_INTERVAL: 10800 # every 3 hours
UPDATE_IF_IDLE: true
RESTART_IF_IDLE: true
Also, the PRE_RESTART_HOOK does not fire.
What is the best way to do that? Supervisord splits the logs into stderr and stdout, so it is difficult to reconstruct the logs back in time order.
Just attach two files? My guess is that the container doesn't have enough resources. See https://github.com/lloesche/valheim-server-docker#system-requirements
Bingo, that was it. Didn't have enough RAM allocated. Thanks!
I got a bunch of lines like this when my server when down for restart, and the server did not come back up.