It's validate, not verify.
On 5/13/2013 7:54 PM, Jason wrote:
I have updated 4 of my 5 servers. With the 5th one, I keep getting
the following error -- and I know I have my install directory
correct.....it went through the update, got to 100% then continually
gives out the following error:
[ 0%] Checking for available updates...
[----] Verifying installation...
Steam Console Client (c) Valve Corporation
-- type 'quit' to exit --
Loading Steam3...OK.
Loading Steam2...OK.
Steam>@ShutdownOnFailedCommand 1
"@ShutdownOnFailedCommand" = "1"
Steam>@NoPromptForPassword 1
"@NoPromptForPassword" = "1"
Steam>login anonymous
Connecting anonymously to Steam Public...Success.
Steam>force_install_dir tf2
Steam>app_update 232250 verify
Initial App state (0x406) installed
App state (0x10506) reconfiguring, progress: 0.00 (0 / 0)
Error! App '232250' state is 0x606 after update job.
------------
I tried with and without "verify" and it's the same result. Also, I
am on Ubuntu 12.04 and don't know how to get past this.....any help
would be appreciated.
On Mon, May 13, 2013 at 6:57 PM, Albert Davis <davis.alb...@gmail.com
<mailto:davis.alb...@gmail.com>> wrote:
I am using the update option through my GPS
On Mon, May 13, 2013 at 6:50 PM, Ross Bemrose <rbemr...@gmail.com
<mailto:rbemr...@gmail.com>> wrote:
They don't anymore. Instead, they push out
cfg/mapcycle_default.txt
Having said that, a few config files are overwritten if you
use validate, specifically all the replay configs and
config_arena.cfg
You are updating through SteamCMD, RIGHT?
On 5/13/2013 6:46 PM, Albert Davis wrote:
WHY when you guys put an update out, you insist on causing
files such as MOTD/MAPCYCLE to default? I find that stupidly
annoying. It just happened again..... wtf?
On Mon, May 13, 2013 at 6:36 PM, Valentin G.
<nextra...@gmail.com <mailto:nextra...@gmail.com>> wrote:
It does happen. Updates take a while to distribute
through the CDN.
On Tue, May 14, 2013 at 12:12 AM, Peter Jerde
<peter-h...@jerde.net <mailto:peter-h...@jerde.net>> wrote:
Did today's different procedure somehow affect how
the update was pushed out to clients? It took me
several tries and restarting steam before my own
client got updated, and I'm getting reports of other
people unable to connect to our servers because their
clients are out of date.
I don't recall that ever happening before pre-steampipe.
- Peter
_______________________________________________
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
_______________________________________________
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
_______________________________________________
To unsubscribe, edit your list preferences, or view the list archives, please
visit:
https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds
