When using the gsquery.py plugin to monitor a server, it causes the server to restart when it's not really crashed. This happens when we load a config that uses sv_cheats 1. It's a practice config called L2L Config, not that that's of any importance. It's the sv_cheats 1 that's the issue (I and others in the community believe).
Specifically, when the server is running in this mode, it is not responsive to status queries, thus, gsquery.py thinks the server has crashed when it has not, and causes it to restart. I've checked the logs and verified it:
Feb 24 21:00:02 l4d2-server3: Monitor: Checking session: CHECKING
Feb 24 21:00:03 l4d2-server3: Monitor: Checking session: OK
Feb 24 21:00:04 l4d2-server3: Monitor: Detected gsquery.py
Feb 24 21:00:05 l4d2-server3: Monitor: Querying port: 104.207.128.135:27017 : QUERYING
Feb 24 21:00:11 l4d2-server3: Monitor: Querying port: 104.207.128.135:27017 : ERROR: Unable to receive
Feb 24 21:00:12 l4d2-server3: Monitor: Waiting 30 seconds to re-query
Feb 24 21:00:42 l4d2-server3: Monitor: Detected gsquery.py
Feb 24 21:00:43 l4d2-server3: Monitor: Querying port: 104.207.128.135:27017 : QUERYING
Feb 24 21:00:49 l4d2-server3: Monitor: Querying port: 104.207.128.135:27017 : ERROR: Unable to receive
Feb 24 21:00:50 l4d2-server3: Restarting:
Feb 24 21:00:50 l4d2-server3: Stopping:
Feb 24 21:00:51 l4d2-server3: Stopping: Stopped
Feb 24 21:00:52 l4d2-server3: Starting:
Feb 24 21:00:53 l4d2-server3: Starting: Rotating log files
I'm asking others in the L4D community if there's a system variable or file that gets created that I could check for existence and perhaps modify your script to abort the call. But I wanted to put this out there to you in case you possibly had a fix or an idea.
Servers that support RCON
- 7 days to die
- Rust
- Source engine
When using the gsquery.py plugin to monitor a server, it causes the server to restart when it's not really crashed. This happens when we load a config that uses sv_cheats 1. It's a practice config called L2L Config, not that that's of any importance. It's the sv_cheats 1 that's the issue (I and others in the community believe).
Specifically, when the server is running in this mode, it is not responsive to status queries, thus, gsquery.py thinks the server has crashed when it has not, and causes it to restart. I've checked the logs and verified it:
Feb 24 21:00:02 l4d2-server3: Monitor: Checking session: CHECKING
Feb 24 21:00:03 l4d2-server3: Monitor: Checking session: OK
Feb 24 21:00:04 l4d2-server3: Monitor: Detected gsquery.py
Feb 24 21:00:05 l4d2-server3: Monitor: Querying port: 104.207.128.135:27017 : QUERYING
Feb 24 21:00:11 l4d2-server3: Monitor: Querying port: 104.207.128.135:27017 : ERROR: Unable to receive
Feb 24 21:00:12 l4d2-server3: Monitor: Waiting 30 seconds to re-query
Feb 24 21:00:42 l4d2-server3: Monitor: Detected gsquery.py
Feb 24 21:00:43 l4d2-server3: Monitor: Querying port: 104.207.128.135:27017 : QUERYING
Feb 24 21:00:49 l4d2-server3: Monitor: Querying port: 104.207.128.135:27017 : ERROR: Unable to receive
Feb 24 21:00:50 l4d2-server3: Restarting:
Feb 24 21:00:50 l4d2-server3: Stopping:
Feb 24 21:00:51 l4d2-server3: Stopping: Stopped
Feb 24 21:00:52 l4d2-server3: Starting:
Feb 24 21:00:53 l4d2-server3: Starting: Rotating log files
I'm asking others in the L4D community if there's a system variable or file that gets created that I could check for existence and perhaps modify your script to abort the call. But I wanted to put this out there to you in case you possibly had a fix or an idea.
Servers that support RCON