Dystopia linux dedicated server guide needed

[jmk]

I need dystopia linux dedicated server guide with steamcmd content download.

Tom said that his guide is private Soo if someone know for install clean dystopia dedicated server via steamcmd i will be grateful.

Yes im lezy and dont wanna try by myself install all SDK dedicated servers with dys content

Cheers.

[KindredPhantom]

I've requested access to the guide. I'll post the info when I get access.

Edit: Here we are.

Linux

1) If you are running a 64-bit Linux OS, you will need to download the 32-bit libraries for srcds to run (this is because srcds is a 32-bit program). To do this (login as root):
|----------------------------------------------------------------------------|
| -Debian 6, Ubuntu, Mint: |
| apt-get install ia32-libs |
| -Debian 7 Wheezy |
| dpkg --add-architecture i386 |
| apt-get update |
| apt-get install ia32-libs |
| -RHEL, Fedora, CentOS |
| yum install glibc.i686 libstd++.i686 |
|----------------------------------------------------------------------------|
2) In a user account (it is not recommended to install and run a srcds server from the root directory), Create a directory in which you want to install steamCMD and place your server build directory. I recommend something along the lines of /home/user/source.

2) In that directory that you created, download SteamCMD from Valve.
wget http://media.steampowered.com/client/st ... nux.tar.gz

3) Extract the steamCMD tar into the directory you created.
tar -xvzf steamcmd_linux.tar.gz

4) Run the steamCMD shell script
./steamcmd.sh

5) You will first need to download the 2013 Source SDK Server files. To do this, first type login anonymous. Once logged in, you will need to choose a directory to install the SDK server files. I recommend installing these files within the directory you created to for SteamCMD. To do this, type force_install_dir /home/user/source/dystopia. Finally, you will need to initialize the download. To do this, type app_update 244310. This will begin the download.
|----------------------------------------------------------------------------|
| tl;dr: Install Source 2013 SDK Server Files |
| login anonymous |
| force_install_dir [directory] |
| app_update 244310 |
|----------------------------------------------------------------------------|
6) Once the SDK server files have finished downloading, close out of SteamCMD. You will now have to reopen SteamCMD. This time, you will need to login to an account that has the Dystopia 1.4 Game Content. To do this, type Login [Your Steam Username]. You will then be prompted to type in your password. If this is the first time you have logged into SteamCMD from that location, you will need to check your e-mail for the Steam Guard code. Once you input the Steam Guard Code, you should be logged in. Now you will need to choose that directory where to install the Dystopia Beta Game Files. This directory must be the same directory where you installed the Source 2013 SDK Server Files. To do this, type force_install_dir [Same Directory as the 2013 SDK Content]. Finally, you will need to download the game content by typing app_update 17580. At this point, the download should begin. Do not close out of SteamCMD until the download has completed.
|----------------------------------------------------------------------------|
| tl;dr: Install Dystopia 1.4 Game Files |
| login [Your Steam Username |
| force_install_dir [Same as 2013 SDK] |
| app_update 17580 |
|----------------------------------------------------------------------------|
7) Once the downloads have completed, there will be a few more things you will need to do. Create a server.cfg file and place it in your /home/user/source/dystopia/dystopia/cfg directory. A sample server.cfg file can be found down below.

You are now ready to start your Dystopia 1.4 Linux Dedicated Server. To do this, you will need to decide your command line options and then execute srcds_run. (See below for additional command line options).
an example start up command line
./srcds_run -game dystopia +map dys_silo +maxplayers 16 -insecure

[jmk]

--------------------------------------------------------
sv_pure value unchanged (current value is 0).
--------------------------------------------------------
Network: IP 5.9.48.231, mode MP, dedicated Yes, ports 32000 SV / 27005 CL
Error loading cfg/trusted_keys_base.txt
[DYSTOPIA_STATS] Trying to connect to the stats server... (0/5)
Segmentation fault (core dumped)
Add "-debug" to the ./srcds_run command line to generate a debug.log to help with solving this problem
Mon Apr 13 18:57:11 CEST 2015: Server restart in 10 seconds
Mon Apr 13 18:57:17 CEST 2015: Server Quit

uname -a
Linux Debian-78-wheezy-64-minimal 3.2.0-4-rt-amd64 #1 SMP PREEMPT RT Debian 3.2.65-1+deb7u2 x86_64 GNU/Linux

ldd --version
ldd (Debian GLIBC 2.19-17) 2.19

[KindredPhantom]

--------------------------------------------------------
sv_pure value unchanged (current value is 0).
--------------------------------------------------------
Network: IP 5.9.48.231, mode MP, dedicated Yes, ports 32000 SV / 27005 CL
Error loading cfg/trusted_keys_base.txt
[DYSTOPIA_STATS] Trying to connect to the stats server... (0/5)
Segmentation fault (core dumped)
Add "-debug" to the ./srcds_run command line to generate a debug.log to help with solving this problem
Mon Apr 13 18:57:11 CEST 2015: Server restart in 10 seconds
Mon Apr 13 18:57:17 CEST 2015: Server Quit

uname -a
Linux Debian-78-wheezy-64-minimal 3.2.0-4-rt-amd64 #1 SMP PREEMPT RT Debian 3.2.65-1+deb7u2 x86_64 GNU/Linux

ldd --version
ldd (Debian GLIBC 2.19-17) 2.19

From looking at it, I think the issue is that the server cannot connect to the stats server?

I am unfamiliar with Linux, and server hosting so I can be of little help to you.

[Atomy]

Uhhm, strange. Can you ldd the executable? Must be srcds_i486 or something like that. Maybe you got even gdd on it and can run the server using gdd?

[Tom Sawyer]

Impossible to determine issue without knowing the command line used and the full server output once the command has been executed. I can assure the Dystopia stats server connection isn't causing the issue (Server usually never connects to stats on first attempt, server utilizes 5 attempts to connect, and if it doesn't connect, the server is still playable).

Add "-debug" to the ./srcds_run command line to generate a debug.log to help with solving this problem

Hopefully you've done this at least, since the output told you to. It will give you the full output of the server once executed and crashed (In case you're freaking out that your linux screen only displays so many lines).

If I were to take a stab in the dark as to what this issue is, I would say you either didnt follow the directions correctly (for instance, pulling 17580 before 244310 will cause an issue), You are missing additional libraries for srcds (You're using a minimal installation, common linux libraries found on other linux distros used by srcds may have been stripped from your version), You're attempting to launch srcds from root user from the root directory or you missed/mistyped important launch parameters at execution ( -ip, not +ip // -port not +port // +map not -map // +maxplayers not -maxplayers (Unlike windows, using the + or - prior to flag is important).

But again, this is all a stab in the dark. Your output you posted doesnt REALLY have any useful information.

[Tom Sawyer]

Side note: If you're trying to utilize sourcemod BEFORE the first successful launch of a vanilla dystopia server, then ignore everything that has been stated above, remove all sourcemod files (or let's be honest, any plugin), and start again.

Future Note to sourcemod users: Sourcemod has not had any OFFICIAL support for dystopia since version 1.2. Yes, sourcemod can still be used with dystopia, however as of a year ago (last time I put any form of testing toward it, which was absolutely minimal) only a beta dev release of sourcemod was configurable to dystopia/source sdk 2013. And even then, half of the plugins and admin controls were incompatible with dystopia, and any changes made to the sdk or sourcemod itself since then can cause even less compatibility.

And if you're thinking, Tom, everyone uses sourcemod, you're just over reacting, Feel free to google search sourcemod seg faults, and let the horrors of sourcemod and plugins plague your mind. Yes it works with counter strike or team fortress, as it has gotten support for those games. New source games and mods typically don't get such support unless its a big name source title or has active community development, which dystopia is neither.

[Tom Sawyer]

Second Side Note (I should have noticed this before)

ports 32000 SV / 27005 CL

Are you purposefully trying to bind your server port to 32000? If you are, I don't recommend it (I don't even know if steam auth will communicate with this port). However, I doubt you are, which means one of two things:

1) Your server is not binding to the correct port. This is either caused by not defining a port in your command line while another server is currently occupying default (27015)

2) If your server has multiple IP's and you did not define the ip in the command line, srcds with default to whatever ip is used in eth0 in your network configuration, which in some instances, may not have the ports forwarded for that particular IP.

This, however, may not be THE issue, but it very well may be an issue if you are not purposefully trying to bind to 32000 (which, for srcds, you really should stick to something in or around the 27015-27050 range).

You don't always have to define ip and port in the command line, but you should get in the habit of always defining IP and Port regardless.