[GH-ISSUE #576] Cannot run two servers at once #463

New issue

Closed

opened 2026-02-27 02:01:40 +03:00 by kerem · 2 comments

kerem commented

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

Owner

Originally created by @LinhyCZ on GitHub (Dec 23, 2015).
Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/576

Today i tried to setup second server. I made a second user (csgoserver2) and downloaded script and installed game.. On first server I have ports 27000, 27001 and 27002. On second I have 27997, 27998 and 27999. I can't get it to work simultaneously. When I launch first server, second shuts down and when I launch second, first shuts down. On the second server I changed service name to csgo-server2. I have cronjob monitoring servers every 5 minutes. On first server it can't query that port, second is not running.. I have no clue, where could be an issue..

Originally created by @LinhyCZ on GitHub (Dec 23, 2015). Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/576 Today i tried to setup second server. I made a second user (csgoserver2) and downloaded script and installed game.. On first server I have ports 27000, 27001 and 27002. On second I have 27997, 27998 and 27999. I can't get it to work simultaneously. When I launch first server, second shuts down and when I launch second, first shuts down. On the second server I changed service name to csgo-server2. I have cronjob monitoring servers every 5 minutes. On first server it can't query that port, second is not running.. I have no clue, where could be an issue..

kerem closed this issue

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

kerem commented

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

Author

Owner

@LinhyCZ commented on GitHub (Dec 23, 2015):

Was my fault, missed, that I was using one auth token for two servers.. LOCK

@LinhyCZ commented on GitHub (Dec 23, 2015): Was my fault, missed, that I was using one auth token for two servers.. LOCK

kerem commented

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

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.

@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.