[GH-ISSUE #3113] LinuxGSM shows wrong server name when running multiple instances of ARK #2200

New issue

Closed

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

kerem commented

2026-02-27 03:01:28 +03:00

Owner

Originally created by @StinkyMcKraken on GitHub (Nov 26, 2020).
Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/3113

User Story

LinuxGSM frequently shows the wrong server name when managing multiple instances of ARK Survival

Basic info

Distro: [Ubuntu 20.04.1 LTS]
Game: [ARK Survival Evolved]
Command: [start, stop, restart, alert]
LinuxGSM version: [v20.5.1]

Further Information

I run multiple (9) instances of ARK off the same install. I have very few players, so the instances do not all run at the same time. I have Discord Alerts enabled and have written a simple python script to allow players to start and stop the various server instances via Discord.

LinuxGSM extracts the server name from the ARK config file ~/serverfiles/ShooterGame/Saved/Config/LinuxServer/GameUserSettings.ini. Since I am running multiple instances, there is no way to use GameUserSettings.ini to specify server names for the different instances, therefore I have used LinuxGSM's instance.cfg to manage server names on ARK's command line. The issue is LinuxGSM gets the server name from GameUserSettings.ini after it processes instance.cfg and typically the name in GameUserSettings.ini does not match the instance being invoked, so console responses from LinuxGSM display the wrong server name in its stdout and in LinuxGSM's built in Discord Alerts. From a functional standpoint, server name has no bearing on the operation of the server instances, this is just an informational bug.

A quick fix may be to add a flag to _default.cfg, GetNameFromServerFiles=True. When true, LinuxGSM will extract the server name from the configs in serverfiles as it does currently. If GetNameFromServerFiles=False in instance.cfg or common.cfg, LinuxGSM does not read from the serverfiles configs. This fix can be universal to all games, not just ARK.

To Reproduce

Steps to reproduce the behaviour:

Install ARK, configure multiple instances. Named arkisland and arkgenesis.
Use ~/lgsm/config-lgsm/arkserver/arkisland.cfg to specify sessionname="ExampleIsland" (and other settings appropriately)
Use ~/lgsm/config-lgsm/arkserver/arkgenesis.cfg to specify sessionname="ExampleGenesis" (and other settings appropriately)
Start arkisland. LinuxGSM stdout: [...] Starting arkisland: LinuxGSM
Wait 5 minutes for server to initialize
Start arkgenesis. LinuxGSM stdout: [...] Starting arkgenesis: ExampleIsland
optional:
Stop arkgenesis. LinuxGSM stdout: [...] Stopping arkgenesis: ExampleGenesis
Stop arkisland. LinuxGSM stdout: [...] Stopping arkisland: ExampleGenesis
Start arkisland. LinuxGSM stdout: [...] Starting arkisland: ExampleGenesis

Expected behaviour

See LinuxGSM stdout: [...] Starting arkisland: ExampleIsland
See LinuxGSM stdout: [...] Starting arkgenesis: ExampleGenesis

Originally created by @StinkyMcKraken on GitHub (Nov 26, 2020). Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/3113 ## User Story LinuxGSM frequently shows the wrong server name when managing multiple instances of ARK Survival ## Basic info * **Distro:** [Ubuntu 20.04.1 LTS] * **Game:** [ARK Survival Evolved] * **Command:** [start, stop, restart, alert] * **LinuxGSM version:** [v20.5.1] ## Further Information I run multiple (9) instances of ARK off the same install. I have very few players, so the instances do not all run at the same time. I have Discord Alerts enabled and have written a simple python script to allow players to start and stop the various server instances via Discord. LinuxGSM extracts the server name from the ARK config file ~/serverfiles/ShooterGame/Saved/Config/LinuxServer/GameUserSettings.ini. Since I am running multiple instances, there is no way to use GameUserSettings.ini to specify server names for the different instances, therefore I have used LinuxGSM's instance.cfg to manage server names on ARK's command line. The issue is LinuxGSM gets the server name from GameUserSettings.ini after it processes instance.cfg and typically the name in GameUserSettings.ini does not match the instance being invoked, so console responses from LinuxGSM display the wrong server name in its stdout and in LinuxGSM's built in Discord Alerts. From a functional standpoint, server name has no bearing on the operation of the server instances, this is just an informational bug. A quick fix may be to add a flag to _default.cfg, GetNameFromServerFiles=True. When true, LinuxGSM will extract the server name from the configs in serverfiles as it does currently. If GetNameFromServerFiles=False in instance.cfg or common.cfg, LinuxGSM does not read from the serverfiles configs. This fix can be universal to all games, not just ARK. ## To Reproduce Steps to reproduce the behaviour: 1. Install ARK, configure multiple instances. Named arkisland and arkgenesis. Use ~/lgsm/config-lgsm/arkserver/arkisland.cfg to specify sessionname="ExampleIsland" (and other settings appropriately) Use ~/lgsm/config-lgsm/arkserver/arkgenesis.cfg to specify sessionname="ExampleGenesis" (and other settings appropriately) 2. Start arkisland. LinuxGSM stdout: [...] Starting arkisland: LinuxGSM 3. Wait 5 minutes for server to initialize 4. Start arkgenesis. LinuxGSM stdout: [...] Starting arkgenesis: ExampleIsland optional: 5. Stop arkgenesis. LinuxGSM stdout: [...] Stopping arkgenesis: ExampleGenesis 6. Stop arkisland. LinuxGSM stdout: [...] Stopping arkisland: ExampleGenesis 7. Start arkisland. LinuxGSM stdout: [...] Starting arkisland: ExampleGenesis ## Expected behaviour See LinuxGSM stdout: [...] Starting arkisland: ExampleIsland See LinuxGSM stdout: [...] Starting arkgenesis: ExampleGenesis

kerem

2026-02-27 03:01:28 +03:00

closed this issue
added the
type: bug
label

kerem commented

2026-02-27 03:01:29 +03:00

Author

Owner

@issue-label-bot[bot] commented on GitHub (Nov 26, 2020):

Issue-Label Bot is automatically applying the label type: bug to this issue, with a confidence of 0.93. Please mark this comment with 👍 or 👎 to give our bot feedback!

Links: app homepage, dashboard and code for this bot.

@issue-label-bot[bot] commented on GitHub (Nov 26, 2020): Issue-Label Bot is automatically applying the label `type: bug` to this issue, with a confidence of 0.93. Please mark this comment with :thumbsup: or :thumbsdown: to give our bot feedback! Links: [app homepage](https://github.com/marketplace/issue-label-bot), [dashboard](https://mlbot.net/data/GameServerManagers/LinuxGSM) and [code](https://github.com/hamelsmu/MLapp) for this bot.

kerem commented

2026-02-27 03:01:29 +03:00

Author

Owner

@Claiyc commented on GitHub (Mar 23, 2022):

Has more to do with how ark works and isn't really an issue with lgsm. The ark session name is defined in GameUserSettings.ini (as well as many other settings) and that cannot be changed for specific instances.

@Claiyc commented on GitHub (Mar 23, 2022): Has more to do with how ark works and isn't really an issue with lgsm. The ark session name is defined in GameUserSettings.ini (as well as many other settings) and that cannot be changed for specific instances.

kerem commented

2026-02-27 03:01:29 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Mar 24, 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 (Mar 24, 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:54:51 +03:00

[PR #2200] [MERGED] fix(ts3server): correct ts3server config file name in comment #3531