Just looked into console to find the reason of too long starting after crash
(with -autoupdate)
Looks like SteamCMD can't connect to the network, on both Linux Win I see
Steamlogin anonymous
Connecting anonymously to Steam Public...Failed to receive license info.
Success.
And timeout for the
Took me a few tries last night as well
On Wed, Oct 30, 2013 at 12:05 PM, Denis Eliseev lisee...@yandex.ru wrote:
Just looked into console to find the reason of too long starting after
crash (with -autoupdate)
Looks like SteamCMD can't connect to the network, on both Linux Win I see
Attempting a clean install of tf2 servers using steamcmd
I'm using install/update scripts from another dedicated server i own so
i know they're working, but on this machine which is a clone of the
other as far as hardware/software is concerned i receive the following
message when attempting
I'm pretty sure this is related to the Steam server maintenance. I was
getting that yesterday and today it's hit-or-miss with whether or not it
will connect. If it didn't, however, it would still go through (albeit this
was on Linux). What does your command line and steamcmd script(s) look like?
It doesn't matter which command you are using, when the Conten-Servers are
down, you cannot update.
I'm lucky to have a masterserver, which is syncs all other servers. If we
get an update, the master synchronizes all slaves.
It's also under windows possible to do this job automated.
I think it
5 matches
Mail list logo
