The same crashes happened when that empty item name bug started happening.

Here's a crash dump in case it helps somebody:
#0  0x00998410 in __kernel_vsyscall ()
#1  0x00b2ad20 in raise () from /lib/libc.so.6
#2  0x00b2c631 in abort () from /lib/libc.so.6
#3  0x00b62e6b in __libc_message () from /lib/libc.so.6
#4  0x00b6ab16 in _int_free () from /lib/libc.so.6
#5  0x00b6e070 in free () from /lib/libc.so.6
#6  0x0059fbcf in CStdMemAlloc::Free () from ./bin/libtier0.so
#7  0x04369711 in GCSDK::CRecordVar::Cleanup ()
   from /home/srcds/tf2server/orangebox/tf/bin/server.so
#8  0x03ba9b17 in CPersistentItem::~CPersistentItem$delete ()
   from /home/srcds/tf2server/orangebox/tf/bin/server.so
#9  0x04366da3 in
GCSDK::CSharedObjectTypeCache::~CSharedObjectTypeCache$delete
    () from /home/srcds/tf2server/orangebox/tf/bin/server.so
#10 0x043646d4 in GCSDK::CSharedObjectCache::~CSharedObjectCache$delete ()
   from /home/srcds/tf2server/orangebox/tf/bin/server.so
#11 0x043437a1 in GCSDK::CGCClient::RemoveSOCache ()
   from /home/srcds/tf2server/orangebox/tf/bin/server.so
#12 0x0434846b in GCSDK::CGCSOCacheUnsubscribedJob::BYieldingRunGCJob ()
   from /home/srcds/tf2server/orangebox/tf/bin/server.so
#13 0x03ba13da in GCSDK::CGCClientJob::BYieldingRunJobFromMsg ()
   from /home/srcds/tf2server/orangebox/tf/bin/server.so
#14 0x04349ee5 in GCSDK::CJob::BRunProxy ()
   from /home/srcds/tf2server/orangebox/tf/bin/server.so
#15 0x0043be27 in Internal_Coroutine_Continue () from ./bin/libvstdlib.so
#16 0x0043c7f8 in Coroutine_Continue () from ./bin/libvstdlib.so
#17 0x04349cfa in GCSDK::CJob::Continue ()
   from /home/srcds/tf2server/orangebox/tf/bin/server.so
#18 0x0434ea07 in GCSDK::CJobMgr::BLaunchJobFromNetworkMsg ()
   from /home/srcds/tf2server/orangebox/tf/bin/server.so
#19 0x0434ed69 in GCSDK::CJobMgr::BRouteMsgToJob ()
   from /home/srcds/tf2server/orangebox/tf/bin/server.so
#20 0x043429ff in GCSDK::CGCClient::OnGCMessageAvailable ()
   from /home/srcds/tf2server/orangebox/tf/bin/server.so
#21 0x0434482e in CCallback<GCSDK::CGCClient, GCMessageAvailable_t,
false>::Run
    () from /home/srcds/tf2server/orangebox/tf/bin/server.so
#22 0x00117a1f in Steam_BGetCallback () from ./bin/libsteam_api.so
#23 0x00117fde in Steam_BGetCallback () from ./bin/libsteam_api.so
#24 0x00118019 in Steam_BGetCallback () from ./bin/libsteam_api.so
#25 0x0011a0a5 in Steam_RunCallbacks () from ./bin/libsteam_api.so
#26 0x0011b71d in SteamGameServer_RunCallbacks () from ./bin/libsteam_api.so
#27 0x067ce8df in CSteam3Server::RunFrame ()
   from /home/srcds/tf2server/orangebox/bin/engine.so
#28 0x067b5585 in SV_Frame ()
   from /home/srcds/tf2server/orangebox/bin/engine.so

-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of Shizzle Nizzle
Sent: Monday, September 13, 2010 7:08 PM
To: [email protected]
Subject: [hlds] Massive TF2 Server Crashing

I am unsure whether it is something recent that valve has done with their
'stats collecting' and whatnot. but it is quite obvious it is something
related to the steam server checking valve does. It has happened several
times this week where all our servers immediately crash together. Servers on
different boxes.. and locations. And after checking with several other major
servers.. such as sourceop, topnotchclan, lotus servers, alpha omega etc
they seem to be experiencing the exact same crash time as I have witnessed,
when I saw their servers emptied out at the same time and reboot. It seemed
at least for today's crash it happened at approximately 8:35 PM Central
Standard Time, be amazed and you will most likely see your server rebooted
at this time as well :P. But it keeps happening every couple days according
to my connection logs, in some cases it happens a couple times in one day.
Which you can find here

/orangebox/bin/logs

and here

/orangebox/logs

the only thing i get from it is..

09/13/10 20:35:44 : Failed to load Steam Service (3)
09/13/10 20:35:44 : BOpenService failed (1060)
09/13/10 20:35:44 : ServiceStart: failed to start (183)


Now I also host DOD/CSS Servers and this mass crash did not occur on those
servers at all, they have not experienced a single crash resulting in that
error above.
_______________________________________________
To unsubscribe, edit your list preferences, or view the list archives,
please visit:
http://list.valvesoftware.com/mailman/listinfo/hlds


_______________________________________________
To unsubscribe, edit your list preferences, or view the list archives, please 
visit:
http://list.valvesoftware.com/mailman/listinfo/hlds

Reply via email to