starred/LinuxGSM

Fork 0

mirror of https://github.com/GameServerManagers/LinuxGSM.git synced 2026-04-25 06:05:57 +03:00

[GH-ISSUE #2863] [CSGOServer] Default Slots Monitor #2056

New issue

Closed

opened 2026-02-27 03:00:35 +03:00 by kerem · 6 comments

kerem commented

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

Owner

Originally created by @JamsRepos on GitHub (May 4, 2020).
Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/2863

User Story

As a CS:GO Server Owner, I want an explanation as to why my servers crash/restart to 20 player slots so that I can get it fixed to it goes to it's custom set amount.

Basic info

Distro: Ubuntu 16.04
Game: Counter-Strike: Global Offensive
Command: Monitor
LinuxGSM version: v20.2.0

Further Information

When a server seems to be detected as down, the server will restart and come back up with 20 player slots. I have an already defined variable for this which it seems to ignore. It seems to only happen with the monitor command detecting the server as down. If I use ./csgoserver restart it will use the specified value.

To Reproduce

Steps to reproduce the behaviour:

Setup a CS:GO server.
Assign a custom slots value in common.cfg/csgoserver.cfg.
Crash the server, wait till the monitor restarts it.
See you have 20 player slots of which you did not specify.

Expected behaviour

Monitor simply see's the server in a down state, turns it back on with all your custom specifications.

Originally created by @JamsRepos on GitHub (May 4, 2020). Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/2863 ## User Story As a CS:GO Server Owner, I want an explanation as to why my servers crash/restart to 20 player slots so that I can get it fixed to it goes to it's custom set amount. ## Basic info * **Distro:** Ubuntu 16.04 * **Game:** Counter-Strike: Global Offensive * **Command:** Monitor * **LinuxGSM version:** v20.2.0 ## Further Information When a server seems to be detected as down, the server will restart and come back up with 20 player slots. I have an already defined variable for this which it seems to ignore. It seems to only happen with the monitor command detecting the server as down. If I use ./csgoserver restart it will use the specified value. ## To Reproduce Steps to reproduce the behaviour: 1. Setup a CS:GO server. 2. Assign a custom slots value in common.cfg/csgoserver.cfg. 3. Crash the server, wait till the monitor restarts it. 4. See you have 20 player slots of which you did not specify. ## Expected behaviour Monitor simply see's the server in a down state, turns it back on with all your custom specifications.

kerem

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

closed this issue
added the
game: Counter-Strike: Global Offensive
label

kerem commented

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

Author

Owner

@WorthlessJ commented on GitHub (May 7, 2020):

This might be because setting max playercount at startup is supposed to be deprecated and some weird stuff is happening. There is a example file called gamemodes_server.txt.example inside /serverfiles/csgo/
Follow the examples for setting playercount in a new gamemodes_server.txt file and see if the problem persists.

@WorthlessJ commented on GitHub (May 7, 2020): This might be because setting max playercount at startup is supposed to be deprecated and some weird stuff is happening. There is a example file called gamemodes_server.txt.example inside /serverfiles/csgo/ Follow the examples for setting playercount in a new gamemodes_server.txt file and see if the problem persists.

kerem commented

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

Author

Owner

@dgibbs64 commented on GitHub (Sep 26, 2020):

Assuming now working. Will auto-close if no response

@dgibbs64 commented on GitHub (Sep 26, 2020): Assuming now working. Will auto-close if no response

kerem commented

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

Author

Owner

@JamsRepos commented on GitHub (Sep 26, 2020):

There's still cases of this happening, the only fix I've found is to just restart the server and it will then rectify.

Very latest LGSM version too as I've got it automatically updating.

@JamsRepos commented on GitHub (Sep 26, 2020): There's still cases of this happening, the only fix I've found is to just restart the server and it will then rectify. Very latest LGSM version too as I've got it automatically updating.

kerem commented

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

Author

Owner

@dgibbs64 commented on GitHub (Sep 26, 2020):

Maybe restarting from a crash/lockup causes the issue and restarting again fixes it. I think this might be difficult to replicate

@dgibbs64 commented on GitHub (Sep 26, 2020): Maybe restarting from a crash/lockup causes the issue and restarting again fixes it. I think this might be difficult to replicate

kerem commented

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

Author

Owner

@dgibbs64 commented on GitHub (Dec 4, 2023):

Since CSGO is no longer available I will close

@dgibbs64 commented on GitHub (Dec 4, 2023): Since CSGO is no longer available I will close

kerem commented

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

Author

Owner

@github-actions[bot] commented on GitHub (Dec 16, 2024):

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 (Dec 16, 2024): 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.