[GH-ISSUE #495] [CSGO] Multiple csgo servers #410

Closed
opened 2026-02-27 02:01:19 +03:00 by kerem · 5 comments
Owner

Originally created by @gelleby on GitHub (Oct 13, 2015).
Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/495

What is the best way on getting multiple csgo servers.

Copying the csgoserver directory multiple times or running multiple instances from one directory?

Adding a script to the csgo server, for example:

port="27015"
sourcetvport="27020"
if [[ $2 == "war1" ]]; then
    port="27015"
    sourcetvport="27115"
fi
if [[ $2 == "war2" ]]; then
    port="27016"
    sourcetvport="27116"
fi
if [[ $2 == "war3" ]]; then
    port="27017"
    sourcetvport="27117"
fi
if [[ $2 == "war4" ]]; then
    port="27018"
    sourcetvport="27118"
fi

Or running a "startall" script, for example:


#!/bin/bash
/home/steam/csgoserver1 start
/home/steam/csgoserver2 start
/home/steam/csgoserver3 start
/home/steam/csgoserver4 start
/home/steam/csgoserver5 start
/home/steam/csgoserver6 start

That last one didnt really work on my end as it only started the first csgoserver and not the rest.
Or am I looking at this the wrong way?

What path is common for steam?

Thanks for help :)

Originally created by @gelleby on GitHub (Oct 13, 2015). Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/495 What is the best way on getting multiple csgo servers. Copying the csgoserver directory multiple times or running multiple instances from one directory? Adding a script to the csgo server, for example: ``` port="27015" sourcetvport="27020" if [[ $2 == "war1" ]]; then port="27015" sourcetvport="27115" fi if [[ $2 == "war2" ]]; then port="27016" sourcetvport="27116" fi if [[ $2 == "war3" ]]; then port="27017" sourcetvport="27117" fi if [[ $2 == "war4" ]]; then port="27018" sourcetvport="27118" fi ``` Or running a "startall" script, for example: ``` #!/bin/bash /home/steam/csgoserver1 start /home/steam/csgoserver2 start /home/steam/csgoserver3 start /home/steam/csgoserver4 start /home/steam/csgoserver5 start /home/steam/csgoserver6 start ``` That last one didnt really work on my end as it only started the first csgoserver and not the rest. Or am I looking at this the wrong way? What path is common for steam? Thanks for help :)
kerem closed this issue 2026-02-27 02:01:19 +03:00
Author
Owner

@andreblue commented on GitHub (Oct 15, 2015):

Are you running the server from the same serverfiles directory? Or are they each in their own? Did you also edit the service name in the csgoserver script? That could cause a conflict with it also

<!-- gh-comment-id:148291067 --> @andreblue commented on GitHub (Oct 15, 2015): Are you running the server from the same serverfiles directory? Or are they each in their own? Did you also edit the service name in the csgoserver script? That could cause a conflict with it also
Author
Owner

@gelleby commented on GitHub (Oct 15, 2015):

I'm doing both and wondering what option is the best.
I did not only edit the service name, I applied more scripting and logs for all 6 csgo servers.

The issue was indeed due to the service name conflict.

But I'm still wondering what option is best.
My opinion is that with running 6 csgo servers from directory, u only have to update 1 folder.
And that's a plus...

<!-- gh-comment-id:148542053 --> @gelleby commented on GitHub (Oct 15, 2015): I'm doing both and wondering what option is the best. I did not only edit the service name, I applied more scripting and logs for all 6 csgo servers. The issue was indeed due to the service name conflict. But I'm still wondering what option is best. My opinion is that with running 6 csgo servers from directory, u only have to update 1 folder. And that's a plus...
Author
Owner

@andreblue commented on GitHub (Oct 15, 2015):

If it is all the same then one should be fine but if you are running different gamemodes or modes then you may want to run it in seperate ones.

<!-- gh-comment-id:148548008 --> @andreblue commented on GitHub (Oct 15, 2015): If it is all the same then one should be fine but if you are running different gamemodes or modes then you may want to run it in seperate ones.
Author
Owner

@ScottSmudger commented on GitHub (Oct 25, 2015):

