Bearbeiten von „Linux Server“

{{cleanup|date=18.10.2016|Reason=Outdated}}
{{übersetzen}}

This tutorial will guide you through the steps required to setup a dedicated 7DTD server on Linux. The tutorial is currently targeted to the Alpha 7.9 release which seems to work as fine on Linux as it does on Windows.

Part of this tutorial are:
* Setup of 7DTD as dedicated server
* Startup/stop scripts, also for automatic start on system boot
* Memory usage monitoring / limit exceeding notification by mail or XMPP/Jabber (optional)
* Automatic save backups (optional)

The steps and used software in this tutorial apply to a Debian Squeeze (6) or Debian Wheezy (7) installation. '''For systems not based on Debian you have to adapt the init-script as the used start-stop-daemon tool seems to be part of Debian's dpkg package.'''

<span lang="de" dir="ltr">Dieses Tutorial führt Sie durch die erforderlichen Schritte zur Einrichtung eines dedizierten 7DTD-Servers unter Linux. Das Tutorial zielt derzeit auf die Alpha 7.9-Version ab, die unter Linux so gut funktioniert wie unter Windows.</span>

<span lang="de" dir="ltr">Teil dieses Tutorials sind:</span>

<span lang="de" dir="ltr">-Einrichtung von 7DTD als dedizierter Server</span>

<span lang="de" dir="ltr">-Start- / Stop-Skripte, auch für automatischen Start beim Systemstart</span>

<span lang="de" dir="ltr">-Speicherverbrauchsüberwachung / Limit überschritten Benachrichtigung per Mail oder XMPP / Jabber (optional)</span>

<span lang="de" dir="ltr">-Automatische Sicherungssicherung (optional)</span>

<span lang="de" dir="ltr">Die Schritte und die verwendete Software in diesem Tutorial gelten für eine Debian Squeeze (6) oder Debian Wheezy (7) Installation. Für Systeme, die nicht auf Debian basieren, müssen Sie das init-script anpassen, da das verwendete start-stop-daemon-Tool Teil des Debian-dpkg-Pakets ist.</span>

== Required software ==
* Wine 32bit (as long as there is no "native" Linux build) (tested: 1.0.1, 1.4.1)
* <span lang="ang" dir="ltr">Xvfb (probably also only as long as there is no native build)</span>
* Mono-runtime
* Screen
* libxml2-utils (parse serverconfig.xml)
* bash (for scripts)
* rsync (for backups)
* sendemail, sendxmpp (for memory limit notifications, both optional)

