Closed FelipeCordova closed 1 year ago
I just experienced this same issue.
I wanted to play the new valentines update, and restarted the container to force an update.
When it attempted to start, this is the error I see in the logs:
Connecting anonymously to Steam Public...OK Waiting for client config...OK Waiting for user info...OK Success! App '1007' already up to date. Success! App '1963720' already up to date. Started server process with pid 69 [UnityMemory] Configuration Parameters - Can be set up in boot.config "memorysetup-bucket-allocator-granularity=16" "memorysetup-bucket-allocator-bucket-count=8" "memorysetup-bucket-allocator-block-size=4194304" "memorysetup-bucket-allocator-block-count=1" "memorysetup-main-allocator-block-size=16777216" "memorysetup-thread-allocator-block-size=16777216" "memorysetup-gfx-main-allocator-block-size=16777216" "memorysetup-gfx-thread-allocator-block-size=16777216" "memorysetup-cache-allocator-block-size=4194304" "memorysetup-typetree-allocator-block-size=2097152" "memorysetup-profiler-bucket-allocator-granularity=16" "memorysetup-profiler-bucket-allocator-bucket-count=8" "memorysetup-profiler-bucket-allocator-block-size=4194304" "memorysetup-profiler-bucket-allocator-block-count=1" "memorysetup-profiler-allocator-block-size=16777216" "memorysetup-profiler-editor-allocator-block-size=1048576" "memorysetup-temp-allocator-size-main=4194304" "memorysetup-job-temp-allocator-block-size=2097152" "memorysetup-job-temp-allocator-block-size-background=1048576" "memorysetup-job-temp-allocator-reduction-small-platforms=262144" "memorysetup-temp-allocator-size-background-worker=32768" "memorysetup-temp-allocator-size-job-worker=262144" "memorysetup-temp-allocator-size-preload-manager=262144" "memorysetup-temp-allocator-size-nav-mesh-worker=65536" "memorysetup-temp-allocator-size-audio-worker=65536" "memorysetup-temp-allocator-size-cloud-worker=32768" "memorysetup-temp-allocator-size-gfx=262144" ./launch.sh: line 46: 69 Segmentation fault (core dumped) DISPLAY=:99 LD_LIBRARY_PATH="$LD_LIBRARY_PATH:../Steamworks SDK Redist/linux64/" ./CoreKeeperServer -batchmode -logfile -world "${WORLD_INDEX}" -worldname "${WORLD_NAME}" -worldseed "${WORLD_SEED}" -gameid "${GAME_ID}" -datapath "${STEAMAPPDATADIR}" -maxplayers "${MAX_PLAYERS}" -logfile CoreKeeperServerLog.txt
Just confirming that I'm seeing the same thing.
I think this is related to the game server itself: https://steamcommunity.com/app/1621690/discussions/0/3759978783504303058/
You are right. Im closing the issue. Thanks!
Today i restarted my containter due to the last seasonal update, i encountered this error on restarting. I tried to find more information about it, but i couldn't find any clues. Its seems to me that could be a display problem, because the segmentation error code changed when i used other docker images (trying to add /tmp/.X11-unix as a volume).
These are the docker logs before dying
Extra info: The server where the container is running is also running other stuff but hasn't been updated in a long time.