starred/LinuxGSM

Fork 0

mirror of https://github.com/GameServerManagers/LinuxGSM.git synced 2026-04-25 06:05:57 +03:00

[GH-ISSUE #2054] Find a way that Monitoring detect if server is (re)starting or not. #1605

New issue

Closed

opened 2026-02-27 02:58:04 +03:00 by kerem · 6 comments

kerem commented

2026-02-27 02:58:04 +03:00

Owner

Originally created by @BattleSheep94 on GitHub (Oct 21, 2018).
Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/2054

My Server needs more than 2 minutes to (re)start.
If i "activate" the monitoring cronjob the server stucks in a loop from monitoring and restart.
Maybe you can add a "status" that the monitoring says. "Server is already restarting, try again in ${required-restarttime}"
Maybe with a time that you can define in the config where we can say how long the server needs to restart.

Originally created by @BattleSheep94 on GitHub (Oct 21, 2018). Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/2054 My Server needs more than 2 minutes to (re)start. If i "activate" the monitoring cronjob the server stucks in a loop from monitoring and restart. Maybe you can add a "status" that the monitoring says. "Server is already restarting, try again in ${required-restarttime}" Maybe with a time that you can define in the config where we can say how long the server needs to restart.

kerem

2026-02-27 02:58:04 +03:00

closed this issue
added the
command: monitor
label

kerem commented

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

Author

Owner

@dgibbs64 commented on GitHub (Oct 21, 2018):

A quick fix would be to extend the monitoring time in the Cron so something like 5-10 mins per check

@dgibbs64 commented on GitHub (Oct 21, 2018): A quick fix would be to extend the monitoring time in the Cron so something like 5-10 mins per check

kerem commented

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

Author

Owner

@dgibbs64 commented on GitHub (Feb 8, 2019):

related to #2119

@dgibbs64 commented on GitHub (Feb 8, 2019): related to #2119

kerem commented

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

Author

Owner

@haggbart commented on GitHub (Apr 24, 2019):

or use rcon, or use server logs

Just adding a delay is seems dirty. Ideally the server should start within seconds of crashing or shutting down for restart. tcadmin does this correctly

@haggbart commented on GitHub (Apr 24, 2019): or use rcon, or use server logs Just adding a delay is seems dirty. Ideally the server should start within seconds of crashing or shutting down for restart. tcadmin does this correctly

kerem commented

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

Author

Owner

@h3o66 commented on GitHub (Feb 15, 2020):

do you know if this was solved with this #2119 ?

@h3o66 commented on GitHub (Feb 15, 2020): do you know if this was solved with this #2119 ?

kerem commented

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

Author

Owner

@dgibbs64 commented on GitHub (Jul 13, 2020):

all servers now have a query delay set. This means if the server has only just started there will be a delay before monitor queries the server for the first time. The monitor will still check that the executable is running. So I believe this fixes this issue

@dgibbs64 commented on GitHub (Jul 13, 2020): all servers now have a query delay set. This means if the server has only just started there will be a delay before monitor queries the server for the first time. The monitor will still check that the executable is running. So I believe this fixes this issue

kerem commented

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

Author

Owner

@github-actions[bot] commented on GitHub (Jul 14, 2021):

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

@github-actions[bot] commented on GitHub (Jul 14, 2021): This issue 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:16 +03:00

[PR #1606] [MERGED] Added fix_ark.sh() to core_functions (hotfix/170803.1) #3371