starred/LinuxGSM

Fork 0

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

[GH-ISSUE #3140] [BUG] [Garry's Mod] Update command fails #2210

New issue

Closed

opened 2026-02-27 03:01:32 +03:00 by kerem · 6 comments

kerem commented

2026-02-27 03:01:32 +03:00

Owner

Originally created by @peter-r-g on GitHub (Dec 22, 2020).
Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/3140

Basic info

Distro: [Ubuntu 20.04]
Game: [Garry's Mod]
Command: [Update]
LinuxGSM version: [v20.6.2]

Further Information

Changing the branch within the configuration file seems to break the update command. If there is no branch set, the update command works fine. Setting it to anything else (even if a valid depot) will always result in the same error. For some reason if you use the validate command then it all works fine and it seems to update to the new depot.

Looking at the script log I found this:

Dec 22 18:26:33.509 gmodserver: UPDATE: INFO: Using anonymous Steam login
Dec 22 18:26:35.101 gmodserver: UPDATE: PASS: Checking local build
Dec 22 18:26:41.076 gmodserver: UPDATE: FATAL: Checking remote build
Dec 22 18:26:41.081 gmodserver: UPDATE: INFO: LinuxGSM version: v20.6.2
Dec 22 18:26:41.082 gmodserver: UPDATE: FATAL: core_exit.sh exiting with code: 1

To Reproduce

Steps to reproduce the behaviour:

Set branch to "x86-64" (64 bit beta to dedicated server, https://steamdb.info/app/4020/depots/?branch=x86-64)
Use update command (./gmodserver update)
See error "[ FAIL ] Updating gmodserver: Checking remote build: SteamCMD"

Expected behaviour

A success message and that my files are updated to the x86-64 branch of the dedicated server.

Originally created by @peter-r-g on GitHub (Dec 22, 2020). Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/3140 ## Basic info * **Distro:** [Ubuntu 20.04] * **Game:** [Garry's Mod] * **Command:** [Update] * **LinuxGSM version:** [v20.6.2] ## Further Information Changing the branch within the configuration file seems to break the update command. If there is no branch set, the update command works fine. Setting it to anything else (even if a valid depot) will always result in the same error. For some reason if you use the validate command then it all works fine and it seems to update to the new depot. Looking at the script log I found this: ``` Dec 22 18:26:33.509 gmodserver: UPDATE: INFO: Using anonymous Steam login Dec 22 18:26:35.101 gmodserver: UPDATE: PASS: Checking local build Dec 22 18:26:41.076 gmodserver: UPDATE: FATAL: Checking remote build Dec 22 18:26:41.081 gmodserver: UPDATE: INFO: LinuxGSM version: v20.6.2 Dec 22 18:26:41.082 gmodserver: UPDATE: FATAL: core_exit.sh exiting with code: 1 ``` ## To Reproduce Steps to reproduce the behaviour: 1. Set branch to "x86-64" (64 bit beta to dedicated server, https://steamdb.info/app/4020/depots/?branch=x86-64) 2. Use update command (./gmodserver update) 3. See error "[ FAIL ] Updating gmodserver: Checking remote build: SteamCMD" ## Expected behaviour A success message and that my files are updated to the x86-64 branch of the dedicated server.

kerem

2026-02-27 03:01:32 +03:00

closed this issue
added the
info: steamcmd

command: update
labels

kerem commented

2026-02-27 03:01:32 +03:00

Author

Owner

@h3o66 commented on GitHub (Dec 22, 2020):

should be proably fixed with #3139

@h3o66 commented on GitHub (Dec 22, 2020): should be proably fixed with #3139

kerem commented

2026-02-27 03:01:33 +03:00

Author

Owner

@peter-r-g commented on GitHub (Dec 25, 2020):

should be proably fixed with #3139

Can confirm that change fixes this issue

@peter-r-g commented on GitHub (Dec 25, 2020): > > > should be proably fixed with #3139 Can confirm that change fixes this issue

kerem commented

2026-02-27 03:01:33 +03:00

Author

Owner

@h3o66 commented on GitHub (Dec 25, 2020):

should be proably fixed with #3139

Can confirm that change fixes this issue

thanks for confirming this

@h3o66 commented on GitHub (Dec 25, 2020): > > should be proably fixed with #3139 > > Can confirm that change fixes this issue thanks for confirming this

kerem commented

2026-02-27 03:01:33 +03:00

Author

Owner

@sarahsturgeon commented on GitHub (Jan 25, 2021):

Also can confirm, applied that change locally and it works.
However, still getting the error even after updating lgsm. Are we still waiting on a deployment?

@sarahsturgeon commented on GitHub (Jan 25, 2021): Also can confirm, applied that change locally and it works. However, still getting the error even after updating lgsm. Are we still waiting on a deployment?

kerem commented

2026-02-27 03:01:33 +03:00

Author

Owner

@h3o66 commented on GitHub (Jan 25, 2021):

Also can confirm, applied that change locally and it works.
However, still getting the error even after updating lgsm. Are we still waiting on a deployment?

yes, this will be done with the next release, what is currently in testing.
If you want to test it, you need to set it to the new release branch.
For further info please join the Discord

@h3o66 commented on GitHub (Jan 25, 2021): > Also can confirm, applied that change locally and it works. > However, still getting the error even after updating lgsm. Are we still waiting on a deployment? yes, this will be done with the next release, what is currently in testing. If you want to test it, you need to set it to the new release branch. For further info please join the Discord

kerem commented

2026-02-27 03:01:33 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Jan 29, 2022):

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@github-actions[bot] commented on GitHub (Jan 29, 2022): This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

kerem referenced this issue

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

[PR #2359] [MERGED] feat(newserver): Soldier of Fortune 2: Gold Edition #3611