Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Server dont update #119

Closed
1 task done
arvan3844 opened this issue Dec 11, 2024 · 9 comments
Closed
1 task done

Server dont update #119

arvan3844 opened this issue Dec 11, 2024 · 9 comments
Labels
bug 🐞 Something isn't working question❓ Further information is requested

Comments

@arvan3844
Copy link

arvan3844 commented Dec 11, 2024

Is there an existing issue for this?

  • I have searched the existing issues

Question

Hello,

i'm having problems with the update of the server. we got a new patch to a new build today, but the server dont update itself.
server logs says all ok:
2024-12-11 12:15:52.739 supervisord: enshrouded-updater enshrouded-server: started
2024-12-11 12:15:52.768 supervisord: enshrouded-updater INFO - enshrouded-updater complete

Server files are outdated (dated 07.12.2024)

Can't also use any of the commands, like
docker compose exec enshrouded supervisorctl start enshrouded-force-update
error is "no configuration file provided: not found". Running server on proxmox in a container.

So i used supervirsorctl directly in the console from the container and it worked, but it does not update the server files.
log: supervisord: enshrouded-updater Error! App '2278520' state is 0x6 after update job.

steamcmd says this to error 0x6:
Reason | No connection to content servers
Reason 2 | Received 401 (Unauthorized) HTTP response for depot 11

Solution was the same as last time: delete both files appmanifest_2278520.acf and appmanifest_228980.acf in steamapps folder.

PUID and PGID are both correcly to 4711.

@arvan3844 arvan3844 added the question❓ Further information is requested label Dec 11, 2024
@kabixi000
Copy link

As a temporary workaround, I was able to resolve the issue by removing the following manifest files inside the container and restarting the server.

rm /opt/enshrouded/server/steamapps/appmanifest_228980.acf
rm /opt/enshrouded/server/steamapps/appmanifest_2278520.acf

@cp-fabian-pittroff
Copy link
Member

Hello there,

seems like there went something wrong with the last steam update job.

Can't also use any of the commands, like
docker compose exec enshrouded supervisorctl start enshrouded-force-update
error is "no configuration file provided: not found". Running server on proxmox in a container.

docker compose exec ... can only work if you are in the same directory as the docker-compose.yaml. The error indicates, that it can't find the file. You can also run docker exec <name_of_container|default enshrouded> supervisor ....

So i used supervirsorctl directly in the console from the container and it worked, but it does not update the server files. log: supervisord: enshrouded-updater Error! App '2278520' state is 0x6 after update job.

steamcmd says this to error 0x6: Reason | No connection to content servers Reason 2 | Received 401 (Unauthorized) HTTP response for depot 11

Solution was the same as last time: delete both files appmanifest_2278520.acf and appmanifest_228980.acf in steamapps folder.

Thats odd, don't know why it helps to delete the steam appmanifest, but I will include the cleanup of those files in the force update command.

@arvan3844
Copy link
Author

arvan3844 commented Dec 11, 2024

Though atm the enshrouded-updater don't really update the client if a new build exist, so the server can't be found on the server browser ingame, because its outdated (version mismatch). Because it still says it's up2date. But i can't find any logs about why, it should try to update itself, since it only said INFO - enshrouded-updater complete but should have find the new build. In the past, this just works.

@andrewgdunn
Copy link

I was going to post an issue that I suspected to be networking but may be this as well. Just to communicate that networking is debugged:

root@0bc1628fd5f1:/usr/local/etc/enshrouded# ss -tupln
Netid                   State                    Recv-Q                   Send-Q                                     Local Address:Port                                        Peer Address:Port                   Process                   
udp                     UNCONN                   0                        0                                                0.0.0.0:15637                                            0.0.0.0:*                                                
udp                     UNCONN                   0                        0                                                0.0.0.0:48079                                            0.0.0.0:*                                                
tcp                     LISTEN                   0                        0                                              127.0.0.1:39273                                            0.0.0.0:*    
[dungeon@storr ~]$ podman ps | grep enshrouded
0bc1628fd5f1  docker.io/mornedhels/enshrouded-server:latest  /usr/local/etc/en...  31 minutes ago  Up 31 minutes        0.0.0.0:15637->15637/udp                                   enshrouded

