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

steamclient.so doesn't get automatically updated #44

Closed
Vauff opened this issue May 24, 2024 · 4 comments · Fixed by #46
Closed

steamclient.so doesn't get automatically updated #44

Vauff opened this issue May 24, 2024 · 4 comments · Fixed by #46
Assignees
Labels
bug Something isn't working high-priority

Comments

@Vauff
Copy link

Vauff commented May 24, 2024

/.steam/sdk64/steamclient.so seems to never get automatically updated (see modification date).
image

However /steamcmd/linux64/steamclient.so does.
image (1)

This has caused issues after todays CS2 update, because Valve seems to now be compiling against a newer steamclient.so.

[S_API] SteamAPI_Init(): Loaded '/home/container/.steam/sdk64/steamclient.so' OK.  (First tried local 'steamclient.so')
[S_API] SteamAPI_Init(): No SteamClient021
Failed to initialize Steamworks SDK for gameserver.  No SteamClient021
 0 Failed to initialize Steamworks SDK for gameserver.  No SteamClient021

Manually copying the updated lib from /steamcmd/linux64/ to /.steam/sdk64/ can solve the issue in the short term.

@LukasW1337
Copy link

LukasW1337 commented May 24, 2024

It does update if you run the install script, so hitting 'reinstall' under settings fixes the server.

But for the future. Would this be solved with a symlink?

@1zc 1zc self-assigned this May 24, 2024
@1zc 1zc added the bug Something isn't working label May 24, 2024
@1zc
Copy link
Owner

1zc commented May 24, 2024

But for the future. Would this be solved with a symlink?

Maybe, maybe not - I'll take a look as soon as I can

1zc added a commit that referenced this issue May 24, 2024
1zc added a commit that referenced this issue May 24, 2024
Update steamclient.so in entrypoint - #44
@1zc 1zc linked a pull request May 24, 2024 that will close this issue
@1zc 1zc removed a link to a pull request May 24, 2024
@1zc 1zc linked a pull request May 24, 2024 that will close this issue
@1zc
Copy link
Owner

1zc commented May 24, 2024

I've updated the docker image's entry point to ensure the steamclient.so binaries for sdk32/64 are updated after SteamCMD is done doing whatever it needs to do

I tried using a symlink, but it looks like this doesn't behave as expected - found my servers just failing to find the file at all.

This is now live on the dev Docker images:
image

I'll push to the main Docker image soon and close this issue when I do. No action should be required for any server using this egg, it should automatically pick up the new Docker image on start. Thanks for the report

@1zc 1zc closed this as completed in #46 May 24, 2024
1zc added a commit that referenced this issue May 24, 2024
Update steamclient.so in entrypoint - #44
@Truyn
Copy link

Truyn commented May 25, 2024

Big LIKE!!!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working high-priority
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants