SpaceBass

Hi, thanks, but I believe I have resolved the issue. Not sure how, but I do know before it didn't stop because it gave it a restart command in the console. Changing it to "killserver" instead of "quit" may have been the fix. I can try to recreate the issue to be double sure if you want. I was having trouble with the Monitor continuously freezing up and not being able to stop or restart it through the terminal or services. The process was stuck so I had to kill it then start the service. That happened all day yesterday, but was fine Today. Another note. A small error in a script flooded one of my servers (which was fixed), but at the time I had kill the process manually because trying to stop it through the web would not work, I guess because that just sends a command to the console, which wouldn't have worked if it was being flooded. Though, I had to then repeat the monitor freezing up process, not sure why that kept happening.

I've actually been having this issue as well and wanted to make a thread on it. If I restart/stop a server it doesn't fully kill the process. If I restart it will hook onto a new port because the previous did not stop. So far to fix it I just changed the stop command to "killserver" instead of "quit" which I would rather not and changed the Web Console Input to "RCon Protcol" Which, using RCon is a little annoying to do every time. Not that the console is being kind to me. I've been having trouble getting the web console to work for me at all really. It displays just fine though. If I just set the wait command to "20s" would that work better or am I not doing something correctly here? PS: This is happening with all the servers I have installed (CS:S, GMOD, HL2MP) With the RCon protcol set to CounterStrike (not sure what to use) and Query to (Half-Life 2 new) to sorta fix it. Also, sorry for posting on an older thread, but it is not to old and is the same issue. ~SpaceBass~