Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Server gets error when attempting to update #142

Open
M-archand opened this issue Dec 20, 2024 · 17 comments
Open

Server gets error when attempting to update #142

M-archand opened this issue Dec 20, 2024 · 17 comments
Assignees
Labels
upstream Bug in CS2 itself or another upstream component

Comments

@M-archand
Copy link

M-archand commented Dec 20, 2024

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:

Redirecting stderr to '/home/steam/Steam/logs/stderr.txt'
Logging directory: '/home/steam/Steam/logs'
[  0%] Checking for available updates...
[----] Verifying installation...
[  0%] Downloading update...
[  0%] Checking for available updates...
[----] Download complete.
[----] Extracting package...
[----] Installing update...
[----] Cleaning up...
[----] Update complete, launching Steamcmd...
steamcmd.sh[8]: Restarting steamcmd by request...
UpdateUI: skip show logoRedirecting stderr to '/home/steam/Steam/logs/stderr.txt'
Logging directory: '/home/steam/Steam/logs'
[  0%] Checking for available updates...
[----] Verifying installation...
UpdateUI: skip show logoSteam Console Client (c) Valve Corporation - version 1733269577
-- type 'quit' to exit --
Loading Steam API...OK
Connecting anonymously to Steam Public...OK
Waiting for client config...OK
Waiting for user info...OK
 Update state (0x3) reconfiguring, progress: 0.00 (0 / 0)
 Update state (0x3) reconfiguring, progress: 0.00 (0 / 0)
 Update state (0x3) reconfiguring, progress: 0.00 (0 / 0)
Error! App '730' state is 0x6 after update job.
@Cyberschorsch
Copy link

Removing the cs2-data/steamapps folder fixed it for me.

@joedwards32
Copy link
Owner

Try clearing out all cached steamapp data, as @Cyberschorsch suggests, or running the container with ENV STEAMAPPVALIDATE=1 set to force steam to revalidate the steamapps data.

@joedwards32 joedwards32 self-assigned this Dec 20, 2024
@joedwards32 joedwards32 added the upstream Bug in CS2 itself or another upstream component label Dec 20, 2024
@joedwards32
Copy link
Owner

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.

@vitordarela
Copy link

Hi, I'm facing the same problem, this only happens after the last 2 updates from Valve.

@julius-gmeinder
Copy link

Revalidating my steamapp data didn't help but clearing it out and performing a full game download again sorted things.

this worked for me. ty

@vitordarela
Copy link

vitordarela commented Dec 22, 2024

Revalidating my steamapp data didn't help but clearing it out and performing a full game download again sorted things.

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

@julius-gmeinder
Copy link

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
its not convenient for now, but better than nothing

@joedwards32
Copy link
Owner

joedwards32 commented Dec 22, 2024

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

@vitordarela
Copy link

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 that container entrypoint script

Thanks for the feedback 🙌🏻

@julius-gmeinder
Copy link

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

@M-archand
Copy link
Author

M-archand commented Jan 1, 2025

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#.

@vitordarela
Copy link

Hi.. @joedwards32 have some update from Valve's side?

@YESIHACK
Copy link

YESIHACK commented Jan 9, 2025

Any updates?

@M-archand
Copy link
Author

I'm now experiencing this same issue on the docker image 1zc/CS2-Pterodactyl as well.

@joedwards32
Copy link
Owner

Nothing from Valve yet. I sent my report to [email protected], if you want to add your voices.

@Barndo42
Copy link

Also having the same issue

@julius-gmeinder
Copy link

julius-gmeinder commented Jan 11, 2025

Revalidating my steamapp data didn't help but clearing it out and performing a full game download again sorted things.

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
upstream Bug in CS2 itself or another upstream component
Projects
None yet
Development

No branches or pull requests

7 participants