Server gets error when attempting to update #142
Assignees
Labels
upstream
Bug in CS2 itself or another upstream component
Comments
|
Removing the cs2-data/steamapps folder fixed it for me. |
|
Try clearing out all cached steamapp data, as @Cyberschorsch suggests, or running the container with ENV |
|
I can reproduce. Bug is upstream (i.e. Valve). Revalidating my steamapp data didn't help but clearing it out and performing a full game download again sorted things. |
|
Hi, I'm facing the same problem, this only happens after the last 2 updates from Valve. |
this worked for me. ty |
Yes, but in the next Valve's update you will need to do the same thing again.. it's not a "real fix", just a hotfix |
i know, uptime is not a big deal for me, i only use the server to practice with my team |
|
This is an upstream bug. I've submitted a bug report to Valve and would like to wait and see if they fix it before implementing any hacky work arounds in the container entrypoint script |
Thanks for the feedback 🙌🏻 |
|
just to add onto the issue: the vanilla server (after doing the hotfix) is working, but theres still an issue with metamod, cssharp or MatchZy and i have no idea why thats happening, theres no errors in console, the plugins seem to load correctly |
Happening to me as well. Can't use CS# without the server freezing. Vanilla works fine, My other servers that don't use this docker image don't have the issue while using the same version of metamod & CS#. |
|
Hi.. @joedwards32 have some update from Valve's side? |
|
Any updates? |
|
I'm now experiencing this same issue on the docker image 1zc/CS2-Pterodactyl as well. |
|
Nothing from Valve yet. I sent my report to [email protected], if you want to add your voices. |
|
Also having the same issue |
i just want to add that since deleting the steamapps folder and reinstalling the game once, my server has been running perfectly ever since, even troughout multiple updates. CS# was also broken after that patch, but they released a hotfix in v293, which solved my plugin related issues aswell. |
|
I'm not using any mods. Since clearing out steamapps my test server has also been behaving correctly across multiple CS2 updates. |
I figured my issue out. I added enough disk space to VM but did not partition it. It now works for me |
|
I think there may be no more to do here. I'll close this issue but will reopen if new evidence is presented. |
|
Hello @joedwards32 just so I understand correctly, we have no way to overcome this other than removing the entire volume and installing the game again, right? In other words, Valve's automatic update process no longer works and we have no way to bypass it? Seems like we are receiving HTTP 401 from the Upstream.. For what reasons would it be returning unauthorized for the update?
https://github.com/GameServerManagers/LinuxGSM-Docs/blob/master/steamcmd/errors.md |
Automatic update has been working on my dev environment after an initial destruction of the volume and re-download. Subsequent updates have been applied successfully. Is this not the case for you?
Potentially anonymous SteamCMD usage is not allowed with the updates depot any more? |
|
Hello, |
|
Understood. I'll test in my environment again and keep this issue open. |
Closed
|
Commenting here to say "me too". I installed the container fresh a day ago and ran into this issue. |
|
|
|
Seems like the problem isn't solved completely. This is the output when I try to update the app myself: Then it decides that it did install completely until you verify the client again. I cannot get rid of this error particularly. It started happening after I deleted the Might be a network related issue, but it started happening only recently. I can post the txt log if you request. |
|
GG @jithatsonei |
Closed
|
Reopened due to #153 |
|
Hmm odd, not sure whats triggering that one, can we enable verbose logging by using the |
|
I'll add a |
|
#154 now in |
|
Log from #153 |
|
Given the 401 errors are we looking at Valve blocking anonymous access to parts of the depots? |
Are we able to pass any authdata to the container in that case? |
|
There was support for steamcmd auth in v1 of this container but I took it away when anonymous access started to work. I can look at bringing it back. |
I will check by hand if adding auth negates the issue, since when I'm logging in steamcmd anonymously, this issue persists even outside the container. I'll clear that out asap. |
|
Seems like logging in didn't work. I even got a new error: Logs still show that some CDNs return 401: P.S. This is steamcmd running from a container for an outdated CS2 client. |
|
If the error occurs outside of the container, we may be back to trying to get Valve to accept an upstream bug. |
That may be something network-related from their side, as spamming the |
|
I could add some error handling with a retry loop |
Tried to do that myself but failed to capture an error that returns from the command. If it's possible, it would save my server cluster, at least. This should be an env-option (as a recovery measure) since this behavior is not expected most of the time. |
joedwards32
added a commit
that referenced
this issue
Feb 19, 2025
|
Fix that works for me in PR #155 Now available in |
Closed
I can check that when the next update for CS2 will roll, and it seems that it will be somewhere during this week. I'll write back. |
|
I can confirm that my server has now updated and is working |
|
I ran into this issue as well last week, but didn't have the latest image at that time. I pulled the latest image and re-built the container. I'll leave a comment if everything is fine after the next CS2 update. Considering I have a lot of workshop maps already downloaded, it'll be the perfect test. |
|
Just had a new update here that worked on retry, thanks for getting this fix in! |
|
Latest update also worked for me on retry. Going to mark this as closed. Will reopen if contrary evidence emerges. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
After updating to build 3.0.1 I have been getting an error during update when restarting the server, resulting in the client being out of date:
The text was updated successfully, but these errors were encountered: