starred/LinuxGSM

Fork 0

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

[GH-ISSUE #277] [UT99] gsquery monitor error #237

New issue

Closed

opened 2026-02-27 02:00:19 +03:00 by kerem · 5 comments

kerem commented

2026-02-27 02:00:19 +03:00

Owner

Originally created by @TFMvdBroek on GitHub (Jan 28, 2015).
Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/277

When i use gsquery.py with the monitoring function i get the following error:

[ OK ] Monitoring ut99-server: Checking session: OK

1")syntax error: invalid arithmetic operator (error token is "

Any idea why ?

Originally created by @TFMvdBroek on GitHub (Jan 28, 2015). Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/277 When i use gsquery.py with the monitoring function i get the following error: [ OK ] Monitoring ut99-server: Checking session: OK - 1")syntax error: invalid arithmetic operator (error token is " Any idea why ?

kerem

2026-02-27 02:00:19 +03:00

closed this issue
added the
type: bug
label

kerem commented

2026-02-27 02:00:20 +03:00

Author

Owner

@dgibbs64 commented on GitHub (Jan 29, 2015):

Not sure on this one. I have tested many times without this issue. Make sure your running the latest version of the script. If you update and still getting the issue I will check this myself.

@dgibbs64 commented on GitHub (Jan 29, 2015): Not sure on this one. I have tested many times without this issue. Make sure your running the latest version of the script. If you update and still getting the issue I will check this myself.

kerem commented

2026-02-27 02:00:20 +03:00

Author

Owner

@TFMvdBroek commented on GitHub (Jan 30, 2015):

After update when running ut99server monitor i get the following:

~$ ./ut99server monitor
[ INFO ] Monitor ut99-server: SteamCMD is currently checking for updates
[ INFO ] Monitor ut99-server: When update is complete ut99-server will start

Even tho the server is already running ...
Also the monitor does not seem to start the game by itself anymore. ./ut99server start needs to be run.

~$ ./ut99server monitor
[ INFO ] Monitor ut99-server: Disabled: No lock file found
To enable monitor run 0 start

@TFMvdBroek commented on GitHub (Jan 30, 2015): After update when running ut99server monitor i get the following: ~$ ./ut99server monitor [ INFO ] Monitor ut99-server: SteamCMD is currently checking for updates [ INFO ] Monitor ut99-server: When update is complete ut99-server will start Even tho the server is already running ... Also the monitor does not seem to start the game by itself anymore. ./ut99server start needs to be run. ~$ ./ut99server monitor [ INFO ] Monitor ut99-server: Disabled: No lock file found To enable monitor run 0 start

kerem commented

2026-02-27 02:00:20 +03:00

Author

Owner

@dgibbs64 commented on GitHub (Jan 30, 2015):

The SteamCMD issue I will look at. The second part is by design. The server must be started to activate the monitor. Saves the server starting itself even if you manually stop it.

@dgibbs64 commented on GitHub (Jan 30, 2015): The SteamCMD issue I will look at. The second part is by design. The server must be started to activate the monitor. Saves the server starting itself even if you manually stop it.

kerem commented

2026-02-27 02:00:20 +03:00

Author

Owner

@dgibbs64 commented on GitHub (Mar 6, 2015):

UT should no longer check that SteamCMD update is running github.com/dgibbs64/linuxgameservers@8e2b5541c8

@dgibbs64 commented on GitHub (Mar 6, 2015): UT should no longer check that SteamCMD update is running https://github.com/dgibbs64/linuxgameservers/commit/8e2b5541c8b895c77073c86c44b39c2426280a2c

kerem commented

2026-02-27 02:00:20 +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.