[GH-ISSUE #3876] [BUG] The scripts using grep to get game server information can garble info when multiple lines match the grep. #2521

New issue

Closed

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

kerem commented

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

Owner

Originally created by @Avanesov79 on GitHub (May 29, 2022).
Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/3876

User Story

As a server admin I want the game server gathering scripts to not assume that the target string is only listed once in the config file.

Basic info

Distro: AlmaLinux 8.6 (Sky Tiger)
Game: Ark: Survival Evolved
Command: I have noticed this in details, backup and I believe it is responsible for my discord alert failure as well.
LinuxGSM version: v21.5.1

Further Information

I use the Beacon server manager to setup my Ark configuration files. It prints the config files with additional lines that contains meta data about what fields it manages. When the LinuxGSM scripts gathers info from these files it grabs the additional lines that also contains references to the keys it is looking for and outputs it all together. For example when I run "./arklostisland details" the "Server Name:" section lists:

Server name:         ManagedKeys(SectionSessionSettingsKeys())
Avas Lost Island Ark Server

This is because the "SessionName" string that is grepped is also included in the [Beacon] section so Beacon knows it is a managed key.

To Reproduce

Steps to reproduce the behaviour:

Add additional lines to a config file that is grepped for a specific string and reference that string along with other information.
Run ./serverscript details (or backup, or run a discord test-alert if the key for the server name is referenced...it will not parse the JSON)
check your output

Expected behaviour

The information gathering scripts should be able to distinguish between lines that contain only the needed key=value pair and other lines that may reference the desired key.

I am attaching my ark server config file that contains the added content by Beacon (private info redacted) as well as a file with relevant output from the details command to show what is gathered. The relevant details fields are: Server Name, Server Password and Admin Password.
details_info.txt
GameUserSettings_upload.ini.txt

Originally created by @Avanesov79 on GitHub (May 29, 2022). Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/3876 ## User Story As a server admin I want the game server gathering scripts to not assume that the target string is only listed once in the config file. ## Basic info Distro: AlmaLinux 8.6 (Sky Tiger) Game: Ark: Survival Evolved Command: I have noticed this in details, backup and I believe it is responsible for my discord alert failure as well. LinuxGSM version: v21.5.1 ## Further Information I use the Beacon server manager to setup my Ark configuration files. It prints the config files with additional lines that contains meta data about what fields it manages. When the LinuxGSM scripts gathers info from these files it grabs the additional lines that also contains references to the keys it is looking for and outputs it all together. For example when I run "./arklostisland details" the "Server Name:" section lists: ``` Server name: ManagedKeys(SectionSessionSettingsKeys()) Avas Lost Island Ark Server ``` This is because the "SessionName" string that is grepped is also included in the [Beacon] section so Beacon knows it is a managed key. ## To Reproduce Steps to reproduce the behaviour: 1. Add additional lines to a config file that is grepped for a specific string and reference that string along with other information. 2. Run ./serverscript details (or backup, or run a discord test-alert if the key for the server name is referenced...it will not parse the JSON) 3. check your output ## Expected behaviour The information gathering scripts should be able to distinguish between lines that contain only the needed key=value pair and other lines that may reference the desired key. I am attaching my ark server config file that contains the added content by Beacon (private info redacted) as well as a file with relevant output from the details command to show what is gathered. The relevant details fields are: Server Name, Server Password and Admin Password. [details_info.txt](https://github.com/GameServerManagers/LinuxGSM/files/8792517/details_info.txt) [GameUserSettings_upload.ini.txt](https://github.com/GameServerManagers/LinuxGSM/files/8792519/GameUserSettings_upload.ini.txt)

kerem

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

closed this issue
added the
type: bug

command: details

info: alerts

distro: AlmaLinux
labels

kerem commented

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

Author

Owner

@h3o66 commented on GitHub (May 29, 2022):

See the connected pr #3878 this hopefully fixes the issue for you and probably others.

@h3o66 commented on GitHub (May 29, 2022): See the connected pr #3878 this hopefully fixes the issue for you and probably others.

kerem commented

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

Author

Owner

@Avanesov79 commented on GitHub (May 31, 2022):

I manually applied the changes in #3878 and it has fixed the issue for me. The details command now displays all fields correctly and test-alert no longer fails to parse JSON for discord.

@Avanesov79 commented on GitHub (May 31, 2022): I manually applied the changes in [#3878](https://github.com/GameServerManagers/LinuxGSM/pull/3878) and it has fixed the issue for me. The details command now displays all fields correctly and test-alert no longer fails to parse JSON for discord.

kerem commented

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

Author

Owner

@github-actions[bot] commented on GitHub (Jun 4, 2023):

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 (Jun 4, 2023): 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:55:26 +03:00

[PR #2521] [MERGED] fix(insserver): fix various problem #3684

kerem referenced this issue

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

[PR #2557] [MERGED] v19.11.0 #3702