Linux server startup failure

So I've been trying out the Linux Game Server Manager (LGSM) on a linux server to host my rust server. I've seen lots of people struggling to get their server to start since the last update where Garry added better AI. Bravo BTW. 'bout time ;-)

I've run into the same problem as others but think I've found the reason. UpdateNavMesh takes a long time to run. This varies by map size, complexity, processing available, memory, etc etc... Here's the catch. The LGSM rustserver script that you run to start your server has a built in monitor to check to see if the server has started yet. If it fails to detect a working rust server within 60 seconds, it stops the server and tries again. Repeatedly. Which for me is after only 27% of the UpdateNavMesh. Annoying.

You can see in the "~/log/script/rust-server-script.log" log file. For example:

Code:

Apr 21 03:11:20 rust-server: START: PASS: Started FireStorm Private Test Server
Apr 21 03:11:20 rust-server: START: PASS: command_start.sh exiting with code: 0
Apr 21 03:15:03 rust-server: MONITOR: INFO: Checking session: CHECKING
Apr 21 03:15:04 rust-server: MONITOR: PASS: Checking session: OK
Apr 21 03:15:04 rust-server: MONITOR: INFO: Querying port: gsquery.py enabled
Apr 21 03:15:05 rust-server: MONITOR: INFO: Querying port: 192.168.0.250:28015 : 1 : QUERYING
Apr 21 03:15:06 rust-server: MONITOR: INFO: Querying port: 192.168.0.250:28015 : 1 : ERROR: Unable to receive
Apr 21 03:15:21 rust-server: MONITOR: INFO: Querying port: 192.168.0.250:28015 : 2 : QUERYING
Apr 21 03:15:23 rust-server: MONITOR: INFO: Querying port: 192.168.0.250:28015 : 2 : ERROR: Unable to receive
Apr 21 03:15:38 rust-server: MONITOR: INFO: Querying port: 192.168.0.250:28015 : 3 : QUERYING
Apr 21 03:15:39 rust-server: MONITOR: INFO: Querying port: 192.168.0.250:28015 : 3 : ERROR: Unable to receive
Apr 21 03:15:54 rust-server: MONITOR: INFO: Querying port: 192.168.0.250:28015 : 4 : QUERYING
Apr 21 03:15:55 rust-server: MONITOR: INFO: Querying port: 192.168.0.250:28015 : 4 : ERROR: Unable to receive
Apr 21 03:16:10 rust-server: MONITOR: INFO: Querying port: 192.168.0.250:28015 : 5 : QUERYING
Apr 21 03:16:11 rust-server: MONITOR: INFO: Querying port: 192.168.0.250:28015 : 5 : ERROR: Unable to receive
Apr 21 03:16:11 rust-server: MONITOR: ERROR: Querying port: 192.168.0.250:28015 : 5 : FAIL
Apr 21 03:16:12 rust-server: ALERT: INFO: Sending restart alert: ERROR: Unable to receive
Apr 21 03:16:14 rust-server: STOP: INFO: Graceful: CTRL+c
Apr 21 03:16:14 rust-server: STOP: PASS: Graceful: CTRL+c: OK: 1 seconds
Apr 21 03:16:15 rust-server: STOP: INFO: tmux kill-session: FireStorm Private Test Server
Apr 21 03:16:16 rust-server: STOP: PASS: Stopped FireStorm Private Test Server
Apr 21 03:16:18 rust-server: CHECK: INFO: Using anonymous Steam login
Apr 21 03:16:19 rust-server: START: INFO: Rotating log files

I'm looking for ways to disable the monitoring or extend the timeout. Does anyone know this script well enough to help? I may just need to abandon using LGSM to manage my server and write my own scripts. Perhaps less is more in this case.

Hopefully this post also helps other admins understand why their LGSM rust servers are not starting.

EDIT:
So I missed something. I had a cron job running every 5 minutes to monitor the server and restart if needed. The output was being merged into the log above which made me think it was part of the start function of the script when it really wasn't. Disabling the monitor job has allowed me to load my server. So to correct myself the monitor was the problem but it is not related to the start function of the script.

 

I have exactly the same problem.
I wish I could monitor my server without stopping the control of the monitor.

Is it possible to increase the search time of gsquery.py ?

 

Nobody can monitor his server with "monitor" without it being restarted too fast ?