starred/LinuxGSM

Fork 0

mirror of https://github.com/GameServerManagers/LinuxGSM.git synced 2026-04-25 06:05:57 +03:00

[GH-ISSUE #4588] [Bug]: Valheim in update loop #2856

New issue

Open

opened 2026-02-27 03:05:50 +03:00 by kerem · 6 comments

kerem commented

2026-02-27 03:05:50 +03:00

Owner

Originally created by @Maltavius on GitHub (Jun 10, 2024).
Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/4588

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

Originally created by @Maltavius on GitHub (Jun 10, 2024). Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/4588 ### 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 ```shell 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

kerem added the

labels

2026-02-27 03:05:50 +03:00

kerem commented

2026-02-27 03:05:50 +03:00

Author

Owner

@JarnoB commented on GitHub (Jun 10, 2024):

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.

@JarnoB commented on GitHub (Jun 10, 2024): Can confirm I'm running into the same issue, ever since they [released the Mac port today](https://steamcommunity.com/app/892970/eventcomments/4336483638881773583). 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](https://steamdb.info/patchnotes/14660887/) and the [Dedicated server](https://steamdb.info/patchnotes/14660893/) files. This seems to have been restored with [BuildID 14662278](https://steamdb.info/patchnotes/14662278/). Less than an hour later, they did [one more update](https://steamdb.info/patchnotes/14662813/) to the Dedicated Server, adding the ManifestID. You can find a full list of updates [here](https://steamdb.info/app/896660/patchnotes/) 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.

kerem commented

2026-02-27 03:05:50 +03:00

Author

Owner

@somethingknew commented on GitHub (Jun 11, 2024):

Same happens to me but for CS2.

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

@somethingknew commented on GitHub (Jun 11, 2024): Same happens to me but for CS2. Edit: Seems it resolved itself after the latest CS2 update. 🤷‍♂️

kerem commented

2026-02-27 03:05:50 +03:00

Author

Owner

@dgibbs64 commented on GitHub (Jun 12, 2024):

Maybe valve broke somthing in steamcmd

@dgibbs64 commented on GitHub (Jun 12, 2024): Maybe valve broke somthing in steamcmd

kerem commented

2026-02-27 03:05:50 +03:00

Author

Owner

@h3o66 commented on GitHub (Sep 29, 2024):

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.

@h3o66 commented on GitHub (Sep 29, 2024): 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.

kerem commented

2026-02-27 03:05:50 +03:00

Author

Owner

@jaumebecks commented on GitHub (Dec 3, 2024):

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

[ FAIL ] Updating vhserver: Checking remote build: SteamCMD

So I guess this is still ongoing

@jaumebecks commented on GitHub (Dec 3, 2024): I'm currently receiving this when running `./vhserver update`: > [ FAIL ] Updating vhserver: Checking remote build: SteamCMD So I guess this is still ongoing

kerem commented

2026-02-27 03:05:51 +03:00

Author

Owner

@historical-theology commented on GitHub (Dec 9, 2024):

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.

@historical-theology commented on GitHub (Dec 9, 2024): > 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.

kerem referenced this issue

2026-02-27 03:56:09 +03:00

[PR #3035] [MERGED] feat(alert): add mailgun api eu support #3880