SRCDS Steam group


[resolved] Could not complete initial ./steam execution
#1
Hello, i didn't found any solution or proper explaination of this problem, so i am starting a new thread.

What i did:

What i got (and still getting):

Code:
$ ./steam
Checking bootstrapper version ...

It hangs for 30 minutes already.

Just out of curiousity what it does, i looked at what it actually doing with strace:

Code:
$ pgrep steam
14687
$ strace -f -p 14687
Process 14687 attached
[ Process PID=14687 runs in 32 bit mode. ]
connect(3, {sa_family=AF_INET, sin_port=htons(27038), sin_addr=inet_addr("68.142.72.250")}, 16

Thats it. It hangs on establishing the connection to server 68.142.72.250 on port 27038 and this server is not letting it in - simply DROP'ing the connection, i guess.

After waiting while with strace attached, this server finally timed out:

Code:
[ Process PID=14687 runs in 32 bit mode. ]
connect(3, {sa_family=AF_INET, sin_port=htons(27038), sin_addr=inet_addr("68.142.72.250")}, 16) = -1 ETIMEDOUT (Connection timed out)
close(3)                                = 0
socket(PF_INET, SOCK_STREAM, IPPROTO_IP) = 3
connect(3, {sa_family=AF_INET, sin_port=htons(27038), sin_addr=inet_addr("68.142.88.34")}, 16

Now it tries another server. With same hanging result.

Any ideas?

Code:
BASIC INFO
Server OS: funtoo linux (rolling release, no version number)
Processor: Intel(R) Core(TM) i7-3520M CPU @ 2.90GHz
Ram: 8Gb
Game(s): No game was possible to access
Start Up Command: ./steam
Admin Mods: none, yet

Code:
$ gcc --version
gcc (Gentoo 4.6.3 p1.6, pie-0.5.2) 4.6.3

Code:
$ clang --version
clang version 3.3 (trunk)
Target: x86_64-pc-linux-gnu
Thread model: posix

Code:
$ ldd --version
ldd (GNU libc) 2.15

Code:
$ uname -a
Linux noteshi 3.7.1-tuxonice #20 SMP Wed Apr 24 17:58:02 MSK 2013 x86_64 Intel(R) Core(TM) i7-3520M CPU @ 2.90GHz GenuineIntel GNU/Linux
Reply
#2
UPD: i finally got something:
Code:
Getting version 50 of Steam HLDS Update Tool

And some activity on strace capture. I guess, you just have to wait, wait and wait, for a couple of hours with this update tool.
Reply
#3
After examining problem a little bit more, i've found that "steam" binary has hard-coded ip+ports:

Code:
207.173.177.11:27030
207.173.177.12:27030
69.28.151.178:27038
69.28.153.82:27038
68.142.88.34:27038
68.142.72.250:27038

And given that ip on which i got this "Getting version 50..etc" message was (for some reason) 208.64.200.189,
i added following rules to my firewall:

Code:
for v in 207.173.177.11 207.173.177.12 69.28.151.178 69.28.153.82 68.142.88.34 68.142.72.250; do iptables -t nat -A OUTPUT -d $v  -j DNAT --to-destination 208.64.200.189; done

And everything worked like a charm.
Reply
#4
Also, once you managed to run ./steam with it, you could delete those rules, it seems like successful ip was cached or somesuch.
Reply
#5
Wink 
(04-28-2013, 09:25 AM)iamtakingiteasy Wrote:  After examining problem a little bit more, i've found that "steam" binary has hard-coded ip+ports:

Code:
207.173.177.11:27030
207.173.177.12:27030
69.28.151.178:27038
69.28.153.82:27038
68.142.88.34:27038
68.142.72.250:27038

And given that ip on which i got this "Getting version 50..etc" message was (for some reason) 208.64.200.189,
i added following rules to my firewall:

Code:
for v in 207.173.177.11 207.173.177.12 69.28.151.178 69.28.153.82 68.142.88.34 68.142.72.250; do iptables -t nat -A OUTPUT -d $v  -j DNAT --to-destination 208.64.200.189; done

And everything worked like a charm.

Thanks a lot ! You're a life saver Shy Cool
Reply


Forum Jump:


Users browsing this thread: 2 Guest(s)