Re: [hlds] Two Issues: Odd Crash at Mapchange? And, is it OK to run SRCDS on Win 2003 x64?

2009-01-04 Thread Cc2iscooL
I use serverdoc myself, and it does support queries to the server. I've also heard that Firedaemon works too, but I haven't tried it myself. On Sun, Jan 4, 2009 at 5:04 AM, Jeff Sugar jeffsu...@gmail.com wrote: Upon finally going to change it (my server only just now emptied out), I found

Re: [hlds] Two Issues: Odd Crash at Mapchange? And, is it OK to run SRCDS on Win 2003 x64?

2009-01-04 Thread Jeff Sugar
Upon finally going to change it (my server only just now emptied out), I found that the 30s I saw was actually the startup time field. The others are pause (time to wait between checking, default 3s) and timeout (time to wait for a reply, default 1s). Since I don't think timeout should probably be

Re: [hlds] Two Issues: Odd Crash at Mapchange? And, is it OK to run SRCDS on Win 2003 x64?

2009-01-04 Thread -xL-Trinidad
Im using QyqStarter since i have also some diferent jobs to do. Works fine so far (monitors 3 gameservers, 1 ftp server, some tools like hlstats, runs 2 cronjobs and kills the ad popup of the av software). Its for Windows. www.qyq.de - Original Message - From: Jeff Sugar

Re: [hlds] Two Issues: Odd Crash at Mapchange? And, is it OK to run SRCDS on Win 2003 x64?

2009-01-04 Thread 1nsane
I had one for 2 minutes (on my fastest raid 1 server no less haha). So after a while of being completely confused as to why the hell my servers are randomly crashing whitout any dumps so eventually I increased my monitor script to wait for 2 whole minutes before killing the process and

Re: [hlds] Two Issues: Odd Crash at Mapchange? And, is it OK to run SRCDS on Win 2003 x64?

2009-01-03 Thread Jeff Sugar
I've had had both occur. I know about the auto-disconnection, and we've had it happen, but this is something different. On Sat, Jan 3, 2009 at 11:41 PM, Cc2iscooL cc2isc...@gmail.com wrote: 1.) No problem here. 2.) Does it actually -crash- or does it just go into the auto-disconnect and then

Re: [hlds] Two Issues: Odd Crash at Mapchange? And, is it OK to run SRCDS on Win 2003 x64?

2009-01-03 Thread Cc2iscooL
If it creates a .mdmp try debugging it to find the source. :) On Sat, Jan 3, 2009 at 11:45 PM, Jeff Sugar jeffsu...@gmail.com wrote: I've had had both occur. I know about the auto-disconnection, and we've had it happen, but this is something different. On Sat, Jan 3, 2009 at 11:41 PM,

Re: [hlds] Two Issues: Odd Crash at Mapchange? And, is it OK to run SRCDS on Win 2003 x64?

2009-01-03 Thread Jeff Sugar
Lastly, it doesn't leave anything in our logs (sm or not) or leave a minidump. :| Hopefully someone will have an idea. On Sat, Jan 3, 2009 at 11:53 PM, Cc2iscooL cc2isc...@gmail.com wrote: If it creates a .mdmp try debugging it to find the source. :) On Sat, Jan 3, 2009 at 11:45 PM, Jeff

Re: [hlds] Two Issues: Odd Crash at Mapchange? And, is it OK to run SRCDS on Win 2003 x64?

2009-01-03 Thread Cc2iscooL
Ah..kinda skimmed it. Might be related to the mapchange lockup (as the server doesn't respond to queries during this time)...whatever program you're using to monitor the server...does it also check for server queries? This would be why you get a crash then. On Sat, Jan 3, 2009 at 11:58 PM, Jeff

Re: [hlds] Two Issues: Odd Crash at Mapchange? And, is it OK to run SRCDS on Win 2003 x64?

2009-01-03 Thread Jeff Sugar
Ahh...Interesting idea! My program that checks the servers does indeed do server queries (usually a good thing) and reboots them after about 30s (also usually a good thing). However, considering the lockups sometimes take 30s, I wouldn't be surprised if you were right. I'll continue to monitor for

Re: [hlds] Two Issues: Odd Crash at Mapchange? And, is it OK to run SRCDS on Win 2003 x64?

2009-01-03 Thread SakeFox
just wanted to also say that there are some map timeouts that are greater then 60s. I think the longest i have seen was 90s with around avg of ~45-50secs. 60s should do you could, but to be more on the safe side maybe 120s for the mean time to just gather if its a crash or the timeout bug.