search

jsknnr / enshrouded-server

Run Enshrouded dedicated server in a container
MIT License
185 stars 23 forks source link

proton-latest | Error! App '2278520' state is 0x202 after update job. #52

Closed pixeliner closed 8 months ago

pixeliner commented 8 months ago

Hi there,

I'm encountering an issue while setting up Docker for an Enshrouded server on a Proxmox VM. I'm working with a limited-core, older PC server, and have decided to use Proton based on discussions I've seen on GitHub.

Here's what I've done so far:

  1. Forwarded both UDP ports on my router.
  2. Pulled the latest Docker image as of February 3rd at 17:30.
  3. Created a persistent volume using: docker volume create enshrouded-persistent-data
  4. Executed the following command to run the server:
docker run \
  --detach \
  --name enshrouded-server \
  --mount type=volume,source=enshrouded-persistent-data,target=/home/steam/enshrouded/savegame \
  --publish 15636:15636/udp \
  --publish 15637:15637/udp \
  --env=SERVER_NAME='Servername' \
  --env=SERVER_SLOTS=16 \
  --env=SERVER_PASSWORD='Serverpassword' \
  --env=GAME_PORT=15636 \
  --env=QUERY_PORT=15637 \
  sknnr/enshrouded-dedicated-server:proton-latest

However, the server starts well but then crashes. Here's the log output:

2024-02-03T16:52:53.946513385Z [  0%] Checking for available updates...
2024-02-03T16:52:53.946516752Z [----] Download complete.
2024-02-03T16:52:53.946520075Z [----] Extracting package...
2024-02-03T16:52:53.946523376Z [----] Extracting package...
2024-02-03T16:52:53.946526664Z [----] Extracting package...
2024-02-03T16:52:53.946529946Z [----] Extracting package...
2024-02-03T16:52:53.946534451Z [----] Installing update...
2024-02-03T16:52:53.946540824Z [----] Installing update...
2024-02-03T16:52:53.946547077Z [----] Installing update...
2024-02-03T16:52:53.946552356Z [----] Installing update...
2024-02-03T16:52:53.946557432Z [----] Installing update...
2024-02-03T16:52:53.946560909Z [----] Installing update...
2024-02-03T16:52:53.946564168Z [----] Installing update...
2024-02-03T16:52:53.946567462Z [----] Installing update...
2024-02-03T16:52:53.946570991Z [----] Cleaning up...
2024-02-03T16:52:53.946574312Z [----] Update complete, launching Steamcmd...
2024-02-03T16:52:54.734250350Z tid(25) burning pthread_key_t == 0 so we never use it
2024-02-03T16:52:54.734308316Z Redirecting stderr to '/home/steam/Steam/logs/stderr.txt'
2024-02-03T16:52:54.734315033Z Logging directory: '/home/steam/Steam/logs'
2024-02-03T16:52:54.734318610Z [  0%] Checking for available updates...
2024-02-03T16:52:54.734321971Z [----] Verifying installation...
2024-02-03T16:52:54.734325560Z Steam Console Client (c) Valve Corporation - version 1705108307
2024-02-03T16:52:54.734328924Z -- type 'quit' to exit --
2024-02-03T16:52:54.841975026Z Loading Steam API...OK
2024-02-03T16:52:54.841997570Z "@sSteamCmdForcePlatformType" = "windows"
2024-02-03T16:52:54.842333004Z 
2024-02-03T16:52:57.587659030Z Connecting anonymously to Steam Public...OK
2024-02-03T16:52:57.587706596Z Waiting for client config...OK
2024-02-03T16:53:06.674478187Z Waiting for user info...OK
2024-02-03T16:53:06.674497995Z  Update state (0x3) reconfiguring, progress: 0.00 (0 / 0)
2024-02-03T16:53:06.674502207Z  Update state (0x3) reconfiguring, progress: 0.00 (0 / 0)
2024-02-03T16:53:06.674513761Z  Update state (0x3) reconfiguring, progress: 0.00 (0 / 0)
2024-02-03T16:53:06.674517693Z Error! App '2278520' state is 0x202 after update job.
2024-02-03T16:53:06.805179393Z 2024-02-03 16:53:06,804 ERROR: steamcmd was unable to successfully initialize and update Enshrouded

It appears the steamcmd is unable to successfully initialize and update Enshrouded. Does anyone have insights or suggestions on how to resolve this issue?

Thank you for your assistance!

jsknnr commented 8 months ago

So the steamcmd error is an error that I built. Basically steamcmd had a non zero exit so I capture that and kill the container. The instances that I have seen the 0x202 error is generally related to steams inability to use the storage. Make sure there is enough storage and the permissions are correct and this will resolve.

pixeliner commented 8 months ago

I'm still a rookie with everything that has to do with Linux/Unix. So not entirely sure if that was the case, but in proxmox I'm using my own steam-dedicated template to start a quick VM with openSSH and docker preinstalled on a Ubuntu... with a preset user named "steam" which has an uid of 1000. When I recreated my Vm with another username, everything worked.

sandalle commented 5 months ago

I had this same issue.

steam:steam user:group setup (10000:10000) with 0755 permissions on /home/steam/ and all subfolders (including enshrouded/savegame/). /home/steam/ still has 260g of available space (and /tmp/ for /tmp/dumps/ has 16g).

So everything had enough space, or so I thought. Then I wondered where Docker is storing the persistent data. When I inspect the Docker volumes, I see this:

[
    {
        "CreatedAt": "2024-04-12T13:20:47-07:00",
        "Driver": "local",
        "Labels": {
            "com.docker.compose.project": "steam",
            "com.docker.compose.version": "1.29.2",
            "com.docker.compose.volume": "enshrouded-persistent-data"
        },
        "Mountpoint": "/var/lib/docker/volumes/steam_enshrouded-persistent-data/_data",
        "Name": "steam_enshrouded-persistent-data",
        "Options": null,
        "Scope": "local"
    }
]

That "Mountpoint" path ( "/var/lib/docker/volumes/steam_enshrouded-persistent-data/_data" ) has only 3.8g of free space! Adding more space to that volume (at least the necessary ~14g for the game, I gave it an additional 26g for patching and other files) fixed the error for me. Hope this helps the next person to run across this.