[Bug]: server-2.cfg not processed by 2d gameserver instance (Single Installation with Multiple Instances)

[Hubfront]

User story

Server-2.cfg is created by LinuxGSM, but not used by 2d server instance

Game

Left 4 Dead 1

Linux distro

Ubuntu 20.04

Command

command: install

Further information

I followed https://docs.linuxgsm.com/configuration/multiple-game-servers and did a single install with multiple instances. After installing the first instance several weeks ago, i now decided to add a new instance: i did run

~/linuxgsm.sh install

and both ./l4dserver-2 and ~/lgsm/config-lgsm/l4dserver/l4dserver-2.cfg were created for the new second instance.

After that i edited ~/ lgsm/config-lgsm/l4dserver/l4dserver-2.cfg and added there a different port for the new instance (27016) and the file name for the server configuration: "server-2.cfg":

port="27016"
clientport="27006"
servercfg="server-2.cfg"
servercfgfullpath="${servercfgdir}/${servercfg}"

After first start of the new instance, the server-2.cfg was created in the ~/serverfiles/l4dserver/cfg/ directory.

I copied the content fo the old server: "server.cfg" to server-2.cfg and changed there host name, among other things, to “New name”. Stop and start:

./l4dserver-2 stop
[..]
./l4dserver-2 start
[OK] Starting l4dserver-2: New name

So ./l4dserver-2 recognizes the new server-2.cfg, read it and states the new name of the instances on startup. But after going to console:

./l4dserver-2 console

to my surprise, the old server name "Old Name" was displayed there:

status
hostname: Old name
version : 1.0.4.1 8483 secure (unknown)
udp/ip : 0.0.0.0:27016 [ public 185.248.140.40:27016 ]
os : Linux Dedicated
map : l4d_smalltown02_drainage
players : 0 humans, 0 bots (4 max) (hibernating) (unreserved)

Checking on an external server browser (steambrowser.com) confirms this for the new port 27016 on same IP as the old instance.

Possible bug:
So, LinuxGSM apparently takes the changes to server-2.cfg into account correctly for the new game server instance, and the new instance runs on the new port 27016 in parallel to the old instance, but unfortunately the gameserver itself still uses the server.cfg of the old instance.

Relevant log output

No response

Steps to reproduce

1. Install first and second gameserver instance with ./linuxgsm install
2. Edit l4dserver-2.cfg for new port and new server configuration file: server-2.cfg
3. Start up new instance: ./l4dserver start and stop it ./l4dserver stop
4. Edit newly created server-2.cfg in ~/serverfiles/l4dserver/cfg/: add new hostname
5. ./l4dserver start
6. ./l4dserver console
7. status
8. verify, that hostname is still the one of old instance, but with new port 27016

[Hubfront]

Config files: server.cfg (old instance on 27015), l4dserver-2.cfg (new instance on 27016) and server-2.cfg:

configfiles.zip

Update 06.03.2024: I solved this problem by avoiding creating additional server.cfg files. For all other cases I just use the first one (other ports only). This issue has been closed.

I would also like to thank the creator and supporter of LinuxGSM.