[GH-ISSUE #1880] Unable to stop (servicename) #1476

New issue

Closed

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

kerem commented

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

Owner

Originally created by @TheGamingG3 on GitHub (Apr 15, 2018).
Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/1880

To sadden for my bad English, I am French.
I had an error during the ruling of my servers Linux under debian 8 Wheeze

Unable to stop (servicename)

To solve it go in / lgsm / functions / command_stop.sh

Then go to the line 266

Original
tmux kill-session -t="${servicename}" > /dev/null 2>&1

Corrected
tmux kill-session -t "${servicename}" > /dev/null 2>&1

Originally created by @TheGamingG3 on GitHub (Apr 15, 2018). Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/1880 To sadden for my bad English, I am French. I had an error during the ruling of my servers Linux under debian 8 Wheeze Unable to stop (servicename) To solve it go in / lgsm / functions / command_stop.sh Then go to the line **266** **Original** `tmux kill-session -t="${servicename}" > /dev/null 2>&1` **Corrected** `tmux kill-session -t "${servicename}" > /dev/null 2>&1`

kerem

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

closed this issue
added the
type: bug

outcome: issue resolved

outcome: duplicate
labels

kerem commented

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

Author

Owner

@UltimateByte commented on GitHub (Apr 15, 2018):

Thanks for your concern.
There was already an issue for that, and this was just fixed.
https://github.com/GameServerManagers/LinuxGSM/issues/1876

Update your LinuxGSM's functions (./gameserver uf) to get the fix.

@UltimateByte commented on GitHub (Apr 15, 2018): Thanks for your concern. There was already an issue for that, and this was just fixed. https://github.com/GameServerManagers/LinuxGSM/issues/1876 Update your LinuxGSM's functions (./gameserver uf) to get the fix.

kerem commented

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

Author

Owner

@lock[bot] commented on GitHub (Apr 15, 2019):

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 (Apr 15, 2019): 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:54:09 +03:00

[PR #1476] [MERGED] Fixed MTA not finding the update version #3340