satisfactory-server: Server won't start anymore with latest image
Hi @wolveix, thanks for the great work!
Your Satisfactory image ran smooth until yesterday. After over 2 weeks my server won’t start anymore. It crashed soon after I fell down and should have died, but didn’t. I stopped the server, saw that you made 2 commits, pulled and started. Since then this happens:
satisfactory-server | Checking available space...
satisfactory-server | Downloading the latest version of the game...
satisfactory-server | Redirecting stderr to '/root/.steam/logs/stderr.txt'
satisfactory-server | Looks like steam didn't shutdown cleanly, scheduling immediate update check
satisfactory-server | [ 0%] Checking for available updates...
satisfactory-server | [----] Verifying installation...
satisfactory-server | Steam Console Client (c) Valve Corporation
satisfactory-server | -- type 'quit' to exit --
satisfactory-server | Loading Steam API...OK
satisfactory-server | @sSteamCmdForcePlatformType windows
satisfactory-server | "@sSteamCmdForcePlatformType" = "windows"
satisfactory-server | Logging in user 'xxx' to Steam Public...OK
satisfactory-server | Waiting for client config...OK
satisfactory-server | Waiting for user info...OK
satisfactory-server | force_install_dir /config/gamefiles
satisfactory-server | app_update "526870"
satisfactory-server | Success! App '526870' already up to date.
satisfactory-server | quit
satisfactory-server | /root/.steam/steamcmd/steamcmd.sh: line 38: 16 Killed $DEBUGGER "$STEAMEXE" "$@"
I tried restarting and removing data. I ended up with only the savefile.sav and the docker-compose.yml
version: '3'
services:
satisfactory-server:
container_name: 'satisfactory-server'
hostname: 'satisfactory-server'
image: 'wolveix/satisfactory-server:latest'
environment:
- STEAMUSER=xxx
- STEAMPWD=yyy
- STEAMCODE=zzz
- MAXBACKUPS=100
ports:
- '7777:7777/udp'
volumes:
- './config:/config'
restart: unless-stopped
Sadly there is only the latest
tag so I can’t check if it’s an issue with the image.
Any ideas?
PS.: The savefile does load on another server with the latest image.
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Comments: 31 (16 by maintainers)
Commits related to this issue
- Modify previous commit's noninteractive fix (hopefully addressing #18) — committed to wolveix/satisfactory-server by wolveix 3 years ago
@VergilzG I found an older build from 3 months ago, which I’ve just pushed to
wolveix/satisfactory-server:dev
. Please test this and report back 😃Yeah, I confirm that, it’s working with the old image (DEV).
I will be glad to help you to solve it.
Thanks for the fast update, I pulled the latest update, unfortunately from my side it’s not working but it’s better. It doesn’t freeze the entire NAS this time, it’s launching the container, however, it’s not downloading the game and crashed after couple of minutes later. I tried to rerun after that, it immediately stop with the following errors
(Docker time is not up to date, 23:00 (11PM) on the screen is currently 01:00 AM)
How it’s managed on synology : https://www.youtube.com/watch?v=krHZB3D_U9E