Ask questions about dedicated servers here and we and other users will do our best to answer them. Please also refer to the self-help section for tutorials and answers to the most commonly asked questions.
The guide asks me to download Steam, extract it and then run a script. I have no issues until I attempt to run the script, here is what happens
steam@***:~/steam-server$ ls linux32steamcmd_linux.tar.gz steamcmd_linux.tar.gz.1 steamcmd.sh steam.sh
steam@***:~/steam-server$ ./steamcmd.sh
./steamcmd.sh: line 29: /home/steam/steam-server/linux32/steamcmd: No such file or directory
I've spoken with one support member and we attempted this
This fixed it, thanks for the help! Sorry to bother everyone with this simple stuff, still new to all of this. Hopefully there aren't any more road blocks
If I didn't say it already, I am brand new to dedicated servers. Again I followed the tutorial exactly. I connected via ftp and added a server.cfg file with the correct info. After this I ran the server again with ./tf2-startup.sh
I am unsure what it means, but I get these messages afterwards
WARNING: Port 27015 was unavailable - bound to port 27016 instead
WARNING: Port 27005 was unavailable - bound to port 27006 instead
WARNING: Port 27020 was unavailable - bound to port 27021 instead
Also, I'm sure it's related somehow, I am unable to connect to the server in game.
I really don't know what to do here as I'm "limited" to the amount of support I can get since my plan is not managed.
That error would indicate that something is already running on those ports. Did you setup a second instance by chance? It really shouldn't be a big issue since it re-bound itself to different ports automatically, unless you want the stock ports.
@Kraze^NFo> Juski has a very valid point
@Juski> Got my new signature, thanks!
@Kraze^NFo> Out of context!
@Juski> Doesn't matter!
@Juski> You said I had a valid point! You can't take it back now! It's out there!
kraze wrote:That error would indicate that something is already running on those ports. Did you setup a second instance by chance? It really shouldn't be a big issue since it re-bound itself to different ports automatically, unless you want the stock ports.
It ended up rebinding to port 27018 and I have since managed to connect to the server in game with that port. I honestly wouldn't know if I setup a second or maybe even a third instance unless using the command ./tf2-startup.sh multiple times does that. In which case yeah I probably did. Is there a way to remove those instances?
You can use the PID(Process Identification Number)s in netstat to shut them down I think, I usually use screen, which seems more convenient and user-friendly.
To shut a process using the PID, find the number and type this in putty:
I see. I've killed all of those processes. I'm still trying to figure out how to correctly make two game servers run. After speaking to a support person, I copied the entire tf2 directory and renamed it to tf2_2 (for the 2nd game server). I then came to the conclusion that one startup script which was above both directories would probably result in two identical servers or something. What I've done is removed the script and placed one inside both tf2 directories, each defining its own IP, port and map.
Now it seems that I run into the port errors again and I am connecting to the servers via ports other than 27015. I've sshd into each directory and executed the tf2-startup.sh.
phaiz wrote:
If both game servers have different IPs, can they use the same port? (27015)
Yes, each IP can have it's own set of ports, if you have 2 different IPs then you can use 27015 port for both.
To me your srcds process starts on it's own or it's not terminated properly. Did you setup any auto-start scripts? Did you try to restart your machine in between, if not then give it a shot as well.
You can get strange errors like this, joshh20 if you're reading this, make installing 32-bit binaries step 1! 
