Hey I've been working on a TF2 linux dedicated server using linuxgsm installer and I've been able to deploy it. However, when I made a 2nd server and I want to start it, I only get this error and crashes the server:
https://imgur.com/a/gJtOGNa
The first server is using the 27015 port and I did use another port for the 2nd server, which is 27016. Any idea what's left to check?
Thanks
Hey I've been working on a TF2 linux dedicated server using linuxgsm installer and I've been able to deploy it. However, when I made a 2nd server and I want to start it, I only get this error and crashes the server:
[img]https://imgur.com/a/gJtOGNa[/img]
The first server is using the 27015 port and I did use another port for the 2nd server, which is 27016. Any idea what's left to check?
Thanks
maneHey I've been working on a TF2 linux dedicated server using linuxgsm installer and I've been able to deploy it. However, when I made a 2nd server and I want to start it, I only get this error and crashes the server:
https://imgur.com/a/gJtOGNa
The first server is using the 27015 port and I did use another port for the 2nd server, which is 27016. Any idea what's left to check?
Thanks
27020 is the default port for STV iirc
[quote=mane]Hey I've been working on a TF2 linux dedicated server using linuxgsm installer and I've been able to deploy it. However, when I made a 2nd server and I want to start it, I only get this error and crashes the server:
[img]https://imgur.com/a/gJtOGNa[/img]
The first server is using the 27015 port and I did use another port for the 2nd server, which is 27016. Any idea what's left to check?
Thanks[/quote]
27020 is the default port for STV iirc
You likely have a detatched srcds instance running. Kill all running srcds instances with
sudo pkill srcds -9 -e
(assuming bash)
set +tv_port in your startup options so servers dont overlap as well
should fix it
i would also recommend having your tv_port = your server port + 1, as it makes it easy to scale in the future
You likely have a detatched srcds instance running. Kill all running srcds instances with
sudo pkill srcds -9 -e
(assuming bash)
set +tv_port in your startup options so servers dont overlap as well
should fix it
i would also recommend having your tv_port = your server port + 1, as it makes it easy to scale in the future
Solved it. I found the right server config of that server instance and changed the port to 27016 etc
However, now my etf2l whitelist is not being read. I used TFTRUE whitelist and the weapons restrictions don't apply, however, a lot of the hats get blocked. Any idea why?
Solved it. I found the right server config of that server instance and changed the port to 27016 etc
However, now my etf2l whitelist is not being read. I used TFTRUE whitelist and the weapons restrictions don't apply, however, a lot of the hats get blocked. Any idea why?
uhhh looks like i'm late on the party but i think way easier solution to get competitive servers on your host would be using docker containers made by mały:
https://github.com/melkortf/tf2-servers
everything is prebuilt already and all you need to do is to pass variables like what ports do you want to have, your api for logs.tf/demos.tf, passwords etc, example:
https://docs.tf2pickup.org/docs/site-components-deployment#gameserver_1env
uhhh looks like i'm late on the party but i think way easier solution to get competitive servers on your host would be using docker containers made by mały:
https://github.com/melkortf/tf2-servers
everything is prebuilt already and all you need to do is to pass variables like what ports do you want to have, your api for logs.tf/demos.tf, passwords etc, example:
https://docs.tf2pickup.org/docs/site-components-deployment#gameserver_1env
Solved it. somehow. I grabbed the pack of cfgs from etf2l and re-executed it(6v6), so with the tftrue whitelist and it worked. Some hats are still blocked but the weapons whitelist is working.
Solved it. somehow. I grabbed the pack of cfgs from etf2l and re-executed it(6v6), so with the tftrue whitelist and it worked. Some hats are still blocked but the weapons whitelist is working.