starred/LinuxGSM

Fork 0

mirror of https://github.com/GameServerManagers/LinuxGSM.git synced 2026-04-25 22:25:59 +03:00

[GH-ISSUE #356] SteamCMD not always getting updates #300

New issue

Closed

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

kerem commented

2026-02-27 02:00:43 +03:00

Owner

Originally created by @dgibbs64 on GitHub (May 1, 2015).
Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/356

Im getting reports that update checker is not always working because SteamCMD is not returning the latest version details. Will need to find out why this is

Originally created by @dgibbs64 on GitHub (May 1, 2015). Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/356 Im getting reports that update checker is not always working because SteamCMD is not returning the latest version details. Will need to find out why this is

kerem

2026-02-27 02:00:43 +03:00

closed this issue
added the
info: steamcmd
label

kerem commented

2026-02-27 02:00:43 +03:00

Author

Owner

@ImChiip commented on GitHub (May 2, 2015):

same here

Steam Console Client (c) Valve Corporation
-- type 'quit' to exit --
Loading Steam API...OK.

Connecting anonymously to Steam Public...Logged in OK
Waiting for license info...OK
Update state (0x5) validating, progress: 12,49 (1275158569 / 10211222143)
Update state (0x61) downloading, progress: 0,06 (5920830 / 10211222143)
Error! App '740' state is 0x402 after update job.
Warning! SteamCMD did not complete the download, retrying: Attempt 2:

@ImChiip commented on GitHub (May 2, 2015): same here Steam Console Client (c) Valve Corporation -- type 'quit' to exit -- Loading Steam API...OK. Connecting anonymously to Steam Public...Logged in OK Waiting for license info...OK Update state (0x5) validating, progress: 12,49 (1275158569 / 10211222143) Update state (0x61) downloading, progress: 0,06 (5920830 / 10211222143) Error! App '740' state is 0x402 after update job. Warning! SteamCMD did not complete the download, retrying: Attempt 2:

kerem commented

2026-02-27 02:00:43 +03:00

Author

Owner

@jackemerson commented on GitHub (May 3, 2015):

Think that's a different issue, Chip. Specifically this issue is that the update check doesn't detect that there's a new version rather than failing once its begun, I believe.

Bar doing it manually is there a force update command? Would be useful to have if it doesn't yet exist.

@jackemerson commented on GitHub (May 3, 2015): Think that's a different issue, Chip. Specifically this issue is that the update check doesn't detect that there's a new version rather than failing once its begun, I believe. Bar doing it manually is there a force update command? Would be useful to have if it doesn't yet exist.

kerem commented

2026-02-27 02:00:43 +03:00

Author

Owner

@dgibbs64 commented on GitHub (May 3, 2015):

Yeah I may have to implement a force update to bypass the check if people are getting the issue

@dgibbs64 commented on GitHub (May 3, 2015): Yeah I may have to implement a force update to bypass the check if people are getting the issue

kerem commented

2026-02-27 02:00:43 +03:00

Author

Owner

@dgibbs64 commented on GitHub (May 6, 2015):

http://steamcommunity.com/groups/linuxgsm/discussions/0/620712999966267752/

@dgibbs64 commented on GitHub (May 6, 2015): http://steamcommunity.com/groups/linuxgsm/discussions/0/620712999966267752/

kerem commented

2026-02-27 02:00:43 +03:00

Author

Owner

@dgibbs64 commented on GitHub (May 9, 2015):

I belive this is now resolved with a recent update github.com/dgibbs64/linuxgsm@078a5ccbd8

@dgibbs64 commented on GitHub (May 9, 2015): I belive this is now resolved with a recent update https://github.com/dgibbs64/linuxgsm/commit/078a5ccbd8659ddd0506287feac7d0e77aa600a4

kerem commented

2026-02-27 02:00:43 +03:00

Author

Owner

@lock[bot] commented on GitHub (Jul 19, 2018):

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

@lock[bot] commented on GitHub (Jul 19, 2018): This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.