Re: [hlds_linux] Linux Seg Fault

[Phoenix]

> Hi all, > > I have a linux server which keeps seg faulting on a certain map, > typically when the map gets full at 16 players. It seg faults about > every 15 minutes when full but it can stay up longer. I have a feeling > there is something this map uses that is causing the server to crash - > but the map should not be able to crash the server so it is likely there > is some sort of bug in the source ds. It happens with this map on > multiple servers, some which are not mine also - so I am fairly certain > it is nothing hardware related. This particular server is Fedora Core 1 > with latest updates. If someone from valve contacts me offlist I can > provide server login info if they need it. > > Basically, the server will crash and restart. > > Here is what the logs show (stripped steam ids): > > File l0301002.log: > > L 03/01/2005 - 01:05:28: "aVoN bARKSDALe<22><STEAM_0:1:xxx><Rebels>" > killed "STuNT<15><STEAM_0:1:xxx><Combine>" with "smg1_grenade" > L 03/01/2005 - 01:05:34: "Cl4mDiGGr<4><STEAM_0:0:xxx><Combine>" killed > "47<12><STEAM_0:0:xxx><Rebels>" with "rpg_missile" > L 03/01/2005 - 01:05:35: "yjp<23><STEAM_ID_PENDING><>" connected, > address "142.179.110.13:xxx" > L 03/01/2005 - 01:05:35: "47<12><STEAM_0:0:xxx><Rebels>" killed > "NeverKl3ver<17><STEAM_0:0:xxx><Combine>" with "combine_ball" > L 03/01/2005 - 01:05:36: "[DOJ]-Rambo-<10><STEAM_0:1:xxx><Rebels>" > killed "[DOJ]Klinger<11><STEAM_0:0:xxx><Combine>" with "smg1_grenade" > L 03/01/2005 - 01:05:49: "gunclapper.gunz<14><STEAM_0:0:xxx><Combine>" > say " yeah but it takes from the game if everyone on my team did it no > one would be fighting " > L 03/01/2005 - 01:05:51: "rich2113<19><STEAM_0:0:5749691><Combine>" > disconnected (reason "Disconnect by user.") > L 03/01/2005 - 01:05:51: "rich2113<19><STEAM_0:0:5749691><Unassigned>" > committed suicide with "smg1" > L 03/01/2005 - 01:05:55: "aVoN bARKSDALe<22><STEAM_0:1:xxx><Rebels>" > killed "mat20<3><STEAM_0:1:xxx><Combine>" with "smg1_grenade" > L 03/01/2005 - 01:05:58: "gunclapper.gunz<14><STEAM_0:0:xxx><Combine>" > say " [ > > The log file literally ends there. > > Next log file l0301003.log: > > L 03/01/2005 - 01:07:20: Log file started (file "logs/L0301003.log") > (game "/home/steam/hl2mp") (version "2301") > L 03/01/2005 - 01:07:20: Log file closed > > Next log file l0301004.log: > > L 03/01/2005 - 01:07:20: Log file started (file "logs/L0301004.log") > (game "/home/steam/hl2mp") (version "2301") > L 03/01/2005 - 01:07:20: Loading map "ctf_2fort_b7" > L 03/01/2005 - 01:07:20: server cvars start > L 03/01/2005 - 01:07:20: "sv_hl2mp_weapon_respawn_time" = "20" > L 03/01/2005 - 01:07:20: "sv_hl2mp_item_respawn_time" = "30" > L 03/01/2005 - 01:07:20: "mp_teamplay" = "1" > L 03/01/2005 - 01:07:20: "mp_fraglimit" = "1000" > L 03/01/2005 - 01:07:20: "mp_falldamage" = "0" > L 03/01/2005 - 01:07:20: "mp_weaponstay" = "0" > L 03/01/2005 - 01:07:20: "mp_forcerespawn" = "0" > > A core file is created, the one for this particular reset is core.7952 > > Made available here: > > http://hl2dm2.aurig.us/core.7952 > > This is about all I know, I've tried to dig a bit deeper but going into > unknown waters here :) > > Parsed the file with strings, output is here: > > http://hl2dm2.aurig.us/core.txt > > Also ran gdb on the core dump, here is the reason for the core file: > > Core was generated by `./srcds_i686 -console -game hl2mp +map > ctf_2fort_b7 +maxplayers 20 -autoupdate'. > Program terminated with signal 11, Segmentation fault. > #0  0x016ddbdd in ?? () > > > So basically, I'm stuck with an annoying crash and no idea whats causing > it. This was happening before and after the last steam update. Any > insight would be appreciated! > > -Dave My HL2MP Linux server is also crashing, for no reason. I never had a problem until the last update. It usually seems to happen on the new map steamlab (everytime I have witnessed it anyway). I am not running any plugins or anything. This is a straight default setup... except for maps. My log files end like yours, so I have not been able to figure out what is causing it.