05-17-2011, 05:29 AM (This post was last modified: 05-17-2011, 05:31 AM by JayHax0r.)
(05-13-2011, 04:46 AM)BR5DY Wrote: Pretty much. It checks if srcds.exe is "Not Responding". If it is "Not Responding" then it will shut it down. I haven't found a server hang that didn't cause "Not Responding" or a total srcds.exe termination, but if they exist, please let me know.
This doesn't work. My servers crash / show "Not Responding" and I always have to log into remote desktop and press close (then it auto restarts).
To the above poster you need to turn off the notification & then it will work fine.
I have come across another more serious problem after further testing.Although able to add more than 10 servers it only actually saves the first 10 servers that are added.
So in other words if you load 15 servers on it & then stop the program for some reason all servers above 10 are gone & have to be manually entered again.
A quick fix for this would be appreciated. Apart from that all appears to be working fine so far.
05-17-2011, 09:19 AM (This post was last modified: 05-17-2011, 09:20 AM by BR5DY.)
(05-17-2011, 05:29 AM)JayHax0r Wrote:
(05-13-2011, 04:46 AM)BR5DY Wrote: Pretty much. It checks if srcds.exe is "Not Responding". If it is "Not Responding" then it will shut it down. I haven't found a server hang that didn't cause "Not Responding" or a total srcds.exe termination, but if they exist, please let me know.
This doesn't work. My servers crash / show "Not Responding" and I always have to log into remote desktop and press close (then it auto restarts).
To fix this, I'm going to have a checkbox in settings that disables the not responding box for Windows. It will be in the next release
coach Wrote:I have come across another more serious problem after further testing.Although able to add more than 10 servers it only actually saves the first 10 servers that are added.
So in other words if you load 15 servers on it & then stop the program for some reason all servers above 10 are gone & have to be manually entered again.
A quick fix for this would be appreciated. Apart from that all appears to be working fine so far.
Look in the ini file after you add another server and click "Save Changes". Does it save it in there? Will fix ASAP.
seDirector (formerly SRCDS Admin) - a management suite for all of your Source Engine servers (auto-update in Windows, too) Newsletter Signup - providing information on beta & stable releases and more
It was something that I had noticed in an earlier version which I forgot to report. On setting up the latest version I remembered & checked after I had added my 12th server & noticed it had stopped recording them at 10. I then stopped adding any further servers till a fix is released.
Today I had the program running & for some reason it thought the server was down so re-started it.
The problem was it wasn't down so when it started the server again it allocated the next available port (1 up from the one set) & started the server.
This then gave me two instances of the same server running.
So I thought just login via HLSW & stop the server that had been added. No good. For some reason because the program had started it I was unable to stop it.
It was not listed in the program itself but whenever I issued the "quit" command it would stop but then re-start itself, obviously via the program.
Hope that makes sense. But it is a serious bug as numerous servers can self start for some reason if a fault exists.
I found the bug in the program that causes it not to save servers over 10. I'll most likely have it fixed and released by this evening. As far as the process running, I'll create a logging option in the settings box and we can track down what's causing that.
seDirector (formerly SRCDS Admin) - a management suite for all of your Source Engine servers (auto-update in Windows, too) Newsletter Signup - providing information on beta & stable releases and more
Came home & two instances of the same server running one port apart.
It is the same server again so it must think there is no response at some stage. No error logs so no idea when or why it is happening.
Is it possible that when the server re-starts that a check is made on the port? Then only re-started on the nominated port & not the next available one.
seDirector (formerly SRCDS Admin) - a management suite for all of your Source Engine servers (auto-update in Windows, too) Newsletter Signup - providing information on beta & stable releases and more
Updated & been running ok all day. No problems so far & no extras started.
On further investigation I have found that teh network I am connected to was having some problems yesterday so maybe this was what was causing the confusion & extra serevrs starting. Posiible the way it looks for the "Unresponsive server" part?
Ah, it could have crashed due to a network connection, then SRCDS Admin detected it closing/hung, killed it, then started a new server. If the network was failing, srcds.exe would just popup and close, and SRCDS Admin would have thought srcds.exe crashed, so it kept opening up servers until it worked.
That's my guess, but the log file will tell us more.
seDirector (formerly SRCDS Admin) - a management suite for all of your Source Engine servers (auto-update in Windows, too) Newsletter Signup - providing information on beta & stable releases and more
OK, just checked & had 3 servers doubled up again.
I gather the log is the new SRCDSAdmin.txt file that is now being created? If so it had nothing in it relating to the re-starts, only when the servers were started or stopped by me.
Once again the network was being worked on tonight. Not sure if it is related though.
When the server is re-started can it be made not to use another port but only the one allocated?
I have never had this problem with ServerChecker but would like to try & solve this problem otherwise I will have to switch back I am afraid.
(05-20-2011, 01:51 AM)coach Wrote: OK, just checked & had 3 servers doubled up again.
I gather the log is the new SRCDSAdmin.txt file that is now being created? If so it had nothing in it relating to the re-starts, only when the servers were started or stopped by me.
Once again the network was being worked on tonight. Not sure if it is related though.
When the server is re-started can it be made not to use another port but only the one allocated?
I have never had this problem with ServerChecker but would like to try & solve this problem otherwise I will have to switch back I am afraid.
Is your server very fast? What are its specs? OS, RAM, Processor.
What game(s) are you running?
It could be the network being worked on. I've run the program on my server for a few weeks now and it hasn't doubled up whatsoever.
seDirector (formerly SRCDS Admin) - a management suite for all of your Source Engine servers (auto-update in Windows, too) Newsletter Signup - providing information on beta & stable releases and more