starred/LinuxGSM

Fork 0

mirror of https://github.com/GameServerManagers/LinuxGSM.git synced 2026-04-25 14:15:59 +03:00

[GH-ISSUE #1708] tf2server monitor won't restart server. as it is stuck in an infinite loop. How do I make ./gameserver monitor restart after a few attempts at querying? #1331

New issue

Closed

opened 2026-02-27 02:56:32 +03:00 by kerem · 3 comments

kerem commented

2026-02-27 02:56:32 +03:00

Owner

Originally created by @diamondburned on GitHub (Nov 23, 2017).
Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/1708

Recently my server started killing itself every morning or so. I checked the console and found this:

WatchDog! Server took too long to process (probably infinite loop).
Host_Error: WatchdogHandler called - server exiting.

In crash.limetech.org: http://moddageserver.ddns.net/1511474324.png

engine_srv.so!Sys_Error_Internal(bool, char const*, char*) + 0x1a1
engine_srv.so!Sys_Error(char const*, ...) + 0x20
engine_srv.so!Host_Error(char const*, ...) + 0xcc
engine_srv.so!WatchDogHandler() + 0x12
linux-gate.so + 0xca0
vphysics_srv.so!IVP_OV_Tree_Manager::connect_boxes(IVP_OV_Node*, IVP_OV_Node*) + 0x143
vphysics_srv.so + 0x1248a3
vphysics_srv.so!IVP_Mindist_Manager::recheck_ov_element(IVP_Real_Object*) + 0x143
vphysics_srv.so + 0x13b9cf
vphysics_srv.so!IVP_Environment::simulate_psi(IVP_Time) + 0x135
Note that it says 2 reports share this crash signature. (1 owner / 1 ip)

My crontab -e:

/30 * * * * '/home/gyrtf2/tf2server update' > /dev/null 2>&1
@reboot '/home/gyrtf2/tf2server monitor' > /dev/null 2>&1
/1 * * * * '/home/gyrtf2/tf2server monitor' > /dev/null 2>&1

Output of ./tf2server monitor:

gyrtf2@notascam:~$ ./tf2server monitor
[ OK ] Log-Manager tf2server: Starting
[ INFO ] Log-Manager tf2server: Removing logs older than 7 days
[ OK ] Log-Manager tf2server: Removed 131 log files
[ OK ] Monitor tf2server: Checking session: OK
[ FAIL ] Monitor tf2server: Querying port: 185.215.224.207:27015 : 5/1 : ERROR: Unable to receive^C

^C means Ctrl+C which I pressed because the thing was going on for ever and couldn't restart. I then had to go to Console, do Ctrl+C and start the server again.

My question is: How do I make ./gameserver monitor restart after a few attempts at querying?

Originally created by @diamondburned on GitHub (Nov 23, 2017). Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/1708 Recently my server started killing itself every morning or so. I checked the console and found this: >WatchDog! Server took too long to process (probably infinite loop). >Host_Error: WatchdogHandler called - server exiting. In `crash.limetech.org`: http://moddageserver.ddns.net/1511474324.png >engine_srv.so!Sys_Error_Internal(bool, char const*, char*) + 0x1a1 >engine_srv.so!Sys_Error(char const*, ...) + 0x20 >engine_srv.so!Host_Error(char const*, ...) + 0xcc >engine_srv.so!WatchDogHandler() + 0x12 >linux-gate.so + 0xca0 >vphysics_srv.so!IVP_OV_Tree_Manager::connect_boxes(IVP_OV_Node*, IVP_OV_Node*) + 0x143 >vphysics_srv.so + 0x1248a3 >vphysics_srv.so!IVP_Mindist_Manager::recheck_ov_element(IVP_Real_Object*) + 0x143 >vphysics_srv.so + 0x13b9cf >vphysics_srv.so!IVP_Environment::simulate_psi(IVP_Time) + 0x135 Note that it says 2 reports share this crash signature. (1 owner / 1 ip) My `crontab -e`: >*/30 * * * * '/home/gyrtf2/tf2server update' > /dev/null 2>&1 >@reboot '/home/gyrtf2/tf2server monitor' > /dev/null 2>&1 >*/1 * * * * '/home/gyrtf2/tf2server monitor' > /dev/null 2>&1 Output of `./tf2server monitor`: >gyrtf2@notascam:~$ ./tf2server monitor >[ OK ] Log-Manager tf2server: Starting >[ INFO ] Log-Manager tf2server: Removing logs older than 7 days >[ OK ] Log-Manager tf2server: Removed 131 log files >[ OK ] Monitor tf2server: Checking session: OK >[ FAIL ] Monitor tf2server: Querying port: 185.215.224.207:27015 : 5/1 : ERROR: Unable to receive^C ^C means Ctrl+C which I pressed because the thing was going on for ever and couldn't restart. I then had to go to Console, do Ctrl+C and start the server again. My question is: How do I make ./gameserver monitor restart after a few attempts at querying?

kerem closed this issue

2026-02-27 02:56:32 +03:00

kerem commented

2026-02-27 02:56:33 +03:00

Author

Owner

@Nealcaffrey2016 commented on GitHub (Nov 24, 2017):

Maybe you should add a timeout on the connection,so after a few time try to connect to the game server,the client will quit with a error.

Sent from Neal Caffrey
On 11/24/2017 06:05, diamondburned wrote:

Recently my server starts killing itself every morning or so. I checked the console and found this:

WatchDog! Server took too long to process (probably infinite loop).
Host_Error: WatchdogHandler called - server exiting.

In crash.limetech.org: http://moddageserver.ddns.net/1511474324.png

engine_srv.so!Sys_Error_Internal(bool, char const*, char*) + 0x1a1
engine_srv.so!Sys_Error(char const*, ...) + 0x20
engine_srv.so!Host_Error(char const*, ...) + 0xcc
engine_srv.so!WatchDogHandler() + 0x12
linux-gate.so + 0xca0
vphysics_srv.so!IVP_OV_Tree_Manager::connect_boxes(IVP_OV_Node*, IVP_OV_Node*) + 0x143
vphysics_srv.so + 0x1248a3
vphysics_srv.so!IVP_Mindist_Manager::recheck_ov_element(IVP_Real_Object*) + 0x143
vphysics_srv.so + 0x13b9cf
vphysics_srv.so!IVP_Environment::simulate_psi(IVP_Time) + 0x135
Note that it says 2 reports share this crash signature. (1 owner / 1 ip)

My crontab -e:

*/30 * * * * '/home/gyrtf2/tf2server update' > /dev/null 2>&1
@reboot '/home/gyrtf2/tf2server monitor' > /dev/null 2>&1
*/1 * * * * '/home/gyrtf2/tf2server monitor' > /dev/null 2>&1

Output of ./tf2server monitor:

gyrtf2@notascam:~$ ./tf2server monitor
[ OK ] Log-Manager tf2server: Starting
[ INFO ] Log-Manager tf2server: Removing logs older than 7 days
[ OK ] Log-Manager tf2server: Removed 131 log files
[ OK ] Monitor tf2server: Checking session: OK
[ FAIL ] Monitor tf2server: Querying port: 185.215.224.207:27015 : 5/1 : ERROR: Unable to receive^C

^C means Ctrl+C which I pressed because the thing was going forever and couldn't restart. I then had to go to Console, do Ctrl+C and start the server again.

My question is: How do I make ./gameserver monitor restart after a few attempts at querying?

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

@Nealcaffrey2016 commented on GitHub (Nov 24, 2017): Maybe you should add a timeout on the connection,so after a few time try to connect to the game server,the client will quit with a error. Sent from Neal Caffrey On 11/24/2017 06:05, diamondburned wrote: Recently my server starts killing itself every morning or so. I checked the console and found this: WatchDog! Server took too long to process (probably infinite loop). Host_Error: WatchdogHandler called - server exiting. In crash.limetech.org: http://moddageserver.ddns.net/1511474324.png engine_srv.so!Sys_Error_Internal(bool, char const*, char*) + 0x1a1 engine_srv.so!Sys_Error(char const*, ...) + 0x20 engine_srv.so!Host_Error(char const*, ...) + 0xcc engine_srv.so!WatchDogHandler() + 0x12 linux-gate.so + 0xca0 vphysics_srv.so!IVP_OV_Tree_Manager::connect_boxes(IVP_OV_Node*, IVP_OV_Node*) + 0x143 vphysics_srv.so + 0x1248a3 vphysics_srv.so!IVP_Mindist_Manager::recheck_ov_element(IVP_Real_Object*) + 0x143 vphysics_srv.so + 0x13b9cf vphysics_srv.so!IVP_Environment::simulate_psi(IVP_Time) + 0x135 Note that it says 2 reports share this crash signature. (1 owner / 1 ip) My crontab -e: */30 * * * * '/home/gyrtf2/tf2server update' > /dev/null 2>&1 @reboot '/home/gyrtf2/tf2server monitor' > /dev/null 2>&1 */1 * * * * '/home/gyrtf2/tf2server monitor' > /dev/null 2>&1 Output of ./tf2server monitor: gyrtf2@notascam:~$ ./tf2server monitor [ OK ] Log-Manager tf2server: Starting [ INFO ] Log-Manager tf2server: Removing logs older than 7 days [ OK ] Log-Manager tf2server: Removed 131 log files [ OK ] Monitor tf2server: Checking session: OK [ FAIL ] Monitor tf2server: Querying port: 185.215.224.207:27015 : 5/1 : ERROR: Unable to receive^C ^C means Ctrl+C which I pressed because the thing was going forever and couldn't restart. I then had to go to Console, do Ctrl+C and start the server again. My question is: How do I make ./gameserver monitor restart after a few attempts at querying? — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.

kerem commented

2026-02-27 02:56:33 +03:00

Author

Owner

@UltimateByte commented on GitHub (Nov 24, 2017):

https://github.com/GameServerManagers/LinuxGSM/wiki/Monitor#how-does-monitor-work

My question is: How do I make ./gameserver monitor restart after a few attempts at querying?

You just wait 60s. Also, you use a cron to restart the server every night, and another cron to monitor the server, that way you stop even thinking about it.
https://github.com/GameServerManagers/LinuxGSM/wiki/Cronjobs

@UltimateByte commented on GitHub (Nov 24, 2017): https://github.com/GameServerManagers/LinuxGSM/wiki/Monitor#how-does-monitor-work > My question is: How do I make ./gameserver monitor restart after a few attempts at querying? You just wait 60s. Also, you use a cron to restart the server every night, and another cron to monitor the server, that way you stop even thinking about it. https://github.com/GameServerManagers/LinuxGSM/wiki/Cronjobs

kerem commented

2026-02-27 02:56:33 +03:00

Author

Owner

@lock[bot] commented on GitHub (Nov 24, 2018):

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock[bot] commented on GitHub (Nov 24, 2018): This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

kerem referenced this issue

2026-02-27 03:54:05 +03:00

[PR #1331] [MERGED] New core_getopt.sh and FastDL generator for all source servers #3319