SRCDS Steam group


Server starts and immediately stops!
#1
Question 
After battling with the steam update tool. I downloaded a fresh install of CS:S. After the downloads completion and reading the how-to information located in the tutorial on this website, I attempted to start the server. I made several unsuccessful attempts to start the server.

Examples:

Quote:[halflife@halflife srcds_l]$ ./srcds_run
Auto detecting CPU
Using default binary.
Auto-restarting the server on crash
Fri Dec 17 07:48:35 CST 2004: Server Quit

[halflife@halflife srcds_l]$
Quote:[halflife@halflife srcds_l]$ ./srcds_run -game cstrike
Auto detecting CPU
Using default binary.
Auto-restarting the server on crash
Fri Dec 17 07:49:01 CST 2004: Server Quit

[halflife@halflife srcds_l]$
Quote:[halflife@halflife srcds_l]$ ./srcds_run -console -game cstrike +map de_dust +maxplayers 16
Auto detecting CPU
Using default binary.
Auto-restarting the server on crash
Fri Dec 17 08:10:36 CST 2004: Server Quit

[halflife@halflife srcds_l]$
When the "-autoupdate" flag is added on the command, it results in an unbreakable loop (can not control break out), which requires me to look up the pid and kill it manually.

I have run halflife servers for a long time. I am baffled at which direction I should go at this point.

Any offered ideas or suggestions are welcome.

Thanks,
No One Expects the Spanish Inquisition!
[Image: logo.gif]
Reply
#2
I've the same problem on a Debian Box ...
:/

XaT
Reply
#3
Got exactly the same on a FreeBSD box.....

Any suggestions ?
Reply
#4
And update ? :p

For me ... nothing ...

XaT
Reply
#5
Help.

XaT
Reply
#6
Ok, what cpu arch are you running, 686? 486?
post your
Code:
uname -mp
[Image: userbar_wow.jpg]
starting 9/24/2006 if your problem has been solved please edit your first post and add [solved] to the begining of the title. Thanks.
Reply
#7
Read/Write permissions maybe?

.. I dunno ..
Reply
#8
Could it have been related to the "+ip" problem earlier this week? Did you re-run hldsupdatetool since the last few updates?
Reply
#9
Here is an update on my issue. It is possible that the Source Dedicated Server will not run on older versions of glibc.

To check your version of use this command :
rpm -aq | grep glibc

Below is an example of the output:
Quote:$ rpm -aq |grep glibc
glibc-devel-2.2.5-44.legacy.3
glibc-2.2.5-44.legacy.3
glibc-kernheaders-2.4-7.16
glibc-debug-2.2.5-44.legacy.3
glibc-utils-2.2.5-44.legacy.3
glibc-common-2.2.5-44.legacy.3
compat-glibc-6.2-2.1.3.2
glibc-debug-static-2.2.5-44.legacy.3
glibc-profile-2.2.5-44.legacy.3

I do not know if its possible to make the server run without Glibc version 2.3

Since updated to 2.3 can be extremely difficult without a full reinstallation of Linux, I am ,of course, going to install a new/up2date version Linux on the server. I will post my results when it is completed. This may take me a few weeks because of the holiday.

-More to come.
No One Expects the Spanish Inquisition!
[Image: logo.gif]
Reply
#10
uname -mp : "i686 unknown"
rpm -aq | grep glibc : "bash: rpm: command not found"

XaT
Reply
#11
same prob in Debian here...
Reply
#12
there is a solution ?!

XaT Sad
Reply
#13
Same thing here, here's a clip, I tried defining the IP as suggested, and got the processors;

Quote:mario# ./srcds_run
Auto detecting CPU
Using default binary.
Auto-restarting the server on crash
Mon Dec 27 19:25:15 PST 2004: Server Quit
mario# ./srcds_run +ip 65.113.136.60
Auto detecting CPU
Using default binary.
Auto-restarting the server on crash
Mon Dec 27 19:26:06 PST 2004: Server Quit
mario# uname -mp
i386 i386
Reply
#14
same problem with Debian here...i did try all..
new glib / gdb etc...nothing works..
Reply
#15
Resolved with the latest Version
(Minimum) Glibc 2.3 x
installed from source not from deb package
Reply


Forum Jump:


Users browsing this thread: 3 Guest(s)