This should do the trick on Debian Weezy base install: (I'm not entirely sure about the libmono2.0-cil)
 apt-get install libxml2-utils screen libmono2.0-cil xvfb xmlstarlet

== '''<span lang="de" dir="ltr">Erforderliche Software</span>''' ==
<span lang="de" dir="ltr">Wine 32 Bit (solange es keinen "nativen" Linux-Build gibt) (getestet: 1.0.1, 1.4.1)</span>

<span lang="de" dir="ltr">Xvfb (wahrscheinlich auch nur solange es keinen nativen Build gibt)</span>

<span lang="de" dir="ltr">Mono-Laufzeit</span>

<span lang="de" dir="ltr">Bildschirm</span>

<span lang="de" dir="ltr">Libxml2-utils (parse serverconfig.xml)</span>

<span lang="de" dir="ltr">Bash (für Scripts)</span>

<span lang="de" dir="ltr">Rsync (für Sicherungen)</span>

<span lang="de" dir="ltr">Sendemail, sendxmpp (für Speichergrenzbenachrichtigungen, beide optional)</span>

<span lang="de" dir="ltr">Dies sollte der Trick auf Debian Weezy Basis installieren: (Ich bin nicht ganz sicher, über die libmono2.0-cil)</span>

=== Installation on 64 bit host ===
In order to run SteamCMD on a 64 bit host you need to have lib32gcc1 installed.

To install 32 bit Wine on 64 bit Wheezy do the following:
 dpkg --add-architecture i386
 apt-get update
 apt-get install wine:i386


If you want to run the server as 64 bit application, you need Debian Sid or similar newer os which includes Wine 1.7.17 or newer (https://bugs.winehq.org/show_bug.cgi?id=30518).

[[Linux Server with Debian Sid]]

== '''<span lang="de" dir="ltr">Installation auf 64-Bit-Host</span>''' ==
<span lang="de" dir="ltr">Um SteamCMD auf einem 64-Bit-Host ausführen zu können, muss lib32gcc1 installiert sein.</span>

<span lang="de" dir="ltr">Um 32-Bit-Wine auf 64-Bit-Wheezy zu installieren, gehen Sie wie folgt vor:</span>

dpkg --add-architecture i386
apt-get update
apt-get install wine:i386

== Installation layout ==
Paths can be changed but this guide will assume that you use the paths as following:
; /home/sdtd
: home for the user running the server
; /home/sdtd/serverconfig.xml
: path of serverconfig.xml used by the scripts, see [[#Install the game|Install the game]]
; /home/sdtd/7dtd
: root of the 7dtd server installation
; /home/sdtd/7dtd/7DaysToDie.exe
: resulting in this path to the main exe
; /home/sdtd/steamcmd
: root of [https://developer.valvesoftware.com/wiki/SteamCMD SteamCMD]
; /usr/local/bin
: For the management scripts
; /etc/7dtd.conf
: For global script configuration
; /etc/init.d/7dtd.sh
: Init script to start/stop the server

== Useraccount dedicated to running 7dtd ==
As running the game as root is not really the best thing we will create a new user just for the server.
 useradd -d /home/sdtd -m -r -s /bin/bash -U sdtd

This will create a user and group named ''sdtd'' (last parameter) with home directory ''/home/sdtd''. Both can be changed but you will also have to adapt the other steps later on.

For wine on Debian 7.5 you'll also need to chown the home of sdtd to sdtd:
 chown sdtd /home/sdtd

== Install the management script files ==
Get the script files:
 wget http://illy.bz/fi/7dtd/management_scripts.tar.gz
Extract the files to ''/'':
 tar -xvzf management_scripts.tar.gz -C /
(alternatively you can extract to some temporary path and move files to their respective target folders manually)

Open the file /etc/7dtd.conf in the editor of your choice and edit the values. Edit at least the following variables:
 export STEAM_USER=
 export STEAM_PASS=
All other values can be kept at their default if you did stick to the paths and names given in this tutorial. Note that memory limit notifications are disabled by default!

Make sure the msvcr100.dll from the management scripts package is one directory level above SDTD_ROOT (if you followed this tutorial this will be the default). This file is required by the Steam library used in 7DtD.

Make the server start at system boot:
 update-rc.d 7dtd.sh defaults

== Install the game ==
'''Note:''' It seems like the 64 bit version of the game does not run nicely on Wine, thus the updater script automatically uses the 32 bit engine.

Run 7dtd-update.sh. This will download and install SteamCMD to the path given in the 7dtd.conf and afterwards download 7DtD itself. You can later on always run this command again to update the 7DtD files if there is an update on Steam.

''Copy the serverconfig.xml from the 7dtd directory to one level above it, so in this tutorial it would go to /home/sdtd/serverconfig.xml. Edit the file to match your needs.'' This way you can edit your serverconfig in the parent folder and Steam updates won't overwrite your changes. You should check back after updates to 7dtd whether there are new options in the original serverconfig.xml that you should add to your copy in ''/home/sdtd/serverconfig.xml''.

== Add cron-jobs for savegame backups and memory limit notifications ==
If you want the system to automatically backup the Worlds folder add the following line to ''/etc/crontab'':
 0 *     * * *   root    /usr/local/bin/7dtd-backup.sh
First two columns specify on which minute (0) and which hour (* = every hour) the backup will be run. Next three specify day, month and day of week (you probably want to keep * here).<br/>
'''Warning:''' As of Alpha 1 the game seems to only save the current state if the last player disconnects. So make sure that all players disconnect every now and then.

If you want to get notifications on the memory limit add this line:
 */5 *   * * *   root    /usr/local/bin/7dtd-check_mem.sh
Setting the minute to ''*/5'' means the script is run ''every 5'' minutes.<br/>
'''Make sure you set the appropriate values in ''/etc/7dtd.conf''!'''

== Start the server ==
 7dtd-start.sh
If everything went fine you should now be able to check console output of 7dtd:
 screen -r sdtd/sdtd
This will open the virtual terminal that was attached to the game. '''Do not press Ctrl+C to disconnect from that screen! Doing so will stop the whole engine!''' The parameter specifies username of the user running 7dtd / screen session name (you should only need to change the first ''sdtd'' if you changed the name of the user running the engine). Normal output should look something like this:
 Mono path[0] = 'Z:/home/sdtd/7dtd/7DaysToDie_Data/Managed'
 Mono path[1] = 'Z:/home/sdtd/7dtd/7DaysToDie_Data/Mono'
 Mono config path = 'Z:/home/sdtd/7dtd/7DaysToDie_Data/Mono/etc'
To disconnect from that screen session press Ctrl+A, Ctrl+D (simply keep Ctrl pressed). To stop the server run
 7dtd-stop.sh

== Feedback etc ==

For feedback, comments, suggestions, discussion whatever please use the [http://7daystodie.com/forums/showthread.php?2188-Dedicated-Server-without-hacky-workarounds forum thread].

[[Kategorie:Technisch]]
[[en:Linux Server]]