[GH-ISSUE #2797] Monitor command no longer contains "MONITOR" component in log message #2016

New issue

Closed

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

kerem commented

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

Owner

Originally created by @codingWithJimmy on GitHub (Apr 2, 2020).
Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/2797

User Story

Recently I've noticed some external monitoring I was using has stopped working and it's because the current version of LGSM no longer contains a component in the log file that helps me identify when certain actions were being taken.

Basic info

Distro: CentOS 7
Game: Team Fortress 2
Command: Monitor
LinuxGSM version: v20.1.6

Further Information

In my logs back in November 2019, I see the value I'm looking for.

Nov 20 18:05:05.641 TRAINING: MONITOR: PASS: command_monitor.sh exiting with code: 0

But now it looks like it may be inadvertently missing.

Apr 02 06:45:07.577 TRAINING: : PASS: command_monitor.sh exiting with code: 0

To Reproduce

Steps to reproduce the behaviour:

Run the monitor command on any game server
Check the script log for that server to see the result

Expected behaviour

No "MONITOR" value

Originally created by @codingWithJimmy on GitHub (Apr 2, 2020). Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/2797 ## User Story Recently I've noticed some external monitoring I was using has stopped working and it's because the current version of LGSM no longer contains a component in the log file that helps me identify when certain actions were being taken. ## Basic info * **Distro:** CentOS 7 * **Game:** Team Fortress 2 * **Command:** Monitor * **LinuxGSM version:** v20.1.6 ## Further Information In my logs back in November 2019, I see the value I'm looking for. Nov 20 18:05:05.641 TRAINING: **MONITOR**: PASS: command_monitor.sh exiting with code: 0 But now it looks like it may be inadvertently missing. Apr 02 06:45:07.577 TRAINING: : PASS: command_monitor.sh exiting with code: 0 ## To Reproduce Steps to reproduce the behaviour: 1. Run the monitor command on any game server 2. Check the script log for that server to see the result ## Expected behaviour No "MONITOR" value

kerem

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

closed this issue
added the
type: bug

command: monitor
labels

kerem commented

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

Author

Owner

@codingWithJimmy commented on GitHub (Apr 2, 2020):

Looks like the log display of core_messages.sh is looking for the "commandname" variable and the scripts are using "commandaction" as the variable.

@codingWithJimmy commented on GitHub (Apr 2, 2020): Looks like the log display of [core_messages.sh](https://github.com/GameServerManagers/LinuxGSM/blob/master/lgsm/functions/core_messages.sh) is looking for the "commandname" variable and the scripts are using "commandaction" as the variable.

kerem commented

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

Author

Owner

@codingWithJimmy commented on GitHub (Apr 2, 2020):

Confirmed. #2798

@codingWithJimmy commented on GitHub (Apr 2, 2020): Confirmed. #2798

kerem commented

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

Author

Owner

@github-actions[bot] commented on GitHub (Apr 26, 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 (Apr 26, 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:34 +03:00

[PR #2016] [MERGED] Add a Codacy badge to README.md #3452

kerem referenced this issue

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

[PR #2019] [CLOSED] Fix Ctrl+C closing wrong session #3454