I recently began running my servers on Windows Server 2008 R2 instead of the Debian 4 to which I am pretty loyal. Just to try it out.
Now, already after the first day I encountered problems, because Windows has this useless popup which tells me the server isn't responding whenever it crashes - which means the process will not end before i press that effing button...
In the long run, this means that scripts monitoring wether the process is running, don't know when the server has crashed, and should be started again.
I never had this problem with Linux obviously, as the developers suppose that Linux users MIGHT use their brain and notice that the program isn't running...
My question shortened would be:
If I cannot monitor my server using the process name - then how am I supposed to monitor it? I could ping it - but lol, it will always respond anyway. I can of course always run "tskill srcds" if it doesn't end by itself, I just need a way to check wether it has crashed.
Any suggestions?
Is srcds running in console mode? I believed console applications didn't get the "x has stopped responding" popup.
[url]http://social.technet.microsoft.com/Forums/en/winservergen/thread/8e7a7f48-a65e-4cd5-a55a-a62e4f7604cc[/url]
Also, I like using ServerChecker to watch my servers. The program is outdated and has some quirks, but it's better than the more bloated watchdog software or the crappy bash scripts.
[url]http://www.dumbclan.co.uk/forum/topic/5784-dumb-serverchecker-v303/[/url]
It works with Half-Life and Source based games, among others based on the Quake engine. It can run by checking the process to see if it has stalled or ended, but this functionality doesn't work as well.
[QUOTE=Naelstrom;31962245]Is srcds running in console mode? I believed console applications didn't get the "x has stopped responding" popup.[/QUOTE]
That's what i thought too, but no :D
Anyways, thanks for the links to disable crash dialogs ^^ I'll see if it works :)
Sorry, you need to Log In to post a reply to this thread.