[Bug]: Valheim in update loop

[Maltavius]

User story

I want my Valheim server to be updated so I have a cron-job that updates it

Game

Valheim

Linux distro

Other

Command

command: update

Further information

The job started informing me today on Discord that the Valheim server was down, and then up, and then down, and then up.

Running the update myself I realised that the service reports the remote version to be newer but then it fails to update although the script reports "Success!"

Linux GameServers 5.15.126-1-pve #1 SMP PVE 5.15.126-1 (2023-10-03T17:24Z) x86_64 GNU/Linux

Relevant log output

vhserver@GameServers:~$ ./vhserver update
[  OK  ] Updating vhserver: Checking for update: SteamCMD

Update available
* Local build: 14662278
* Remote build: 14662813
* Branch: public
https://steamdb.info/app/896660/

[ WARN ] Updating vhserver: vhserver will be restarted
[  OK  ] Stopping vhserver: Graceful: CTRL+c: 4: OK
[ START ] Updating vhserver: SteamCMD
Branch: public
WARNING: setlocale('en_US.UTF-8') failed, using locale: 'C'. International characters may not work.
Redirecting stderr to '/home/vhserver/.local/share/Steam/logs/stderr.txt'
Logging directory: '/home/vhserver/.local/share/Steam/logs'
[  0%] Checking for available updates...
[----] Verifying installation...
UpdateUI: skip show logoSteam Console Client (c) Valve Corporation - version 1716584438
-- type 'quit' to exit --
Loading Steam API...OK

Connecting anonymously to Steam Public...OK
Waiting for client config...OK
Waiting for user info...OK
Success! App '896660' already up to date.
Complete! Updating vhserver: SteamCMD
[  OK  ] Starting vhserver: WoxNet Valheim Server
[  OK  ] Updating vhserver: Sending Discord alert
vhserver@GameServers:~$

Steps to reproduce

./vhserver update

[JarnoB]

Can confirm I'm running into the same issue, ever since they released the Mac port today. I did note in the comments of the post about the Mac port that they made a mistake and temporary nuked both the Linux version and the Dedicated server files.

This seems to have been restored with BuildID 14662278. Less than an hour later, they did one more update to the Dedicated Server, adding the ManifestID. You can find a full list of updates here

Right now, when I check for an update with ./vhserver update, it keeps thinking that the server is still on the version/BuildID that restored most of the files, before restoring the ManifestID:

* Local build: 14662278
* Remote build: 14662813

I suspect the error is caused be the removing/restoring of these files, Hope this helps!

Edit; I can confirm I worked around the issues by manually editing ~/serverfiles/steamapps/appmanifest_896660.acf. Open that file in a text editor and change the line with the buildid to:

"buildid" "14662813"

Save the file and restart the server. That should fix the issue.

[somethingknew]

Same happens to me but for CS2.

Edit: Seems it resolved itself after the latest CS2 update. 🤷‍♂️

[dgibbs64]

Maybe valve broke somthing in steamcmd

[h3o66]

Does someone get still this issue or was this only tempory with steamcmd ? With a update on my side I did not see this now.

[jaumebecks]

I'm currently receiving this when running ./vhserver update:

[ FAIL ] Updating vhserver: Checking remote build: SteamCMD

So I guess this is still ongoing

[historical-theology]

I'm currently receiving this when running ./vhserver update:

[ FAIL ] Updating vhserver: Checking remote build: SteamCMD

So I guess this is still ongoing

I just opened a new issue thread about this here: https://github.com/GameServerManagers/LinuxGSM/issues/4713

Have you found a resolution? If so, please let us know there. Thanks.