All in the same directory is a lot easier, and works fine.
Just change the service-name variable and the port(s) that the server will use the script will create separate log files for each server based on the service name.

There is no need to separate them, even if you have multiple game modes.
Plus, in the same directory is a lot easier if you ever have custom content. You can also use the autoexec.cfg file to execute the same cvars on multiple servers as they will probably have commonalities.

<!-- gh-comment-id:150964536 --> @ScottSmudger commented on GitHub (Oct 25, 2015): All in the same directory is a lot easier, and works fine. Just change the service-name variable and the port(s) that the server will use the script will create separate log files for each server based on the service name. There is no need to separate them, even if you have multiple game modes. Plus, in the same directory is a lot easier if you ever have custom content. You can also use the autoexec.cfg file to execute the same cvars on multiple servers as they will probably have commonalities.
Author
Owner

@lock[bot] commented on GitHub (Jul 19, 2018):

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.

<!-- gh-comment-id:406367319 --> @lock[bot] commented on GitHub (Jul 19, 2018): 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.
Sign in to join this conversation.
No labels
Atomic
Epic
cannot reproduce
command: backup
command: console
command: debug
command: details
command: fast-dl
command: install
command: mods
command: monitor
command: post-details
command: restart
command: send
command: start
command: stop
command: update
command: update-lgsm
command: validate
command: wipe
distro: AlmaLinux
distro: Arch Linux
distro: CentOS
distro: Debian
distro: Fedora
distro: RedHat
distro: Rocky Linux
distro: Ubuntu
distro: openSUSE
engine: goldsrc
engine: source
game: 7 Days to Die
game: ARMA 3
game: Ark: Survival Evolved
game: Assetto Corsa
game: Avorion
game: BATTALION: Legacy
game: Barotrauma
game: Battalion 1944
game: Battlefield 1942
game: Black Mesa: Deathmatch
game: Blade Symphony
game: Call of Duty 2
game: Call of Duty 4
game: Call of Duty: United Offensive
game: Counter-Strike 1.6
game: Counter-Strike 2
game: Counter-Strike: Global Offensive
game: Counter-Strike: Source
game: Day of Infamy
game: Dayz
game: Death Match Classic
game: Don't Starve Together
game: ET: Legacy
game: Eco
game: Factorio
game: Factorio
game: Garry's Mod
game: Half-Life
game: Hurtword
game: Insurgecy
game: Insurgecy
game: Insurgency: Sandstorm
game: Just Cause 3
game: Killing Floor
game: Killing Floor 2
game: Left 4 Dead 2
game: Minecraft
game: Minecraft Bedrock
game: Mordhau
game: Multi Theft Auto
game: Mumble
game: Natural Selection 2
game: No More Room in Hell
game: Pavlov VR
game: Post Scriptum
game: Project Zomboid
game: Quake 3
game: QuakeWorld
game: Red Orchestra: Ostfront 41-45
game: Return to Castle Wolfenstein
game: Rising World
game: Rust
game: San Andreas Multiplayer
game: Satisfactory
game: Soldat
game: Soldier of Fortune 2
game: Squad
game: Squad 44
game: Starbound
game: Stationeers
game: Sven Co-op
game: Team Fortress 2
game: Teamspeak 3
game: Teeworlds
game: Terraria
game: The Front
game: Unreal Tournament 2004
game: Unreal Tournament 3
game: Unreal Tournament 99
game: Unturned
game: Valheim
game: Wurm Unlimited
game: Zombie Master Reborn
game: label missing
good first issue
help wanted
info: alerts
info: dependency
info: docker
info: docs
info: email
info: query
info: steamcmd
info: systemd
info: tmux
info: website
info: website
needs more info
outcome: duplicate
outcome: issue resolved
outcome: issue resolved
outcome: issue unresolved
outcome: pr accepted
outcome: pr rejected
outcome: unconfirmed
outcome: wontfix
outcome: wrong forum
potential-duplicate
priority
pull-request
type: bug
type: feature
type: feature
type: feature request
type: game server request
type: refactor
waiting response
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/LinuxGSM#410
No description provided.