Today the steamcmd would just exit straight away without any output. I redownloaded the .tar.gz containing steam.sh etc and was able to run it and update my game. Then I tried again out of curiosity and it just returned straight away (exit code 0). I also still can't update servers in one of my other datacentres as connecting to the Steam auth server fails due to timeout (even with 'login anonymous').
The worst part is that I can't tell if these things fail with automated scripts since SteamCMD either hangs - could be updating - or returns 0 even if an update or authentication failed. Chris On 12 January 2013 13:22, Thiago Abreu <[email protected]> wrote: > Hello, we have four hosts running csgo servers and consequently steamcmd. > EVERYDAY we need to do some repair to the steamcmd, like removing > depotcache and base dir, kill stuck instances of steamcmd and at least > reinstall. > > Four hardware setups, four Centos 64, two link providers. > And the same problem. > > That's just me? > > _______________________________________________ > Csgo_servers mailing list > [email protected] > https://list.valvesoftware.com/cgi-bin/mailman/listinfo/csgo_servers >
_______________________________________________ Csgo_servers mailing list [email protected] https://list.valvesoftware.com/cgi-bin/mailman/listinfo/csgo_servers
