server freeze on startup

[mikeytrw]

Hi, I am running srcds on a red hat EL4 server,

The servers start and run fine 90% of the time, but every so often it will hang just after adding master servers for about 3 minutes and then says

"Connection to Steam servers successful."

Why does it connect to Steam servers? I dont want it to, can I disable this along with master server disable?

This wouldnt normally be a problem but these are on-demand servers which start automatically via a web interface. So the delay is really an issue.

I have tried disabling the master server connection as it isnt needed so I am confused as to what this problem might be.

Any Ideas?

[VRDriver4l]

mikeytrw Wrote:Hi, I am running srcds on a red hat EL4 server,

The servers start and run fine 90% of the time, but every so often it will hang just after adding master servers for about 3 minutes and then says

"Connection to Steam servers successful."

Why does it connect to Steam servers? I dont want it to, can I disable this along with master server disable?

This wouldnt normally be a problem but these are on-demand servers which start automatically via a web interface. So the delay is really an issue.

I have tried disabling the master server connection as it isnt needed so I am confused as to what this problem might be.

Any Ideas?

I would say it has somthing to do with steams servers responding slowly. Your server must be added to the steam master list I am almost positive there is no way to turn this off.

[Muppet]

mikeytrw Wrote:Hi, I am running srcds on a red hat EL4 server,

The servers start and run fine 90% of the time, but every so often it will hang just after adding master servers for about 3 minutes and then says

"Connection to Steam servers successful."

Why does it connect to Steam servers? I dont want it to, can I disable this along with master server disable?

This wouldnt normally be a problem but these are on-demand servers which start automatically via a web interface. So the delay is really an issue.

I have tried disabling the master server connection as it isnt needed so I am confused as to what this problem might be.

Any Ideas?

Try adding '-nomaster' to your start-up command parameters.

[mikeytrw]

Hi guys, thanks for the replies.

The master servers can be turned off by adding '-nomaser' to the command line.

The problem still occurs...

Annoyingly the problem still applies if I try running a server with sv_lan set to 1.

I also have VAC disabled.

the command line is:

srcds_run -game cstrike +map de_dust +maxplayers 10 -nomaster +port 27035 +tv_port 27037 +ip xx.xxx.xx.xx -insecure


Thanks,

[mikeytrw]

Hey, I beleive i have solved this issue. However it is not 100% certain.

If so I will post my solution...

[mikeytrw]

Hey Y'all.

For the sake of anyone else trying to sort this, i used netstat to examine the Steam servers that caused this delay, some do, some dont. I created firewall rules to block srcds from accessing these problematic servers...

result - servers now always start instantly with no-delay.
using iptables in linux...edit the /etc/sysconfig/iptables file and insert the following :

# Snub Steam
-A OUTPUT -p tcp -m tcp -d 68.142.88.34 --dport 27030:27038 -j REJECT --reject-with tcp-reset
# Snub Steam 2
-A OUTPUT -p tcp -m tcp -d 69.28.151.178 --dport 27030:27038 -j REJECT --reject-with tcp-reset

then either reboot machine or restart firewall/iptables

[warcrime]

mikeytrw Wrote:Hey Y'all.

For the sake of anyone else trying to sort this, i used netstat to examine the Steam servers that caused this delay, some do, some dont. I created firewall rules to block srcds from accessing these problematic servers...

result - servers now always start instantly with no-delay.
using iptables in linux...edit the /etc/sysconfig/iptables file and insert the following :

# Snub Steam
-A OUTPUT -p tcp -m tcp -d 68.142.88.34 --dport 27030:27038 -j REJECT --reject-with tcp-reset
# Snub Steam 2
-A OUTPUT -p tcp -m tcp -d 69.28.151.178 --dport 27030:27038 -j REJECT --reject-with tcp-reset

then either reboot machine or restart firewall/iptables

Thanks for this solution. It certainly helped me.

[mikeytrw]

Ok Theres another one people might need to add :

# Snub Steam 3
-A OUTPUT -p tcp -m tcp -d 72.165.61.190 --dport 27030:27038 -j REJECT --reject-with tcp-reset


Also, Please not the instructions above are for Red Hat, you might need to check how to set up iptables for your linux distro, Debian is different in that you use iptabes to insert these records and then iptables-save to save them. A quick google will give you any info you need.

Regards