Not sure if this helps you but usually when it "hangs" when i try to log
in, i just ctrl+c aka kill it and start again. Works immediately.
-ics
Ammon Lauritzen kirjoitti:
I originally posted this question to the source sdk forum but got no response
other than a suggestion to try here :)
Some time yesterday, on one of our VM’s, steamcmd appeared to stop
authenticating. It worked flawlessly earlier in the week and no firewall or
other changes have been made. Upon further investigation, I determined that it
is trying to log in via TCP instead of UDP. These TCP login attempts take 2
minutes before failing, and they always fail.
After the host tries to log in to two different mirrors via TCP, it decides to
try UDP and inevitably works immediately. This process takes approximately 5
minutes and does not report the successful login - instead reporting an error.
But it syncs version numbers shortly after reporting a failure and if I attempt
to issue other commands, everything seems to work correctly.
I cannot reproduce this anywhere else. All other locations I’ve attempted from
just try UDP for their initial login and work from the start.
Is there any way to just tell steamcmd not to try TCP for logins? Or at the
very least, tell it to return to the behavior I’m observing everywhere else by
trying UDP first?
Ammon Lauritzen
_______________________________________________
To unsubscribe, edit your list preferences, or view the list archives, please
visit:
https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds_linux
_______________________________________________
To unsubscribe, edit your list preferences, or view the list archives, please
visit:
https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds_linux
