starred/LinuxGSM

Fork 0

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

[GH-ISSUE #1086] Monitoring broke? #853

New issue

Closed

opened 2026-02-27 02:53:55 +03:00 by kerem · 6 comments

kerem commented

2026-02-27 02:53:55 +03:00

Owner

Originally created by @shavitush on GitHub (Sep 24, 2016).
Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/1086

My servers don't go up back after crashing, I realized monitoring broke for me since the latest CS:GO update?

root@csgo:~# su - jail
jail@csgo:~$ ./csgoserver monitor
[ERROR ] Monitor csgo-server: SteamCMD is currently checking for updates

Tried running update-functions, no help :(

Running Ubuntu 16.04LTS

Sorry for not providing logs, I have disabled logging because I run many servers and they ended up ripping apart my SSD space. I'd be glad to enable logging for a day or so if you guys can tell me which files exactly to send!

Originally created by @shavitush on GitHub (Sep 24, 2016). Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/1086 My servers don't go up back after crashing, I realized monitoring broke for me since the latest CS:GO update? ``` root@csgo:~# su - jail jail@csgo:~$ ./csgoserver monitor [ERROR ] Monitor csgo-server: SteamCMD is currently checking for updates ``` Tried running `update-functions`, no help :( Running Ubuntu 16.04LTS Sorry for not providing logs, I have disabled logging because I run many servers and they ended up ripping apart my SSD space. I'd be glad to enable logging for a day or so if you guys can tell me which files exactly to send!

kerem closed this issue

2026-02-27 02:53:55 +03:00

kerem commented

2026-02-27 02:53:55 +03:00

Author

Owner

@UltimateByte commented on GitHub (Sep 24, 2016):

Hey,

Well, i had this issue recently, that was actually due to myself having a wrongly set cronjob that would check for updates every minute instead of every 30 minutes.
So to make sure what's going on, first please check the last script log.

cat /home/jail/log/script/csgo-server-script.log

Please, paste the output here if this log exists.
In the wait for logs, you can also provide a copy of your cronjobs so that we can check them.
That way we will know if the server is actually really checking for an update.

@UltimateByte commented on GitHub (Sep 24, 2016): Hey, Well, i had this issue recently, that was actually due to myself having a wrongly set cronjob that would check for updates every minute instead of every 30 minutes. So to make sure what's going on, first please check the last script log. `cat /home/jail/log/script/csgo-server-script.log` Please, paste the output here if this log exists. In the wait for logs, you can also provide a copy of your cronjobs so that we can check them. That way we will know if the server is actually really checking for an update.

kerem commented

2026-02-27 02:53:55 +03:00

Author

Owner

@shavitush commented on GitHub (Sep 24, 2016):

Sep 23 08:20:02 csgo-server: MONITOR: INFO: Checking session: CHECKING
Sep 23 08:20:03 csgo-server: MONITOR: PASS: Checking session: OK
Sep 23 08:20:03 csgo-server: MONITOR: INFO: Querying port: gsquery.py enabled
Sep 23 08:20:04 csgo-server: MONITOR: INFO: Querying port: ser.ver.add.ress:27110 : 1 : QUERYING
Sep 23 08:20:05 csgo-server: MONITOR: PASS: Querying port: ser.ver.add.ress:27110 : 1 : OK
Sep 23 08:20:05 csgo-server: MONITOR: PASS: monitor_gsquery.sh exiting with code: 0
Sep 23 08:25:03 csgo-server: MONITOR: INFO: Checking session: CHECKING
Sep 23 08:25:04 csgo-server: MONITOR: PASS: Checking session: OK
Sep 23 08:25:04 csgo-server: MONITOR: INFO: Querying port: gsquery.py enabled
Sep 23 08:25:05 csgo-server: MONITOR: INFO: Querying port: ser.ver.add.ress:27110 : 1 : QUERYING
Sep 23 08:25:06 csgo-server: MONITOR: PASS: Querying port: ser.ver.add.ress:27110 : 1 : OK
Sep 23 08:25:06 csgo-server: MONITOR: PASS: monitor_gsquery.sh exiting with code: 0
Sep 23 08:30:01 csgo-server: UPDATE: INFO: Checking for update: Server logs
Sep 23 08:30:02 csgo-server: MONITOR: ERROR: SteamCMD is currently checking for updates
Sep 23 08:30:03 csgo-server: MONITOR: ERROR: command_monitor.sh exiting with code: 2
Sep 23 08:30:03 csgo-server: UPDATE: INFO: Checking for update: SteamCMD
Sep 23 08:31:08 csgo-server: UPDATE: PASS: Checking for update: SteamCMD
Sep 23 08:31:09 csgo-server: UPDATE: PASS: Checking for update: SteamCMD: No update available
Sep 23 08:31:09 csgo-server: UPDATE: INFO: Current build: 1346753
Sep 23 08:31:09 csgo-server: UPDATE: INFO: Available build: 1346753
Sep 23 08:31:09 csgo-server: UPDATE: PASS: command_update.sh exiting with code: 0
Sep 23 08:35:02 csgo-server: MONITOR: INFO: Checking session: CHECKING
Sep 23 08:35:03 csgo-server: MONITOR: PASS: Checking session: OK

Basically like this (since the issue started)

crontab:

*/5 * * * * /home/jail/csgoserver monitor >/dev/null 2>&1
*/30 * * * * /home/jail/csgoserver update >/dev/null 2>&1

@shavitush commented on GitHub (Sep 24, 2016): ``` Sep 23 08:20:02 csgo-server: MONITOR: INFO: Checking session: CHECKING Sep 23 08:20:03 csgo-server: MONITOR: PASS: Checking session: OK Sep 23 08:20:03 csgo-server: MONITOR: INFO: Querying port: gsquery.py enabled Sep 23 08:20:04 csgo-server: MONITOR: INFO: Querying port: ser.ver.add.ress:27110 : 1 : QUERYING Sep 23 08:20:05 csgo-server: MONITOR: PASS: Querying port: ser.ver.add.ress:27110 : 1 : OK Sep 23 08:20:05 csgo-server: MONITOR: PASS: monitor_gsquery.sh exiting with code: 0 Sep 23 08:25:03 csgo-server: MONITOR: INFO: Checking session: CHECKING Sep 23 08:25:04 csgo-server: MONITOR: PASS: Checking session: OK Sep 23 08:25:04 csgo-server: MONITOR: INFO: Querying port: gsquery.py enabled Sep 23 08:25:05 csgo-server: MONITOR: INFO: Querying port: ser.ver.add.ress:27110 : 1 : QUERYING Sep 23 08:25:06 csgo-server: MONITOR: PASS: Querying port: ser.ver.add.ress:27110 : 1 : OK Sep 23 08:25:06 csgo-server: MONITOR: PASS: monitor_gsquery.sh exiting with code: 0 Sep 23 08:30:01 csgo-server: UPDATE: INFO: Checking for update: Server logs Sep 23 08:30:02 csgo-server: MONITOR: ERROR: SteamCMD is currently checking for updates Sep 23 08:30:03 csgo-server: MONITOR: ERROR: command_monitor.sh exiting with code: 2 Sep 23 08:30:03 csgo-server: UPDATE: INFO: Checking for update: SteamCMD Sep 23 08:31:08 csgo-server: UPDATE: PASS: Checking for update: SteamCMD Sep 23 08:31:09 csgo-server: UPDATE: PASS: Checking for update: SteamCMD: No update available Sep 23 08:31:09 csgo-server: UPDATE: INFO: Current build: 1346753 Sep 23 08:31:09 csgo-server: UPDATE: INFO: Available build: 1346753 Sep 23 08:31:09 csgo-server: UPDATE: PASS: command_update.sh exiting with code: 0 Sep 23 08:35:02 csgo-server: MONITOR: INFO: Checking session: CHECKING Sep 23 08:35:03 csgo-server: MONITOR: PASS: Checking session: OK ``` Basically like this (since the issue started) crontab: ``` */5 * * * * /home/jail/csgoserver monitor >/dev/null 2>&1 */30 * * * * /home/jail/csgoserver update >/dev/null 2>&1 ```

kerem commented

2026-02-27 02:53:55 +03:00

Author

Owner

@UltimateByte commented on GitHub (Sep 25, 2016):

Well, most functions will stop if the server is checking for update, since if there is an update, the server will restart anyways.
You just happened to have the monitor at the exact same time as update check, as the message said in the first place.
Is that a big deal for you ?

@UltimateByte commented on GitHub (Sep 25, 2016): Well, most functions will stop if the server is checking for update, since if there is an update, the server will restart anyways. You just happened to have the monitor at the exact same time as update check, as the message said in the first place. Is that a big deal for you ?

kerem commented

2026-02-27 02:53:55 +03:00

Author

Owner

@shavitush commented on GitHub (Sep 25, 2016):

Not really a big deal, I'm not necessarily asking for something like it to be done withing LGSM of course :)

Thanks

@shavitush commented on GitHub (Sep 25, 2016): Not really a big deal, I'm not necessarily asking for something like it to be done withing LGSM of course :) Thanks

kerem commented

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

Author

Owner

@UltimateByte commented on GitHub (Sep 25, 2016):

There are sometimes improvements that we could not figure out without somebody asking, that's why i asked it to you if it was a big deal for ya !

I'm glad that was nothing bad in the end :)

Have fun with LGSM, feel free to come back if you see anything that seems abnormal ! :)

@UltimateByte commented on GitHub (Sep 25, 2016): There are sometimes improvements that we could not figure out without somebody asking, that's why i asked it to you if it was a big deal for ya ! I'm glad that was nothing bad in the end :) Have fun with LGSM, feel free to come back if you see anything that seems abnormal ! :)

kerem commented

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

Author

Owner

@lock[bot] commented on GitHub (Jul 19, 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 (Jul 19, 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:53:36 +03:00

[PR #853] [CLOSED] Add variable to set email's sender 'emailfrom' #3187