SRCDS Steam group


L4D2 Segmentation Fault Before Server Load
#1
Hi guys, I'm having an issue with getting a L4D2 server to load up, pretty much after i execute the ./srcds_run, the server prints

Console initialized
Segmentation Fault

Has this ever appeared before, if so what is the best way to go around and fix this issue?

BASIC INFO
Server OS: Ubuntu Server 64bit 9.04 (jaunty)
Processor: Intel Core 2 Quad Q9400 @ 2.66GHz
Ram:8GB
Game(s): L4D2 (l4d1 working)
Start Up Command: ./srcds_run -autoupdate -console -game left4dead2 +hostport 27017 +clientport 27080 +exec l4d2server.cfg +map c1m1_hotel
Admin Mods: NONE (2 fresh l4d2 installs tried)

Thanks for any help!

Regards
Rob
Reply
#2
apt-get update && apt-get upgrade
Later ./steam blababa -verify_all

To make sure you have latest working packages and verify all gamedata.

Also try starting the server only with ./scrds_run -game left4dead2 -ip youripnumber -port 27017

Not needed Parameters:
-console +hostport 27017 +clientport 27080 +map c1m1_hotel
Reply
#3
(01-15-2010, 09:48 PM)Terrorkarotte Wrote:  apt-get update && apt-get upgrade
Later ./steam blababa -verify_all

To make sure you have latest working packages and verify all gamedata.

Also try starting the server only with ./scrds_run -game left4dead2 -ip youripnumber -port 27017

Not needed Parameters:
-console +hostport 27017 +clientport 27080 +map c1m1_hotel

I just updated the packaged and upgraded, also verified all game data - the server is still reporting a segmentation fault immediatly.

Regards
Rob
Reply
#4
what is you startcommand? Still using
./srcds_run -autoupdate -console -game left4dead2 +hostport 27017 +clientport 27080 +exec l4d2server.cfg +map c1m1_hotel
?
I run: ./srcds_run -game left4dead2 -ip 123671276 -port 21010+## -fork 8 +exec server_fork_##.cfg
if I start forked servers and this for standalone:
./srcds_run -game left4dead2 -ip 21421412421 -port 21010
Thats all
Reply
#5
(01-15-2010, 10:27 PM)Terrorkarotte Wrote:  what is you startcommand? Still using
./srcds_run -autoupdate -console -game left4dead2 +hostport 27017 +clientport 27080 +exec l4d2server.cfg +map c1m1_hotel
?
I run: ./srcds_run -game left4dead2 -ip 123671276 -port 21010+## -fork 8 +exec server_fork_##.cfg
if I start forked servers and this for standalone:
./srcds_run -game left4dead2 -ip 21421412421 -port 21010
Thats all

A forked server would be more than on server running on one install correct?
I'm only trying to run 1 L4D2 server, the commandline im using is just the basic one you gave me above (./srcds_run -game left4dead2 -ip -port)
Reply
#6
Forked server share the memory.and each instance eats up normal cpu. What happens if you start with ./srcds_run -game left4dead2 ?
Reply
#7
It still causes the segmentation fault immediatly
Reply
#8
actually, i cannot believe i missed it before - when running the update & upgrade it returns this after a while:

dpkg was interrupted, you must manually run "sudo dpkg --configure -a" to correct the problem

So i run that and it returns:

Processing triggers for initramsf-tools ...
update-initramfs: Generating /boot/initrd.img-2.6.28.10-slabpreemptcore2

gzip; stdout: no space left on device
update-initramfs: failed for /boot/initrd.img-2.6.28.10-slabpreemptcore2
dpkg: subprocess post-installation script returned error exit status 1

There is atleast 60gb left on the HDD so i do not know why it says no space left on device

Regards
Rob
Reply
#9
A guess: Like most linux Distros ubuntu created several partitions like swap etc. The Partition which is used for the /boot diretory is full. Delete all not used kernel and try again.
Reply
#10
This usually associates with memory access.

As it is hard to tell from the given info, I got no good suggestion for you at the moment, but I would like to have you try to start L4D2 as su -, and see how it goes.
A less annoying signature... (link)
Reply
#11
Running servers as root is a bad idea. You can do it for testing ok but not for actually running.

df -h /boot

Will give you the usage of the used partition.
Reply
#12
Size: 92mb Used 69mb Avail 18mb
for the df -h /boot

I have tried running it under the actual root account before, doesn't make a difference
Reply
#13
(01-16-2010, 06:17 PM)Terrorkarotte Wrote:  Running servers as root is a bad idea.

Just for troubleshooting of course. Unless he has fixed the issue, he isn't hosting any SRCDS instance. Cool
A less annoying signature... (link)
Reply
#14
Have you treid deleting not used kernels to free some space? and re run sudo dpkg --configure -a
Reply
#15
(01-16-2010, 11:30 PM)Terrorkarotte Wrote:  Have you treid deleting not used kernels to free some space? and re run sudo dpkg --configure -a

I was not involved the the compiling of the new kernel for the box, how do you tell which ones are not being used?
Reply


Forum Jump:


Users browsing this thread: 2 Guest(s)