I agree - looks like mani - and definitely happens on a map change - I have had a full server tank on me at least 3 times now. Frustrating.
I am now cutting back the tk protection options - because I think it may have to do with those silly freeze/burn bombs -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Kingsley Foreman Sent: Sunday, July 02, 2006 7:33 PM To: hlds@list.valvesoftware.com Subject: Re: [hlds] srcds Crashing Woes it is mani doing it, if you remove that the servers are nice and stable. Kingsley ----- Original Message ----- From: "Paladin82" <[EMAIL PROTECTED]> To: <hlds@list.valvesoftware.com> Sent: Monday, July 03, 2006 7:41 AM Subject: RE: [hlds] srcds Crashing Woes > Here is my set up. > > Win2k3 > DoD:S > VAC, CVAR-X v1.0, SBS v1.1 > Mani Admin Plugin v1.2BetaN, MetaMod:Source v1.2.3 > > The only time I notice a crash since the update is when one of the new > maps loads right after the other. So for example if I load Colmar then > Jagd I crash on Jagd, if I load Jagd then Colmar I crash on Colmar, > now if I load Colmar then Anzio then Jagd or the opposite no problem. > > Also no errors in the logs and no I don't have access to the event logs. > > Very strange... > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] > On > Behalf Of Erling K. Sæterdal > Sent: Sunday, July 02, 2006 11:13 AM > To: hlds@list.valvesoftware.com > Subject: RE: [hlds] srcds Crashing Woes > > You should see the callstack without the symbol files, but they will > not show the source where it crashes ( but some asm ). > And srcds does not ship with symbol files, offcourse that could come > in handy at times:) But most of the time when srcds crashes its the > plugin that does something wrong ( Im my xp at least ). > > Want a Basic Admin Tool for your Source server? > http://forums.alliedmods.net/showthread.php?p=343034 > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Frazer > Sent: 2. juli 2006 17:38 > To: hlds@list.valvesoftware.com > Subject: RE: [hlds] srcds Crashing Woes > > Well, your point about access to the Event Log on rented servers is > very well taken and would prevents that approach, without the > cooperation of the hoster. > > Now, my vs.net debugging is rusty - so I stand to be corrected but: > do you not have to have the symbols file (.dpg or .dbg) accessible to > vs.net in order to obtain the call stack frames, etc? Some mods ship > with these files > - but not all. (Which is to be expected, since apps compiled with "debug" > are not quite as performant). I have not been able to locate a > symbols file for srcds.exe - I don't think one is shipped. > > The vast majority of exceptions are trappable in exception handling > blocks. > Exception wrapping is a bit of a coding pain, to be sure, but > eventually, as with all good coding practices, it become habit. Even > if the server Event Log is not the best choice - dropping a simple "It > was me that bombed your server" message in text file would go a long > way to helping mod users isolate issues. It's not a criticism - it's > just a suggestion. > > I don't think downloading, installing and figuring out VS.NET Express > is something that a lot of server admins have the time or patience to > work through. I don't think they should have to. > > greets, > Frazer > > > > > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Erling K. > Sæterdal > Sent: Sunday, July 02, 2006 11:12 AM > To: hlds@list.valvesoftware.com > Subject: RE: [hlds] srcds Crashing Woes > > hehe, > > Well I'm sure we can get better at adding try/catch I certainly can. > But adding any errors we find to event log would not be that helpful. > As those admins who rent servers are likely not to have access to the > event log ( Also I don't think admins are gonna check the event log > for errors regarding their servers, their gonna check the server logs > + admin tool logs ). So the challage is to get a meaning full error > into there. > > And the reason i replyed, to make my previus email more clear. "anyone" > should be able to find out what crashed their server ( as long as they > can download the crash files from the srcds root folder). > Simple download VS.net ( 2005 Express Edition is free, i assume it > comes with a debuger ). Open the dump file. Find the callstack window, > and there you should see what plugin last did something (You may have > to scroll a bit down). > Then simply contact the author of that tool, and give him the crash dump. > Offcourse a certain way of reproducing the crash is allways better in > my book ;) > > Want a Basic Admin Tool for your Source server? > http://forums.alliedmods.net/showthread.php?p=343034 > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Frazer > Sent: 2. juli 2006 13:27 > To: hlds@list.valvesoftware.com > Subject: RE: [hlds] srcds Crashing Woes > > Thanks for the tip on the crashdump - trying that now to see if it > isolates things a bit better. As to "predicting where the bugs are > gonna happen" - the whole point of wrapping ALL non-trivial blocks of > code in error-reporting exception handling is exactly that "we" don't > know where the bugs are :) > > > http://gearbox.oathill.com/cbb/blogs/dawgs_blawg/archive/2006/06/06/32 > .aspx > > > cheers, > > Frazer > > > > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Erling K. > Sæterdal > Sent: Saturday, July 01, 2006 10:32 PM > To: hlds@list.valvesoftware.com > Subject: RE: [hlds] srcds Crashing Woes > > If your running a windows server, then your srcds generates crash dumps. > That can be debugged in VS.net ( Off course your gonnna be limited in > the information that's shown without the pdb files) or sends to the > plugin developer. > I'm sure "we" could start adding a bite more error handlig code, the > problem is predicting where the bugs are gonna happen :) > > > Want a Basic Admin Tool for your Source server? > http://forums.alliedmods.net/showthread.php?p=343034 > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Frazer > Sent: 2. juli 2006 02:48 > To: hlds@list.valvesoftware.com > Subject: RE: [hlds] srcds Crashing Woes > > Thanks - already running on Windows Server 2003. I suspect the issue > is addons and suspect statsme, versus mani. > > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Kevin Ottalini > Sent: Saturday, July 01, 2006 8:55 PM > To: hlds@list.valvesoftware.com > Subject: Re: [hlds] srcds Crashing Woes > > Frazer, > As a baseline for you, I just moved both of my game servers over > to a datacenter to a Server2003 box and they have been totally crash > free since the update ... and as you might guess ...for the HL2DM > server I don't use any server addons at all. > > > > ----- Original Message ----- > From: "Frazer" > To: <hlds@list.valvesoftware.com> > Sent: Saturday, July 01, 2006 4:31 PM > Subject: [hlds] srcds Crashing Woes > > >> Since the new update, I have been experiencing more than the usual >> number of srcds crashes. I suspect an addon - possibly mani or >> statsme minimum (these are the only two I run). >> >> I was wondering if anyone else has been experiencing a recent >> increase in server crashes? >> >> Looking at my logs, this seems to happen on a map change. The game >> play log for the ending map closes correctly. The "loading map" log >> is created and closed correctly. The game play log for the next >> level is opened - but the server crashes before things get started. >> >> Also, I am interested in which version combinations of Mani and >> StatsMe minimum that folks are using who have reasonably stable >> servers, since the new upgrade. >> >> <rant> >> I am not a server guy, my thing is writing code. While I am grateful >> for the great addons and mods that are available, I am always puzzled >> that their developers don't wrap their code in decent exception >> handling and dump a simple message to the application or system log >> when their dll's are about to puke. It would be SO nice to look in >> the event log and see something >> like: "LameMod v2.3 unhandled My_Oopsie exception". Then, instead of >> the whole guessing and trial and error thing, we might be able to >> isolate the source of problems a hell of a lot quicker. Hell, if the >> developer is creative in their exception logging, it can even *gasp* >> help them find bugs!" >> >> Just sayin'... >> </rant> >> >> Frazer > > > _______________________________________________ > 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 > > > _______________________________________________ > 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 > > > _______________________________________________ > 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 > > > _______________________________________________ > 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 > > _______________________________________________ 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
