Segmentation fault with srcds_run

[404UserNotFound]

Server OS: Ubuntu 12.04, I think 64-bit
Processor: Intel i3
Ram: 8GB DDR3

Note: For further information about my dedicated server, please see http://www.ovh.com/ca/en/dedicated-servers/ks1.xml

Game(s): Team Fortress 2 - "Surf" server
Admin Mods: SourceMod (1.5.1 SourceMod, 1.10 Metamod, latest snapshots)

Start Up Command: See below
Full Install Command: This isn't the "install" line, but it's the one I use to start the server up. If the server folder was empty, this would of course turn itself into the "install" command.

Code:

#!/bin/bash
screen -A -m -S surf /home/usernotfound/gameservers/tf2/surf/srcds_run -console -game tf +ip 142.4.211.173 +hostport 27003 +maxplayers 24 -autoupdate -steam_dir /home/usernotfound/SteamCMD/ -steamcmd_script /home/usernotfound/scripts/tf2/surf/update.txt +map surf_utopia_v3

Here's what's happening. Right now, I run 3 Team Fortress 2 servers and a Minecraft Feed the Beast server for my Steam group on my dedicated server. I also offer hosting to three other people, all three of which only run 1 Team Fortress 2 server from their hosting.

There is still plenty of HDD space on the dedicated server, as well as plenty of memory left to run many more servers. So I decided to set up a "Surf" server in Team Fortress 2.

Everything starts up fine, but the issue arises whenever a player suicides. During the "Waiting for Players" period, players can suicide without issue.

Once the actual round starts, if someone suicides, the server crashes. I've kept PuTTY up (I use it to start the server up), and when the server crashes, this is what I see appear:

Quote:1270 Segmentation fault (core dumped) $HL_CMD

The "1270" part tends to change. I've seen "7750", etc. It also points out that the error is on line 324 of srcds_run. So I looked at that particular line, and line 324 says "$HL_CMD".

It also tells me to add "-debug" to my start up script to generate a debug log, so I did that....and on start up, I see something about an unknown "dbg" command, and the debug log never generates.

This issue does not occur on any of the other 6 TF2 servers running of my dedicated server, only this new surf server. All the TF2 servers run the exact same copy of SourceMod/Metamod (I keep SourceMod and Metamod updated religiously)

[404UserNotFound]

Anyone?

I just started up a Gmod server for a guy who I offer hosting to, and even that is Segmentation Fault'ing.

I've Googled around and it seems like nobody has came to a resolution on this, and any threads about this issue just go unanswered.

[404UserNotFound]

Ok so I may be onto something....well, the guy who I set up the Gmod server for may be onto something.

He tried switching the map on his gmod server to Construct, and it didn't seg fault on startup.

It seems that large maps cause servers to seg fault. In TF2, when a player suicides or dies, the server seg faults. With Gmod, it seg faults on startup. It seems certain games act differently.

More information on this required, and unfortunately I can't seem to figure out how to get my servers to accept the -debug parameter and generate a debug log.

[blaquicat]

You can try to start without the update features (to accept the -debug)

[DrFallen07]

You're update could of failed if you attached results from -debug we may be able to help more.

[404UserNotFound]

Well I'd like to restate that the issue seems to occurr with overly large maps, such as most TF2 surf maps, and some very large Garry's Mod maps.

When we switch to normal sized maps (such as ctf_2fort in TF2, or gm_construct in Garry's Mod), there's no segmentation faults whatsoever.

The updates haven't failed, they've always completed properly. If they did fail, I wouldn't be able to start the server up with any map. Because I can still start the server up with normal sized maps, that tells me the update(s) are/were successful.

[DrFallen07]

Hmm until we know more from the debug there isn't much more we can say. You could try re-downloading the server or running it without any mods and see what it does. There is nothing fundamentally wrong with your servers hardware.

[404UserNotFound]

(10-05-2013, 12:06 AM)DrFallen07 Wrote:  Hmm until we know more from the debug there isn't much more we can say. You could try re-downloading the server or running it without any mods and see what it does. There is nothing fundamentally wrong with your servers hardware.

Well I've tried the debug, it just always fails because of some missing dbg command.