-
-
Notifications
You must be signed in to change notification settings - Fork 77
SteamCMD error with new container using sourcemod tag #25
Comments
The SDL warning is normal and happens always, it's not the cause of the issue. Make sure that you have enough space on disk, it sounds like it's running out during the download. |
There's definitely enough space, my docker's storage is using a 512 gig SSD
array that's only at about 5% used.
Later today I can do a fresh attempt on a new container and capture all of
the logs for you, and then I can also run steamCMD interactively and
capture the error there too.
Would it be better to email you the logs or post them in the GitLab issue?
Thanks for looking into this! I'm running the container on a Synology NAS,
ds1019+. It was working fine for weeks but then level changes took a long
time and I saw an error about CMD updating in the log, that's when I purged
the container and rebuilt from scratch and after several attempts I still
can't get it to work.
Jeffrey
…On Sat, Jun 20, 2020, 6:12 AM Walentin L. ***@***.***> wrote:
The SDL warning is normal and happens always, it's not the cause of the
issue. Make sure that you have enough space on disk, it sounds like it's
running out during the download.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#25 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AEOSCDSZNYT3UNG32AT32GDRXSYUHANCNFSM4NWLSTBA>
.
|
You can post them here, so the next person that has this problem will know how to fix it :). |
Added a "sleep 3600" to the end of /home/steam/csgo-dedicated/entry.sh so the container would not exit. Logs from a fresh container start (newest on top) 2020-06-20 20:52:22 stdout /home/steam/csgo-dedicated/entry.sh: 4: /home/steam/csgo-dedicated/entry.sh: /home/steam/csgo-dedicated/srcds_run: not found It's not a disk space issue: steam@cm2network-csgo1:~/csgo-dedicated$ df -h /home/steam/csgo-dedicated/ I see a new image was pushed 7 hours ago, I will try that one and see if I get the same result. |
Similar problem with the new container, also getting the "state is 0x602" error. I'll poke around with it more later. 2020-06-20 21:33:01 stdout bash: /home/steam/csgo-dedicated/srcds_run: No such file or directory |
I figured it out. I had some files mounted into the container as read only: /home/steam/csgo-dedicated/csgo/cfg/gamemode_casual.cfg Apparently when I flushed the container and it tried to re-download game files, it couldn't complete the app update because those files couldn't be overwritten since they were mapped as read only. It was this line that helped me figure it out: 2020-06-20 21:33:01 stdout sed: cannot rename /home/steam/csgo-dedicated/csgo/cfg/sedUaCIde: Device or resource busy |
When deploying a new container, steamcmd is failing to update the csgo dedicated server. After downloading the ~25GB dedicated server files, steamcmd throws an error:
"SteamCMD - App state is 0x602 after update job"
Appid 740 files are still in the temp download directory.
When running steamcmd manually, I experienced:
"Loading Steam API...Warning: failed to init SDL thread priority manager: SDL not found"
I believe this is caused by the absence of a 32bit SDL library, possibly now required by steam after a recent update?
I encountered these issues when I noticed a very long delay changing maps on the server, and after pulling the container fresh, the server will not start at all.
The text was updated successfully, but these errors were encountered: