Toggle search
Toggle menu
TF2 Classified Wiki
Toggle preferences menu
Toggle personal menu
Not logged in
Your IP address will be publicly visible if you make any edits.

User:Webb/New linux server: Difference between revisions

From TF2 Classified Wiki
More actions
← Older edit

Webb (talk | contribs)

97 edits
Webb (talk | contribs)
97 edits
No edit summary
Webb (talk | contribs)
97 edits
No edit summary
 
(7 intermediate revisions by the same user not shown)
Line 1: Line 1:
:''This is a WIP updated version of the Linux dedicated server article. I want to ask for feedback before moving out of my user namespace. The original article was adapted and revised from a guide written by Raizo, the original of which can be found here: https://blog.raizo.dev/posts/tf2-classic-linux-server-tutorial/''
:''This article is based on a guide written by Raizo, the original of which can be found [https://blog.raizo.dev/posts/tf2-classic-linux-server-tutorial/ here].''


== Prerequisites ==
== Reading this article ==
 
* A Linux server running Ubuntu Server<sup>*</sup> on an x86_64 CPU<sup>**</sup> with root/administrator access
* A SFTP/SSH client (PuTTY, Termius, FileZilla, MobaXterm)
* At least 20GB of free storage
* A minimum of a 10Mbps upload speed if you intend on hosting a server over the Internet. More bandwidth may be needed if custom maps are used.
 
<sup>*</sup> This guide was written for and tested on Ubuntu Server 24.04 LTS Minimal. Other distros may use different package names and conventions.
 
<sup>**</sup> Using an x86 compatibility layer like Box86 for another architecture is unsupported and may not work.
 
=== Reading this article ===
<!-- Originally from https://wiki.teamfortress.com/wiki/Linux_dedicated_server#Reading_this_article -->
<!-- Originally from https://wiki.teamfortress.com/wiki/Linux_dedicated_server#Reading_this_article -->
A command prefixed by <code>#</code> is meant to be run as '''root'''.
A command prefixed by <code>#</code> is meant to be run as '''root'''.
Line 22: Line 11:
Some commands are listed in-line with the rest of a paragraph and lack this symbol, in which case you should run the command as whichever account you're currently logged in with.
Some commands are listed in-line with the rest of a paragraph and lack this symbol, in which case you should run the command as whichever account you're currently logged in with.


=== Creating a user for the server ===
== Prerequisites ==
 
* A Linux server running Ubuntu Server<sup>*</sup> on an x86_64 CPU<sup>**</sup> with root access
* At least 20GB of free storage
* A minimum of a 10Mbps upload speed if you intend on hosting a server over the Internet, more will be needed if you host custom content
* An opened port on your firewall for the server
* ''Optional'': An SSH/SFTP client if doing remote access/file management
* ''Optional'': A port that's been forwarded for the server if you wish to have it accessible over the internet


Pick a directory to install your server into. Many put it under a directory in <code>/opt</code>, but for this guide we'll be using <code>/home/srcds</code>.
<sup>*</sup> This guide was written for and tested on Ubuntu Server 24.04 LTS Minimal. Other distros may use different package names and conventions.


Create a disabled user with a home directory:
<sup>**</sup> Using an x86 compatibility layer like Box86 for another architecture is unsupported and may not work.


<pre>
== Preparing for install ==
# useradd -s /bin/false -mr srcds
</pre>


<code>-m</code> creates a home directory for the new user, <code>-r</code> specifies that it's a system account that will not have a password, and <code>-s /bin/false</code> prevents the account from having a default shell.
=== Dependencies ===


=== Installing Source SDK Base 2013 Dedicated Server (<code>srcds</code>), SteamCMD, and dependencies ===
We'll need to install some required packages and tools for our server to work, as well as for installation.


The SteamCMD package is in the multiverse repos. TF2Classic and SteamCMD require i386 (32-bit) libraries to function. You also need 7-Zip to extract TF2Classic.
Since the legacy TF2C branch, Source SDK, and SteamCMD are built for 32-bit, we'll need to enable 32-bit packages. We'll also add the <code>multiverse</code> repository which has SteamCMD.


<pre>
<pre>
Line 44: Line 38:
</pre>
</pre>


Install SteamCMD, and miscellaneous packages that we'll be using.
Next, we'll install the <code>dialog</code> package so the Steam Subscriber Agreement dialog works, and then the rest of the packages we need.


<pre>
<pre>
Line 50: Line 44:
# apt install steamcmd p7zip aria2 tilde lib32z1 libbz2-1.0:i386 lib32gcc-s1 lib32stdc++6 libcurl3-gnutls:i386 libsdl2-2.0-0:i386 wget
# apt install steamcmd p7zip aria2 tilde lib32z1 libbz2-1.0:i386 lib32gcc-s1 lib32stdc++6 libcurl3-gnutls:i386 libsdl2-2.0-0:i386 wget
</pre>
</pre>
''<sup>*</sup>'''Note''':See [https://developer.valvesoftware.com/wiki/SteamCMD#Package_From_Repositories|Valve Developer Wiki SteamCMD Repository Packages] if your distro is having issues getting steamcmd.
''


If your version of Ubuntu doesn't come with a text editor, you may install one now. For this guide we'll use <code>nano</code>.
If your version of Ubuntu doesn't come with a text editor, you may install one now. For this guide we'll use <code>nano</code>.
Line 57: Line 49:
<pre># apt install nano</pre>
<pre># apt install nano</pre>


Switch to the srcds user you created:
=== Creating a user for the server ===
 
Pick a directory to install your server into. Many put it under a directory in <code>/opt</code>, but for this guide we'll be using <code>/home/srcds</code>.
 
Create a disabled user with a home directory.
 
<pre>
# useradd -s /bin/false -mr srcds
</pre>
 
<code>-m</code> creates a home directory for the new user, <code>-r</code> specifies that it's a system account that will not have a password, and <code>-s /bin/false</code> prevents the account from having a default shell.
 
=== Installing Source SDK Base 2013 Dedicated Server (SDK 2013) ===
 
Switch to the new <code>srcds</code> user you made, and run SteamCMD.


<pre>
<pre>
Line 66: Line 72:
</pre>
</pre>


You should be dropped into a SteamCMD shell. We can install the SDK now. Note that <code>force_install_dir</code> must be ran before <code>login anonymous</code>.
You should be dropped into a SteamCMD shell. We can install the SDK 2013 now. Note that <code>force_install_dir</code> must be ran before <code>login anonymous</code>.


<pre>
<pre>
Line 76: Line 82:


If everything went well, <code>srcds</code> should be installed and you should be back at your user shell.
If everything went well, <code>srcds</code> should be installed and you should be back at your user shell.
Before we continue we'll need to fix some files.


== Installing TF2C ==
Valve changed some shared object file names in the SDK, but the objects included with our install of SDK 2013 have not adopted the new names.  
 
Since these are simply renames, we can symlink them.  
We'll be downloading the archived verison of TF2C. You also have the option of using TF2CDownloader.
 
<pre>
$ wget https://wiki.tf2classic.com/archive/tf2classic-2.2.3.zip -O /tmp/tf2classic.zip
$ mkdir ~/sdk/tf2classic
$ cd ~/sdk/tf2classic
$ 7z x /tmp/tf2classic.zip && rm /tmp/tf2classic.zip
</pre>


This will downloaded the latest archive of TF2C, create its directory, and extract it. If extraction succeeds it will delete tf2classic.zip.
=== Create symlinks to missing shared objects. ===
Valve changed some shared object file names in the SDK and the objects we’re given have not adapted to the new names. Since these are simply renames, we can symlink them.
'''Your server will not start without doing this.'''
'''Your server will not start without doing this.'''
Run the following commands to create the symlinks in the bin folder:


<pre>
<pre>
Line 110: Line 101:
$ ln -s vphysics_srv.so vphysics.so
$ ln -s vphysics_srv.so vphysics.so
$ ln -s soundemittersystem_srv.so soundemittersystem.so
$ ln -s soundemittersystem_srv.so soundemittersystem.so
$ cd ~/sdk/tf2classic/bin
$ ln -s server.so server_srv.so
</pre>
</pre>


We can also fix steamclient.so errors by symlinking a file to .steam.
Finally, we'll also symlink <code>steamclient.so</code> to a special directory to prevent bugs.


<pre>
<pre>
$ mkdir -p ~/.steam/sdk32
$ mkdir -p ~/.steam/sdk32
$ ln -s ~/sdk/bin/steamclient.so ~/.steam/sdk32/
$ ln -s ~/sdk/bin/steamclient.so ~/.steam/sdk32/
</pre>
== Installing TF2C ==
We'll be downloading the archived verison of TF2C, since it's unlikely to get updates. You have the option of using TF2CDownloader, but we won't cover it here.
<pre>
$ wget https://wiki.tf2classic.com/kachemak/tf2classic.zip -O /tmp/tf2classic.zip
$ mkdir ~/sdk/tf2classic
$ cd ~/sdk/tf2classic
$ 7z x /tmp/tf2classic.zip && rm /tmp/tf2classic.zip
</pre>
This will download the latest archive, create its directory, and extract it. If extraction succeeds it will also delete the downloaded archive.
We'll also need to do a quick symlink in TF2C's bin folder.
<pre>
$ cd ~/sdk/tf2classic/bin
$ ln -s server.so server_srv.so
</pre>
</pre>


Line 134: Line 143:
== Server Configuration ==
== Server Configuration ==


Generate your server config(s) on [https://cfg.tf/ cfg.tf].
For a basic, private server, you should only need to set a password in <code>sdk/tf2classic/cfg/server.cfg</code> by appending the file with <code>sv_password yourpassword</code>.
You can also make it LAN-only by appending <code>sv_lan 1</code> in the same file.
 
If you want a more complicated setup, consider using [https://cfg.tf/ cfg.tf]. If you don't need this you can skip to the next section.


Make sure the server type is set to “Internet and LAN” if you want players outside your LAN to be able to join (you may need to port forward if you’re on consumer broadband or open ports on your firewall).
Make sure the server type is set to “Internet and LAN” if you want players outside your LAN to be able to join (you may need to port forward if you’re on consumer broadband or open ports on your firewall).


Upload the generated ZIP file to your server using SFTP, unzip the folder using:
Upload the generated ZIP file to your server, perhaps using SFTP, and unzip the folder.


<pre>
<pre>
Line 151: Line 163:
</pre>
</pre>


== Running the server via Systemd ==
== Managing the server via Systemd ==


Systemd is a program that will automatically handle things like logging, restarts, and starting your server when your machine boots. We'll use this to run our server, instead of manually running commands.
Systemd is a program that will automatically handle things like logging, restarts, and starting your server when your machine boots. We'll use this to run our server, instead of manually running commands.
Line 157: Line 169:
=== Creating an SDK 2013 update script ===
=== Creating an SDK 2013 update script ===


We're going to create a script that will update our SDK 2013 for us instead of typing it out manually each time. Later, we'll optionally use this script to check and update SDK 2013 on our server automatically when the server starts.  
We're going to create a script that will update SDK 2013 for us instead of typing it out manually each time. Later, we'll optionally use this script to check and update SDK 2013 on our server automatically when the server starts.  


First, let's create a directory for the script.
First, let's create a directory for the script.
Line 186: Line 198:
=== Creating a service file ===
=== Creating a service file ===


Create a service file in <code>/etc/systemd/system/</code> as root.
Create a service file in <code>/etc/systemd/system/</code> as root. For this guide we'll use <code>/etc/systemd/system/tf2c.service</code>.


Example <code>tf2c.service</code>:
<pre>
<pre>
[Unit]
[Unit]
Description=TF2C
Description=TF2C Server
After=network-online.target
After=network-online.target
Wants=network-online.target
Wants=network-online.target
Line 207: Line 218:
TimeoutStartSec=infinity
TimeoutStartSec=infinity
Restart=always
Restart=always
[Install]
WantedBy=multi-user.target


[Install]
[Install]
Line 215: Line 223:
</pre>
</pre>


Then, enable the service to start with Systemd.
Then, enable the service to start with Systemd on boot.


<pre>
<pre>
# systemctl enable tf2c.service
# systemctl enable tf2c.service
</pre>
</pre>
You may create as many services as you have TF2C servers but remember to name the service files uniquely. When modifying service files, remember to run <code>systemctl daemon-reload</code> before restarting the service.


=== Automatic restarts using crontab ===
=== Automatic restarts using crontab ===


As root, execute <code>crontab -e</code>. This will open a special file where you can set cronjobs. For example, adding the following line will restart your game server every day at 04:00:
Cron is a program built into most Linux distros that runs scheduled commands.
 
As root, execute <code>crontab -e</code>. This will open a special file in your editor where you can declare what jobs you want to run and when. Let's add a job to run at 04:00 that will restart our server.


<pre>
<pre>
Line 229: Line 241:
</pre>
</pre>


You may create as many services as you have TF2C servers but remember to name the service files uniquely, enable them in <code>systemctl</code>, and add them to the <code>crontab</code>.
=== Manually managing services ===
 
=== Systemd manual start, stop, restart/update ===


If you don't wish to use the service files above to automatically boot servers, or you need to perform these actions for maintenance: you may issue commands to manually ''start'', ''stop'', ''restart'', or ''update'' the server(s) through systemd.  
If you don't wish to use the service files above to automatically boot servers, or you need to perform these actions for maintenance: you may issue commands to manually ''start'', ''stop'', ''restart'', or ''update'' the server(s) through systemd.  
Retrieved from "https://wiki.tf2classified.com/wiki/User:Webb/New_linux_server"