starred/LinuxGSM

Fork 0

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

[GH-ISSUE #2473] [BUG] Port conflict witth two or more servers #1822

New issue

Open

opened 2026-02-27 02:59:13 +03:00 by kerem · 2 comments

kerem commented

2026-02-27 02:59:13 +03:00

Owner

Originally created by @BlackYuzia on GitHub (Aug 13, 2019).
Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/2473

User Story

I try install 3 the same game servers (CS:GO).
I create user, next I create different folders for server.

Example: Server №1 have folder Server_1, Server №2 have folder Server_2 etc

Each server has its own folder in which are configs and server files.

path to the configs: ~/Server_{1,2,3}/lgsm/config-lgsm/csgoserver/csgoserver.cfg.

In each of the server configs I registered unique settings (like a port, slots, sourcetv port, client port, gslt token etc).

Let me remind you that each server has a separate folder, as well as a separate config.

When, I try run server

command would like: bash ~/SERVER_{1,2,3}/csgoserver start

I get some weird results.
One (of the three) server was run (active). Other (2) was shutdown.
I think this is my mistake.

I try run check console of server.

I check console servers (./csgoserver console) [I did it three times]

When I check ports of server, I get three times the same port (25015).

Next time, when I stoped all servers and run second server first and next other both, I get three the same ports (but not 25015 is it 26015).

So, bug can be -> When you try run two or more servers from one user, you get the same ports. OR, If I right. You just get one tmux window from and for third config/setup files (csgoserver).

Basic info

Distro: [Debian 9]
Game: [CS:GO]
Commands: [start, console]

Further Information

This can be bug with ~~tmux~~ [Same tmux window name] or
bug with ports [lgsm setup settings from first csgoserver.cfg for all other servers]

How I fix it?
Just rename csgoserver => csgoserver + number of server.

Example: ~/Server_1/csgoserver1 | ~/Server_2/csgoserver2 | ~/Server_3/csgoserver3

I'm not sure if this should be so. Perhaps the developers had no other solution than to change the name of the boot file. If so, then a bug with ports is a feature

To Reproduce

Steps to reproduce the behaviour:

Use mkdir to create third different folders.
Download linuxgsm.sh script.
Copy linuxgsm.sh file to third folders.
Run and download csgoserver file (third times).
Download and setup csgo servers.
Don't forget setup different ports for servers.
Run servers with a start command.
Get the same port for different servers with dirrenent folders.

For fix that:
9. Rename csgoserver => csgoserver + server number => csgoserver1 or csgoserver2 etc

Expected behaviour

If this is "feature", I was expect message, like

HEY YOU, YEP, YOU! YOU RUN SERVER WITH THE SAME TMUX WINDOW?
RENAME THIS SHIT TO DIFFERENT OR I SWEAR YOU WILL HAVE SERIOUS TROUBLES!

If this is BUG, I was expect NO BUG :D
~~So, Call it feature. Feature != bug, Fixed! Hey!~~

Originally created by @BlackYuzia on GitHub (Aug 13, 2019). Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/2473 ## User Story I try install 3 the same game servers (CS:GO). I create user, next I create different folders for server. > Example: Server №1 have folder Server_1, Server №2 have folder Server_2 etc Each server has its own folder in which are configs and server files. > path to the configs: ~/Server_{1,2,3}/lgsm/config-lgsm/csgoserver/csgoserver.cfg. In each of the server configs I registered unique settings (like a port, slots, sourcetv port, client port, gslt token etc). **Let me remind you that each server has a separate folder, as well as a separate config.** When, I try run server > command would like: bash ~/SERVER_{1,2,3}/csgoserver start I get some weird results. One (of the three) server was run (active). Other (2) was shutdown. I think this is my mistake. I try run check console of server. I check console servers (**./csgoserver console**) [I did it three times] When I check ports of server, I get three times the same port (25015). Next time, when I stoped all servers and run second server first and next other both, I get three the same ports (but not 25015 is it 26015). So, bug can be -> **When you try run two or more servers from one user, you get the same ports.** OR, If I right. **You just get one tmux window from and for third config/setup files** (**csgoserver**). ## Basic info * Distro: [Debian 9] * Game: [CS:GO] * Commands: [start, console] ## Further Information This can be bug with ~~tmux~~ [Same tmux window name] or bug with ports [lgsm setup settings from first `csgoserver.cfg` for all other servers] How I fix it? Just rename csgoserver => csgoserver + number of server. > Example: ~/Server_1/csgoserver1 | ~/Server_2/csgoserver2 | ~/Server_3/csgoserver3 _I'm not sure if this should be so. Perhaps the developers had no other solution than to change the name of the boot file. If so, then a bug with ports is a feature_ ## To Reproduce Steps to reproduce the behaviour: 1. Use `mkdir` to create third different folders. 2. Download `linuxgsm.sh` script. 3. Copy `linuxgsm.sh` file to third folders. 4. Run and download csgoserver file (third times). 5. Download and setup csgo servers. 6. Don't forget setup different ports for servers. 7. Run servers with a `start` command. 8. Get the same port for different servers with dirrenent folders. For fix that: 9. Rename csgoserver => csgoserver + server number => csgoserver1 or csgoserver2 etc ## Expected behaviour If this is "feature", I was expect message, like >HEY YOU, YEP, YOU! YOU RUN SERVER WITH THE SAME TMUX WINDOW? RENAME THIS SHIT TO DIFFERENT OR I SWEAR YOU WILL HAVE SERIOUS TROUBLES! If this is **BUG**, I was expect **NO BUG** :D ~~So, Call it **feature**. Feature != bug, Fixed! Hey!~~

kerem added the

type: bug

label

2026-02-27 02:59:13 +03:00

kerem commented

2026-02-27 02:59:14 +03:00

Author

Owner

@issue-label-bot[bot] commented on GitHub (Aug 13, 2019):

Issue-Label Bot is automatically applying the label type: feature request to this issue, with a confidence of 0.69. 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 (Aug 13, 2019): Issue-Label Bot is automatically applying the label `type: feature request` to this issue, with a confidence of 0.69. 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 02:59:14 +03:00

Author

Owner

@BlackYuzia commented on GitHub (Aug 13, 2019):

Wow, Why this is feature request? :c

I missed up or bot just helps developers answer me 😄

@BlackYuzia commented on GitHub (Aug 13, 2019): Wow, Why this is feature request? :c I missed up or bot just helps developers answer me :smile:

kerem referenced this issue

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

[PR #1822] [MERGED] New fix for Rust #3412