I am a developer from LGSM http://gameservermanagers.com and I have seen getting reports of issues with checking SteamCMD for updates (specifically users are reporting csgo).
This issue isn't directly related to SteamDB however there may be some expertise in this forum.
Currently the script queries SteamCMD using +app_info_print, grabs the buildid and compares the buildid in the appmanifest file. If there are differences the update is run. However currently SteamCMD is not returning the latest buildid meaning servers are not getting updates.
My only guess currently is that SteamCMD is caching the output of app_info_print and not checking remotely.
Is anyone aware of this issue or know of anyway to resolve this?
The command that returns the buildid is run as follows:
./steamcmd.sh +login anonymous +app_info_print "740" +app_info_print "740" +quit | grep -EA 1000 "^\s+\"branches\"$" | grep -EA 5 "^\s+\"public\"$" | grep -m 1 -EB 10 "^\s+}$" | grep -E "^\s+\"buildid\"\s+" | tr '[:blank:]"' ' ' | tr -s ' ' | cut -d\ -f3
Try messing with app_info_update command.
Thanks or the fast reply looking up the command it does the following
app_info_update : [0|1] : trigger app info update, optionally for update all
So I believe the command should be as follows.
./steamcmd.sh +login anonymous +app_info_update 1 +app_info_print "740" +app_info_print "740" +quit
app_info_update does not return anything to say its working or not so I will have to probably just add it in and hopfully it works
On a side note I was trying to get a complete list of all Commands and ConVars on SteamCMD. I was hoping that find * would work but it didnt. Is there a way to list all commands or am i just going to have to do find a, find b etc?
Thanks again for the pointer :)
Figured out the solution to this while messing around. steamcmd is caching the info. app_info_update is reading the cache anyway if you tell it not to. To fix this, delete the appcache folder where you have steamcmd installed before you check for new app info.
15:09 [kisak] Someone tell that thread that it's only appinfo.vdf in the appcache folder, not the entire folder that needs to be nuked.
I have found that only deleting appinfo.vdf to be unreliable. Quite frequently new updates are not detected unless the something else in the appcache is removed. Since I haven't diagnosed this beyond deleting the entire appcache I'm not sure what else is is interfering with a reliable check.
You are currently replying to another tree, would you like to make a top level comment? Reply
In order to reply to this thread,
you must login via Steam.