My players have been unable to see the instance for several days (started last week) and I wasn't able to test a local connection until today. I'm unable to connect to it locally. I assume this is because of a client/server mismatch?

@andrewgdunn
Copy link

Can confirm that after doing what @kabixi000 recommended above the server becomes available:

[dungeon@storr ~]podman unshare rm enshrouded/server/steamapps/appmanifest_22*
[dungeon@storr ~]$ systemctl --user restart container-enshrouded.service

@cp-fabian-pittroff
Copy link
Member

Could someone check if the following line can be found in the logs “Download of Enshrouded server failed - aborting update”?

The updater should not set a new version, if the update itself fails.

@cp-fabian-pittroff
Copy link
Member

I got an enshrouded update today for both of my running instances. Both are still up and running and I can connect to them. So the updater script seems only to have a problem, when the steamcli errors out. The problem, I can't really reproduce that locally.

For now I will add the workaround into the force-update command. I'll have to test a little bit, but will provide an update soon™️

2024-12-11 14:00:15.305 supervisord: enshrouded-updater Success! App '2278520' fully installed.
2024-12-11 14:00:15.446 supervisord: enshrouded-updater DEBUG - [53487] - [setCurrentVersion]: 16705286

@cp-fabian-pittroff
Copy link
Member

Well on my develop environment I got the same error. Not sure why though. But the steamworks common redis had a betakey flag in it. After removing and updating the betakey flag was gone.

old manifest (228980)

{
        "appid"         "228980"
        "Universe"              "1"
        "name"          "appid_228980"
        "StateFlags"            "6"
        "installdir"            "Steamworks Shared"
        "LastUpdated"           "1723292042"
        "LastPlayed"            "0"
        "SizeOnDisk"            "0"
        "StagingSize"           "0"
        "buildid"               "14615842"
        "LastOwner"             "0"
        "UpdateResult"          "0"
        "BytesToDownload"               "0"
        "BytesDownloaded"               "0"
        "BytesToStage"          "0"
        "BytesStaged"           "0"
        "TargetBuildID"         "0"
        "AutoUpdateBehavior"            "0"
        "AllowOtherDownloadsWhileRunning"               "0"
        "ScheduledAutoUpdate"           "0"
        "FullValidateAfterNextUpdate"           "1"
        "InstalledDepots"
        {
        }
        "UserConfig"
        {
                "BetaKey"               "public"
        }
        "MountedConfig"
        {
                "BetaKey"               "public"
        }
}

new manifest (228980)

{
        "appid"         "228980"
        "Universe"              "1"
        "name"          "Steamworks Common Redistributables"
        "StateFlags"            "2"
        "installdir"            "Steamworks Shared"
        "LastUpdated"           "0"
        "LastPlayed"            "0"
        "SizeOnDisk"            "0"
        "StagingSize"           "0"
        "buildid"               "0"
        "LastOwner"             "0"
        "UpdateResult"          "0"
        "BytesToDownload"               "0"
        "BytesDownloaded"               "0"
        "BytesToStage"          "0"
        "BytesStaged"           "0"
        "TargetBuildID"         "0"
        "AutoUpdateBehavior"            "0"
        "AllowOtherDownloadsWhileRunning"               "0"
        "ScheduledAutoUpdate"           "0"
        "InstalledDepots"
        {
        }
        "UserConfig"
        {
        }
        "MountedConfig"
        {
        }
}

@cp-fabian-pittroff
Copy link
Member

Released with version 1.4.1. Thanks for reporting and solving the issue 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug 🐞 Something isn't working question❓ Further information is requested
Projects
None yet
Development

No branches or pull requests

4 participants