Re: [hlds] [hlds_linux] Ok, I am totally drawing a blank here, on a HLDS install for HL1
I guess they never implemented the "UpToDateCheck" for the GoldSrc titles either. Not that anything GoldSrc gets updated very often anyway. But I opened a "suggestion" for that, on their GitHub yesterday anyway. > Ross Bemrose Fri, 16 Jan 2015 07:29:22 -0800 > > In my experience, its been this way since appid > 90 was first added to steamcmd. That was nearly > two years ago. > > While I don't do a lot with hlds (most of the > stuff I do is with srcds), it still irritates > me when I go to set up a CS 1.6 server and have > to install multiple times. > > I even went and added the warning to the SteamCMD > wiki page to warn other people that this would > happen. ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds
Re: [hlds] Steamcmd Outage?
Are they having issues with some DoS attack on those servers that happen to start with 208.? On Jan 16, 2015 1:26 PM, "Ross Bemrose" wrote: > While I haven't seen any comments in public about it, one of Valve's > engineers is working on the problem. We've had some email exchanges back > and forth which involved me sending steamcmd connection logs, steamcmd > command-line switches, the steamcmd runscript I use, plus ping and > traceroute from my NFOServers Chicago VPS to one of Valve's Steam servers. > > There's a new version of steamcmd out now. The timeout hasn't changed, > but now it will try 4 different servers before it gives up. > > For me, my current list has two 208 servers before the first 72 server, so > it waits for the first two to time out before actually connecting to the > third and checking for updates. > > > > On Fri, Jan 16, 2015 at 2:53 PM, Robert Paulson > wrote: > >> Why is the timeout on the connection so long? >> >> If the timeout was shorter and it didn't keep trying to connect to the >> first IP in config.vdf every time there would actually be a point to having >> multiple CM server entries. >> >> Can someone at Valve comment? >> >> On Fri, Jan 16, 2015 at 8:06 AM, N-Gon wrote: >> >>> Ross >>> When I follow your steams and run SteamCMD again it redownloaded that >>> config.vdf file >>> It updated TF2 just fine though. >>> I reedited that vdf file and saved a copy of the modified version. >>> Thanks! >>> >>> On Fri, Jan 16, 2015 at 10:18 AM, Ross Bemrose >>> wrote: >>> We were just discussing this over on hlds_linux. "Someone posted this workaround on csgo_servers yesterday: Hi, I have a temporary workaround for Steamcmd failing to connect/login. My server is in New Jersey, and has been unable to login to Steam for many days now. The following worked for me: 1. In your steamcmd directory, make a backup of config/config.vdf 2. Open config/config.vdf and find the IP addresses listed under InstallConfigStore -> Software -> Valve -> Steam -> CM 3. Remove the IP addresses starting with 208.* (note that the addresses are delimited by semicolons) 4. Re-run steamcmd and login Again, this is only temporary, and you should restore the backed-up copy when things are back to normal." On Fri, Jan 16, 2015 at 10:12 AM, Stephen Swires wrote: > Hi, > > I'm wondering if anyone else is affected by Steamcmd refusing to > login? Every time I try and login anonymously I get: > > Connecting anonymously to Steam Public...Login Failure: No Connection > FAILED with result code 3 > > I have tried two completely different servers in different data > centres (one in New York and the other in North Virginia). iptables have > been setup to allow the connections. It does appear from > http://steamstat.us/ that a good chunk of Steam servers are > unavailable in North America right now so could that explain this issue? > > Thanks. > > ___ > To unsubscribe, edit your list preferences, or view the list archives, > please visit: > https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds > > -- Ross Bemrose ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds >>> >>> ___ >>> To unsubscribe, edit your list preferences, or view the list archives, >>> please visit: >>> https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds >>> >>> >> >> ___ >> To unsubscribe, edit your list preferences, or view the list archives, >> please visit: >> https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds >> >> > > > -- > Ross Bemrose > > ___ > To unsubscribe, edit your list preferences, or view the list archives, > please visit: > https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds > > ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds
Re: [hlds] Steamcmd Outage?
While I haven't seen any comments in public about it, one of Valve's engineers is working on the problem. We've had some email exchanges back and forth which involved me sending steamcmd connection logs, steamcmd command-line switches, the steamcmd runscript I use, plus ping and traceroute from my NFOServers Chicago VPS to one of Valve's Steam servers. There's a new version of steamcmd out now. The timeout hasn't changed, but now it will try 4 different servers before it gives up. For me, my current list has two 208 servers before the first 72 server, so it waits for the first two to time out before actually connecting to the third and checking for updates. On Fri, Jan 16, 2015 at 2:53 PM, Robert Paulson wrote: > Why is the timeout on the connection so long? > > If the timeout was shorter and it didn't keep trying to connect to the > first IP in config.vdf every time there would actually be a point to having > multiple CM server entries. > > Can someone at Valve comment? > > On Fri, Jan 16, 2015 at 8:06 AM, N-Gon wrote: > >> Ross >> When I follow your steams and run SteamCMD again it redownloaded that >> config.vdf file >> It updated TF2 just fine though. >> I reedited that vdf file and saved a copy of the modified version. >> Thanks! >> >> On Fri, Jan 16, 2015 at 10:18 AM, Ross Bemrose >> wrote: >> >>> We were just discussing this over on hlds_linux. >>> >>> "Someone posted this workaround on csgo_servers yesterday: >>> >>> Hi, I have a temporary workaround for Steamcmd failing to connect/login. >>> My server is in New Jersey, and has been unable to login to Steam for many >>> days now. The following worked for me: >>> >>> 1. In your steamcmd directory, make a backup of config/config.vdf >>> 2. Open config/config.vdf and find the IP addresses listed under >>> InstallConfigStore -> Software -> Valve -> Steam -> CM >>> 3. Remove the IP addresses starting with 208.* (note that the addresses >>> are delimited by semicolons) >>> 4. Re-run steamcmd and login >>> >>> Again, this is only temporary, and you should restore the backed-up copy >>> when things are back to normal." >>> >>> On Fri, Jan 16, 2015 at 10:12 AM, Stephen Swires >>> wrote: >>> Hi, I'm wondering if anyone else is affected by Steamcmd refusing to login? Every time I try and login anonymously I get: Connecting anonymously to Steam Public...Login Failure: No Connection FAILED with result code 3 I have tried two completely different servers in different data centres (one in New York and the other in North Virginia). iptables have been setup to allow the connections. It does appear from http://steamstat.us/ that a good chunk of Steam servers are unavailable in North America right now so could that explain this issue? Thanks. ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds >>> >>> >>> -- >>> Ross Bemrose >>> >>> ___ >>> To unsubscribe, edit your list preferences, or view the list archives, >>> please visit: >>> https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds >>> >>> >> >> ___ >> To unsubscribe, edit your list preferences, or view the list archives, >> please visit: >> https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds >> >> > > ___ > To unsubscribe, edit your list preferences, or view the list archives, > please visit: > https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds > > -- Ross Bemrose ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds
Re: [hlds] Steamcmd Outage?
Why is the timeout on the connection so long? If the timeout was shorter and it didn't keep trying to connect to the first IP in config.vdf every time there would actually be a point to having multiple CM server entries. Can someone at Valve comment? On Fri, Jan 16, 2015 at 8:06 AM, N-Gon wrote: > Ross > When I follow your steams and run SteamCMD again it redownloaded that > config.vdf file > It updated TF2 just fine though. > I reedited that vdf file and saved a copy of the modified version. > Thanks! > > On Fri, Jan 16, 2015 at 10:18 AM, Ross Bemrose wrote: > >> We were just discussing this over on hlds_linux. >> >> "Someone posted this workaround on csgo_servers yesterday: >> >> Hi, I have a temporary workaround for Steamcmd failing to connect/login. >> My server is in New Jersey, and has been unable to login to Steam for many >> days now. The following worked for me: >> >> 1. In your steamcmd directory, make a backup of config/config.vdf >> 2. Open config/config.vdf and find the IP addresses listed under >> InstallConfigStore -> Software -> Valve -> Steam -> CM >> 3. Remove the IP addresses starting with 208.* (note that the addresses >> are delimited by semicolons) >> 4. Re-run steamcmd and login >> >> Again, this is only temporary, and you should restore the backed-up copy >> when things are back to normal." >> >> On Fri, Jan 16, 2015 at 10:12 AM, Stephen Swires wrote: >> >>> Hi, >>> >>> I'm wondering if anyone else is affected by Steamcmd refusing to login? >>> Every time I try and login anonymously I get: >>> >>> Connecting anonymously to Steam Public...Login Failure: No Connection >>> FAILED with result code 3 >>> >>> I have tried two completely different servers in different data centres >>> (one in New York and the other in North Virginia). iptables have been setup >>> to allow the connections. It does appear from http://steamstat.us/ that >>> a good chunk of Steam servers are unavailable in North America right now so >>> could that explain this issue? >>> >>> Thanks. >>> >>> ___ >>> To unsubscribe, edit your list preferences, or view the list archives, >>> please visit: >>> https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds >>> >>> >> >> >> -- >> Ross Bemrose >> >> ___ >> To unsubscribe, edit your list preferences, or view the list archives, >> please visit: >> https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds >> >> > > ___ > To unsubscribe, edit your list preferences, or view the list archives, > please visit: > https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds > > ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds
Re: [hlds] Steamcmd Outage?
Ross When I follow your steams and run SteamCMD again it redownloaded that config.vdf file It updated TF2 just fine though. I reedited that vdf file and saved a copy of the modified version. Thanks! On Fri, Jan 16, 2015 at 10:18 AM, Ross Bemrose wrote: > We were just discussing this over on hlds_linux. > > "Someone posted this workaround on csgo_servers yesterday: > > Hi, I have a temporary workaround for Steamcmd failing to connect/login. > My server is in New Jersey, and has been unable to login to Steam for many > days now. The following worked for me: > > 1. In your steamcmd directory, make a backup of config/config.vdf > 2. Open config/config.vdf and find the IP addresses listed under > InstallConfigStore -> Software -> Valve -> Steam -> CM > 3. Remove the IP addresses starting with 208.* (note that the addresses > are delimited by semicolons) > 4. Re-run steamcmd and login > > Again, this is only temporary, and you should restore the backed-up copy > when things are back to normal." > > On Fri, Jan 16, 2015 at 10:12 AM, Stephen Swires wrote: > >> Hi, >> >> I'm wondering if anyone else is affected by Steamcmd refusing to login? >> Every time I try and login anonymously I get: >> >> Connecting anonymously to Steam Public...Login Failure: No Connection >> FAILED with result code 3 >> >> I have tried two completely different servers in different data centres >> (one in New York and the other in North Virginia). iptables have been setup >> to allow the connections. It does appear from http://steamstat.us/ that >> a good chunk of Steam servers are unavailable in North America right now so >> could that explain this issue? >> >> Thanks. >> >> ___ >> To unsubscribe, edit your list preferences, or view the list archives, >> please visit: >> https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds >> >> > > > -- > Ross Bemrose > > ___ > To unsubscribe, edit your list preferences, or view the list archives, > please visit: > https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds > > ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds
Re: [hlds] Steamcmd Outage?
No issues here updating Windows2012 servers in Chicago and Seattle On Fri, Jan 16, 2015 at 10:18 AM, Ross Bemrose wrote: > We were just discussing this over on hlds_linux. > > "Someone posted this workaround on csgo_servers yesterday: > > Hi, I have a temporary workaround for Steamcmd failing to connect/login. > My server is in New Jersey, and has been unable to login to Steam for many > days now. The following worked for me: > > 1. In your steamcmd directory, make a backup of config/config.vdf > 2. Open config/config.vdf and find the IP addresses listed under > InstallConfigStore -> Software -> Valve -> Steam -> CM > 3. Remove the IP addresses starting with 208.* (note that the addresses > are delimited by semicolons) > 4. Re-run steamcmd and login > > Again, this is only temporary, and you should restore the backed-up copy > when things are back to normal." > > On Fri, Jan 16, 2015 at 10:12 AM, Stephen Swires wrote: > >> Hi, >> >> I'm wondering if anyone else is affected by Steamcmd refusing to login? >> Every time I try and login anonymously I get: >> >> Connecting anonymously to Steam Public...Login Failure: No Connection >> FAILED with result code 3 >> >> I have tried two completely different servers in different data centres >> (one in New York and the other in North Virginia). iptables have been setup >> to allow the connections. It does appear from http://steamstat.us/ that >> a good chunk of Steam servers are unavailable in North America right now so >> could that explain this issue? >> >> Thanks. >> >> ___ >> To unsubscribe, edit your list preferences, or view the list archives, >> please visit: >> https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds >> >> > > > -- > Ross Bemrose > > ___ > To unsubscribe, edit your list preferences, or view the list archives, > please visit: > https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds > > ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds
Re: [hlds] Steamcmd Outage?
We were just discussing this over on hlds_linux. "Someone posted this workaround on csgo_servers yesterday: Hi, I have a temporary workaround for Steamcmd failing to connect/login. My server is in New Jersey, and has been unable to login to Steam for many days now. The following worked for me: 1. In your steamcmd directory, make a backup of config/config.vdf 2. Open config/config.vdf and find the IP addresses listed under InstallConfigStore -> Software -> Valve -> Steam -> CM 3. Remove the IP addresses starting with 208.* (note that the addresses are delimited by semicolons) 4. Re-run steamcmd and login Again, this is only temporary, and you should restore the backed-up copy when things are back to normal." On Fri, Jan 16, 2015 at 10:12 AM, Stephen Swires wrote: > Hi, > > I'm wondering if anyone else is affected by Steamcmd refusing to login? > Every time I try and login anonymously I get: > > Connecting anonymously to Steam Public...Login Failure: No Connection > FAILED with result code 3 > > I have tried two completely different servers in different data centres > (one in New York and the other in North Virginia). iptables have been setup > to allow the connections. It does appear from http://steamstat.us/ that a > good chunk of Steam servers are unavailable in North America right now so > could that explain this issue? > > Thanks. > > ___ > To unsubscribe, edit your list preferences, or view the list archives, > please visit: > https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds > > -- Ross Bemrose ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds
Re: [hlds] Steamcmd Outage?
Someone posted this workaround on csgo_servers yesterday: Hi, I have a temporary workaround for Steamcmd failing to connect/login. My server is in New Jersey, and has been unable to login to Steam for many days now. The following worked for me: 1. In your steamcmd directory, make a backup of config/config.vdf 2. Open config/config.vdf and find the IP addresses listed under InstallConfigStore -> Software -> Valve -> Steam -> CM 3. Remove the IP addresses starting with 208.* (note that the addresses are delimited by semicolons) 4. Re-run steamcmd and login Again, this is only temporary, and you should restore the backed-up copy when things are back to normal. according to Ross: The path on Linux is likely ~/Steam/config/config.vdf regardless of where the actual steamcmd binary is installed. On 1/16/2015 10:12 AM, Stephen Swires wrote: Hi, I'm wondering if anyone else is affected by Steamcmd refusing to login? Every time I try and login anonymously I get: Connecting anonymously to Steam Public...Login Failure: No Connection FAILED with result code 3 I have tried two completely different servers in different data centres (one in New York and the other in North Virginia). iptables have been setup to allow the connections. It does appear from http://steamstat.us/ that a good chunk of Steam servers are unavailable in North America right now so could that explain this issue? Thanks. ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds
Re: [hlds] Steamcmd Outage?
You know I've been having this issue myself for the last few days on a new physical server I just set up running Windows 2008R2. On Fri, Jan 16, 2015 at 10:12 AM, Stephen Swires wrote: > Hi, > > I'm wondering if anyone else is affected by Steamcmd refusing to login? > Every time I try and login anonymously I get: > > Connecting anonymously to Steam Public...Login Failure: No Connection > FAILED with result code 3 > > I have tried two completely different servers in different data centres > (one in New York and the other in North Virginia). iptables have been setup > to allow the connections. It does appear from http://steamstat.us/ that a > good chunk of Steam servers are unavailable in North America right now so > could that explain this issue? > > Thanks. > > ___ > To unsubscribe, edit your list preferences, or view the list archives, > please visit: > https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds > > ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds
[hlds] Steamcmd Outage?
Hi, I'm wondering if anyone else is affected by Steamcmd refusing to login? Every time I try and login anonymously I get: Connecting anonymously to Steam Public...Login Failure: No Connection FAILED with result code 3 I have tried two completely different servers in different data centres (one in New York and the other in North Virginia). iptables have been setup to allow the connections. It does appear from http://steamstat.us/ that a good chunk of Steam servers are unavailable in North America right now so could that explain this issue? Thanks. ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds
