[Closed] SteamCMD login fails, if i try it automaticly

[ReLaX]

Hi,

I have a very odd problem.

I'm trying to automate my steamcmd, but that wont work for me.

i have a script called update.txt that holds the following

Code:

login anonymous
force_install_dir 232330
app_update 232330
quit

I run it with this command

Code:

./steamcmd.sh +runscript .update.txt

and get the following error

Code:

login anonymous

Connecting anonymously to Steam Public...Login Failure: No Connection
Failed.
force_install_dir 232330
app_update 232330
ERROR! Failed to request AppInfo update, not online or not logged in to Steam.
quit

I i run this

Code:

./steamcmd.sh +login anonymous +force_install_dir 232330 +app_update 232330 +quit

Then it fails just like above.

BUT.. When i run it by my self.

Enter the ./steamcmd.sh and enter
login anonymous, it successes..

Code:

Connecting anonymously to Steam Public...Success.

I have googled the connection failed message, and tried a lot of solutions, but none worked yet.

Also i want to note. I used Ubuntu 12.04 x64 before, and the exact same thing happend there, as it now does at CentOS6

Information
Linux version: CentOS 6.2 x64
CPU: Intel Dual-Core E2160 (1 cpu with 2 cores)
RAM: 2048

[Ghost Assassin]

You should read the SteamCMD guide @ https://developer.valvesoftware.com/wiki/SteamCMD .

Code:

force_install_dir <path>

for example,
force_install_dir ./cs_go/

You set the force_install_dir to 232330 which is wrong. It should be a directory.

[ReLaX]

(09-05-2013, 12:07 PM)Ghost Assassin Wrote:  You should read the SteamCMD guide @ https://developer.valvesoftware.com/wiki/SteamCMD .

Code:

force_install_dir <path>

for example,
force_install_dir ./cs_go/

You set the force_install_dir to 232330 which is wrong. It should be a directory.

Hi,

Thanks for your reply.

I did try with full paths too /home/user/srcds/css1
That did not work either, but it did when i typed it in manually.

I did never got the problem solved.

We canceled our boxes at this provider, beceause we wanted it on another location.

Suprisely this works at our server hosting provider.. Cant tell why, but it does.


So this problem is closed, but im sorry to say that it is without any solution.