L4D Server (Floating point exception) *SOLVED*

[fampat]

*UDPATE*
For everyone who encountered this problem:
The problem is solved due to the help of the reaplys in the following thread:
http://forums.srcds.com/viewtopic/8765


Hi Folks, iam tryin to get the L4D Demo Server to work, but ive encountered a serius problem from where i dont know what to do.

Its a Suse 9 Server and iam also running a TF2 server on this machine without any problems, but as soon as i start the l4d demo server with the following line:

/home/l4d/srcds/l4d_demo/srcds_run -console -game left4dead +ip "[Server IP]" -port 27500 -maxplayers 4 +map l4d_dem_hospital01_apartment.bsp

Ill get this:
Auto detecting CPU
Using SSE2 Optimised binary.
Enabling debug mode
Server will auto-restart if there is a crash.
/home/l4d/srcds/l4d_demo/srcds_run: line 361: 3415 Floating point exception(core dumped) $HL_CMD
email debug.log to linux@valvesoftware.com
Sun Nov 9 12:57:30 CET 2008: Server restart in 10 seconds
Sun Nov 9 12:57:37 CET 2008: Server Quit

Thanks for any helpful input

[realchamp]

Don't use the .bsp behind your map. Only l4d_dem_hospital01_apartment

[fampat]

realchamp Wrote:Don't use the .bsp behind your map. Only l4d_dem_hospital01_apartment

Thanks for the tip, tryed it:
~/srcds/l4d_demo> /home/l4d/srcds/l4d_demo/srcds_run -console -game left4dead +ip "[Server IP]" -port 27500 -maxplayers 4 +map l4d_dem_hospital01_apartment

Response:
Auto detecting CPU
Using SSE2 Optimised binary.
Server will auto-restart if there is a crash.
/home/l4d/srcds/l4d_demo/srcds_run: line 361: 7204 Floating point exception$HL_CMD
Add "-debug" to the /home/l4d/srcds/l4d_demo/srcds_run command line to generate a debug.log to help with solving this problem
Sun Nov 9 13:08:02 CET 2008: Server restart in 10 seconds
Sun Nov 9 13:08:05 CET 2008: Server Quit

[realchamp]

Try run HldsUpdaterTool.exe with -verify_all in the end.

[fampat]

realchamp Wrote:Try run HldsUpdaterTool.exe with -verify_all in the end.

Hmm i ran:
/home/l4d/hldsupdatetool.bin -verify_all

and recieved this:
PDV 1.5.1 - Glen Wiley <gwiley@ieee.org>


Cant be correct huh?
Tryed to start again after this.. but nothing changed.. i also deleted all und "reinstalled" the l4d demo (v5) but doesnt changed anything either.

[realchamp]

You have to use the entire line as you first of all downloaded the server.

/home/l4d/hldsupdatetool.bin -command update -game left4dead -dir . -verify_all

[fampat]

realchamp Wrote:You have to use the entire line as you first of all downloaded the server.

/home/l4d/hldsupdatetool.bin -command update -game left4dead -dir . -verify_all

Ran it:
/home/l4d/hldsupdatetool.bin -command update -game left4dead -dir . -verify_all

Result:
/home/l4d/hldsupdatetool.bin: invalid option -- c
/home/l4d/hldsupdatetool.bin: invalid option -- o
/home/l4d/hldsupdatetool.bin: invalid option -- m
/home/l4d/hldsupdatetool.bin: invalid option -- m
/home/l4d/hldsupdatetool.bin: invalid option -- a
/home/l4d/hldsupdatetool.bin: invalid option -- n
/home/l4d/hldsupdatetool.bin: invalid option -- d
/home/l4d/hldsupdatetool.bin: invalid option -- g
/home/l4d/hldsupdatetool.bin: invalid option -- a
/home/l4d/hldsupdatetool.bin: invalid option -- m
/home/l4d/hldsupdatetool.bin: invalid option -- e
/home/l4d/hldsupdatetool.bin: invalid option -- d
/home/l4d/hldsupdatetool.bin: invalid option -- i
/home/l4d/hldsupdatetool.bin: invalid option -- r
PDV 1.5.1 - Glen Wiley <gwiley@ieee.org>

Maybe ill better giveup.. its not meant to run on my server.. dunno.. TF2 works great..

UDPATE:
The following command just worked:
/home/l4d/steam -command update -game left4dead -dir . -verify_all
Checking bootstrapper version ...
Updating Installation
Checking/Installing 'left4dead demo base' version 5


Checking/Installing 'left4dead demo dedicated content' version 0


HLDS installation up to date


But still the floating error on start...

[fampat]

Problem is solved (See opening post)

[TheMG]

I'm having this problem (also with Fedora FC5) but the solution in the OP does not work for me, the server still crashes with a floating point exception.

Is there anything else you may have updated other than glibc and glibc-common?