Search the Community

Showing results for tags 'debian'.

More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • Exile
    • Changelogs
    • Feedback
  • Exile Community
    • General Discussion
    • New Feature Voting
    • Problems & Bugs
    • Cat Walk
    • Recruitment
    • Small Talk
  • Exile Mod XM8 App
    • XM8 Server Administration
    • XM8 Android App
    • XM8 Discord Bot
  • Exile Mod Server Administration
    • Ask a Game Server Provider
    • Hosting
    • Operating Systems
    • Installation
    • Database
    • Security
    • Maintenance
  • Exile Mod Customization
    • Downloads & Releases
    • Content
    • Environment
    • Gameplay
    • Look & Feel
    • Tech Talk
  • Exile Life Mod
    • Visit forum on


  • Knowledge Base
  • Items
  • Constructions
  • Traders
  • Vehicles


  • Servers


  • Devblog

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start




Found 6 results

  1. Rotter

    Stuck Connecting

    I know that issue is old but after reading and doing all the stuff that people recommend it, still I can't find the light at the end of the tunnel. First of all, my goal is to setup a vanilla exile gnu/linux (debian) server. I followed this tutorial: It's really useful but lacks two important tips: still you must lowercase mod names as Bohemia's wiki suggests (Some mods such as @ALiVE and @A3MP will not function if there are capital letters in any of their file names. If you do not update your mods on a regular basis, you can just use the command...). Maybe I'm wrong but the point that it did'nt work until I do the change. never lowercase "extDB2" folder and the dinamic library "". Okay. Let's continue. The config files are set as it follows: Battleye is set to 1 (true) at @exileserver/config.cfg At @exileserver/extdb-conf.ini is set the [exile] database parameters: I launch the server executing this command: ./arma3server -cfg=@exileserver/basic.cfg -config=@exileserver/config.cfg -autoinit -mod=@exile\; -servermod=@exileserver\; -port=2302 -profiles=SC -name=SC -noSound 2> SC/serverlog.rpt The "nice" ouput confirms that everything runs fine: 15:57:09 Dedicated host created. 15:57:24 BattlEye Server: Initialized (v1.217) 15:57:24 Host identity created. 15:57:25 Game Port: 2302, Steam Query Port: 2303 Arma 3 Console version 1.84.144924 x86 : port 2302 15:57:25 Mission Exile.Malden read from bank. 15:57:25 Roles assigned. 15:57:26 Reading mission ... 15:57:36 Mission read. 15:57:37 Game started. The verbose ouput (saved at SC/serverlog.rpt) also confirms that the server connects to database without any issue: 15:57:36 CallExtension loaded: extDB2 (/home/rotter/Server/@exileserver/ [j] 15:57:36 "ExileServer - Installed extDB2 version: 71" 15:57:36 "ExileServer - Connected to database!" 15:57:36 "ExileServer - Database protocol initialized!" Also I check the log file from extDB seems to say ok: extDB2: Version: 71 extDB2: extDB2: Linux Version Message: All development for extDB2 is done on a Linux Dedicated Server Message: If you would like to Donate to extDB2 Development Message: Message: Also leave a message if there is any particular feature you would like to see added. Message: Thanks for all the people that have donated. Message: Torndeco: 20/02/15 extDB2: Found extdb-conf.ini extDB2: Detected 1 Cores, Setting up 2 Worker Threads [15:57:36 +02:00] [Thread 713] extDB2: Database Type: MySQL [15:57:36 +02:00] [Thread 713] extDB2: Database Session Pool Started [15:57:36 +02:00] [Thread 713] extDB2: SQL_CUSTOM_V2: Loading Template Filename: /home/rotter/Server/@exileserver/extDB/sql_custom_v2/exile.ini [15:57:36 +02:00] [Thread 713] extDB2: SQL_CUSTOM_V2: Version 12 Detected, Latest Version 12 Available I don't forget the tip from @snorp and other guys about the need of include this line at "/etc/mysql/my.cnf" sql-mode="ERROR_FOR_DIVISION_BY_ZERO,NO_ZERO_DATE,NO_ZERO_IN_DATE,NO_AUTO_CREATE_USER" So, when I trying to log in to the server, it stucks at the Connecting screen. Nothing happens. Only this: Checking again the server log and didn't see any change or update. Nothing revelant at the client logs as well. I found that I think is the same problem: and another dead end thread about the same issue: Any help will be welcome...!
  2. snorp

    Tutorial - Linux Server

    Hallo guys, This article was written by me in German. I have decided to translate it into English now. You are welcome to correct me! Feel free to criticize me, too! ARMA III Linux Installation Guide After a Linux distribution has been installed, in this case Debian 8 (8.9), we create a user responsible for the ARMA server and its administration. adduser steam ARMA III and SteamCMD need some libraries to install. sudo apt-get install lib32stdc++6 sudo apt-get install lib32gcc1 Furthermore, we need a SQL Server, unzip and nano the text editor. We install it with the following command. Important: When creating the sql server, make sure that you enter your data correctly, because password etc., you will have to save it in your config file later! apt-get update apt-get upgrade apt-get install software-properties-common apt-key adv --recv-keys --keyserver 0xcbcb082a1bb943db add-apt-repository 'deb [arch=amd64,i386,ppc64el] jessie main' apt-get update apt-get install mariadb-server apt-get install unzip apt-get install zip apt-get install nano We log in with the created user and add a folder that we enter directly. sudo -i -u steam From the Valve Developer Community page we download the current SteamCMD and run it after unpacking the package. wget tar xf steamcmd_linux.tar.gz ./ It is recommended to create an extra Steam account for hosting dedicated servers. We log in with the account in the SteamCMD and start the download of ARMA III. login username force_install_dir ./arma3/ app_update 233780 exit EXILE Mod installation To use the Exile Mod for our ARMA III server we will download the server data from the official exilemod. com site (version may vary). Go to the arma3 folder and save the zip data in an extra folder. cd arma3 mkdir data cd data wget wget unzip \ unzip \ After unpacking the data, we move all relevant data. mv @Exile ../ cd Arma\ 3\ Server/ mv LICENSE.txt ../../ mv tbbmalloc.dll ../../ mv @ExileServer/ ../../ mv battleye/* ../../battleye/ mv keys/* ../../keys/ mv mpmissions/* ../../mpmissions/ cd .. rm -r Arma\ 3\ Server/ We build the database by executing the following command and feeding it with the exile. sql file. mysql -u root -p create database if not exists exile; GRANT ALL ON exile.* TO 'exile'@localhost IDENTIFIED BY 'password'; flush privileges; source /home/steam/arma3/data/MySQL/exile.sql quit An important step is configuring the config files. Here you should adjust the server name, password etc. For example, the map to be played can be changed in config. cfg (template = Exile. Malden). Access to the database must also be guaranteed. For this reason we edit the extdb-conf. ini and insert the access data from our created database. cd ~/arma3/@ExileServer nano config.cfg nano extdb-conf.ini Fault analysis As now, check whether the extDB works with the following command. ldd If there is "not found" after a line, we will execute the following as root. dpkg --add-architecture i386 apt-get update apt-get install libc6 tmux lib32gcc1 lib32gcc1 lib32stdc++6 libtbb2:i386 To start the server we go to the folder where the arma3server file is located and execute this command. ./arma3server -cfg=@ExileServer/basic.cfg -config=@ExileServer/config.cfg -autoinit -mod=@Exile\; -servermod=@ExileServer\; >> serverlog.rpt -autoinit Starts the mission, including all related tasks, otherwise this is only done after the first connection by a client to the server. >> serverlog.rpt Creates the "serverlog.rpt" log file in our server directory. Bambi Creation Timeout If the problem arises that players cannot join the server because "Bambi" cannot be loaded correctly, the mysqld. cnf file must be edited as root. sudo nano /etc/mysql/my.cnf Adds the following line after [mysqld]. sql-mode="ERROR_FOR_DIVISION_BY_ZERO,NO_ZERO_DATE,NO_ZERO_IN_DATE,NO_AUTO_CREATE_USER" Restarts the service to make the changes effective. service mysql restart Modify Exile Mod coming soon... Server AdminToolkit To manage the inGame server I decided to use a free variant. I use the AdminToolkit von Ole from Ole which works really well. First we load the data from GitHub and unpack the @AdminToolServer folder into our server directory. cd ~/arma3/data wget unzip cd a3-admintoolkit-master mv @AdminToolkitServer ../../ Afterwards we move the key file. mv admintoolkit.bikey ../../keys/ We unpack the admintoolkit_servercfg. pbo archive and add the admin's UID?s to the config. cpp (this can be found in the Arma 3 menu > Profile). Moderators can also be added to this file. After we have saved the file again we pack the data back to a. pbo archive. Next we need to customize our Missions. pbo file. We unpack them and open the description. ext file. There we add behind class ExileServer_system_network_dispatchIncomingMessage { allowedTargets = 2; }; the following class AdminToolkit_network_receiveRequest { allowedTargets = 2; }; We stay in our missions directory and open the config. cpp there we search for the line class CfgExileCustomCode and add the following before the above line. class CfgAdminToolkitCustomMod { /* Exclude some main menu items * To only show the menus loaded from an extension, use: * * ExcludeMenu[] = {"Players", "Vehicles", "Weapons" , "Other"}; */ ExcludeMenu[] = {}; Extensions[] = { {"Exile Mod","ExileMod"} }; /* 4 Quick buttons allowing to add any action you want - See example below*/ QuickButtons[] = { /* send a chat message to selected player containing 'Test 123' */ {"Chat", "['message', [AdminToolkit_Player, 'Test 123']] call AdminToolkit_doAction"}, /* send a message to everyone using the parameters text field */ {"Msg To All", "['messageall', AdminToolkit_Params] call AdminToolkit_doAction"}, /* Quickly get a Helicopter */ {"Heli", "['getvehicle', 'B_Heli_Light_01_armed_F'] call AdminToolkit_doAction"}, }; }; Last but not least, we copy the atk folder from the @MissionsFile folder, which we downloaded, into our missions folder on our server and put it back into the. pbo archive. Now all we have to do is adjust the start parameter. ./arma3server -cfg=@ExileServer/basic.cfg -config=@ExileServer/config.cfg -autoinit -mod=@Exile\; -servermod=@ExileServer\;@AdminToolkitServer\; >> serverlog.rpt ExileZ Mod + Ryan Zombies & Demons First of all we download all important data, starting with the ExileZ Mod and then the Zombie Mod. To do this, we go back to our data folder by packing all relevant data for Exile. Please make sure that you check the links I posted here again! I put the Zombies & Demons Zip file on my private server, because I don't get a direct link via google drive. cd ~/arma3/data wget wget As usual we unpack both archives with unzip (master. zip. 1, because there is already a master. zip in our data folder). unzip unzip We receive two folders, the ExileZ-Mod-master and the ZombiesDemonsV5.0 folder, which we will now go into in more detail. This contains another folder @Ryanzombies which we move into our arma3 directory. mv @Ryanzombies ../ Now it is important that we copy the key located in the @Ryanzombies folder. cd ../@Ryanzombies/Keys cp RyanD.bikey ../../keys Unfortunately, I noticed that there were problems starting the server. I have received an error message that may indicate that the directories in the @Ryanzombies folder are not all written in lower case. For this reason, we have to provide all folders with lowercase letters. To do this, we go back to our basic directory. cd ~/arma3 mv @Ryanzombies @ryanzombies cd @ryanzombies mv Addons addons mv Keys keys After that we can check the @ryanzombies folder and now we are working on the ExileZ Mod. This mod is sent with an exilez_mod. pbo file. We can unpack these to change some values, like spawning the zombies etc. (more about this later). For simplicity's sake, we take the finished exilez_mod. pbo directly and add it to our @ExileServer Addons folder. cd ../data/ExileZ-Mod-master/ mv exilez_mod.pbo ../../@ExileServer/addons Now we have to adjust the mission file. To do this, we go to the arma3 folder in the mpmissions folder and unpack the. pbo archive, which we have on the server. We add ryanzombies and ryanzombiesfunctions to the missions. sqm file, so it should look like this. addOns[]= { "exile_client", "a3_map_altis", "ryanzombies", "ryanzombiesfunctions" }; After this is done we pack all the data back into a. pbo archive and put it in our mpmissions folder, which is located directly in the arma3 directory. Finally, we adjust the start parameter by adding @Ryanzombies;. The whole thing looks like this. ./arma3server -cfg=@ExileServer/basic.cfg -config=@ExileServer/config.cfg -autoinit -mod=@Exile\; -servermod=@ExileServer\;@AdminToolkitServer\;@ryanzombies\; >> serverlog.rpt Konfiguration Exilez Mod Theoretically, the configuration files are self-explanatory, as they have been well commented. But let's start with the first one, which data is relevant for us. First we should unpack the exilez_mod. pbo file and open the config. sqf. I won't explain every setting in this step, because that would go beyond the tutorial. That is why I would like to make the most important points. These two settings represent the maximum number of zombies to be created on the server and the fraction that each zombie receives. For example, if we place the Zombies' faction on West, they don't attack us anymore and run directly to a pre-defined point without paying attention to us. EZM_MaxZombies = 100 EZM_ZombieSide = EAST Furthermore, I deactivated the demons and the exploding zombies. EZM_ryanzombieshealthdemon = -1; EZM_ExplosiveZombies = false; The option of throwing is a bit too much and in my opinion it seems to be "robust" (which it is not). For this reason, the following settings. EZM_ryanzombiescanthrow = -1; EZM_ryanzombiescanthrowtank = -1; Horde building and spawning settings around the player have all been left on default. I think it's also a question of taste and server performance. If there is a real need for further explanation, you are welcome to comment on it here. Restart/Backup Script After the server shuts down by the integrated RCON commands, it has to be restarted properly. I have created a small shell script which is called up every 3h via crontab. The script itself looks like this. ################################################################################# # NAME: BACKSTART SCRIPT # AUTHOR: SNORP (THUNDERFIRE.NET) # VERSION: 1.3 # DATE: 2017/09/14 ################################################################################# # # VARIABLE # BACKUP_DIR=/home/steam/backup CURRENT_HOUR=$(date +"%H") CURRENT_DATE=$(date +"%F_%H") SERVER_PROCESS=$(ps axf | grep arma3server | grep -v grep) # CHECK SERVER IS RUNNING while [ ! -z "$SERVER_PROCESS" ]; do sleep 5 echo "The server is still running!" SERVER_PROCESS=$(ps axf | grep arma3server | grep -v grep) done echo "The server is offline, the script is now started." # CHECK THE TIME FOR A BACKUP if [ "$CURRENT_HOUR" -eq 10 ] || [ "$CURRENT_HOUR" -eq 22 ]; then # ITS TIME FOR A BACKUP echo "A backup is created." mysqldump --user=exile --password=PASSWORDHERE exile > $BACKUP_DIR/db_$CURRENT_DATE.sql zip -r $BACKUP_DIR/bu_$ /home/steam/arma3/battleye /home/steam/arma3/@AdminToolkitServer /home/steam/arma3/@ExileServer /home/steam/arma3/@ryanzombies /home/steam/arma3/mpmissions #BACKUP COMPLETE NOW RESTART THE SERVER screen -S A3Server -X stuff './arma3server -cfg=@ExileServer/basic.cfg -config=@ExileServer/config.cfg -autoinit -mod=@Exile\; -servermod=@ExileServer\;@AdminToolkitServer\;@ryanzombies\;>> serverlog.rpt\n' echo "Backup was created successfully, the server is now restarted." else # ITS NOT TIME FOR A BACKUP JUST RESTART echo "No backup is performed. The server is restarted." screen -S A3Server -X stuff './arma3server -cfg=@ExileServer/basic.cfg -config=@ExileServer/config.cfg -autoinit -mod=@Exile\; -servermod=@ExileServer\;@AdminToolkitServer\;@ryanzombies\; >> serverlog.rpt\n' fi There are certainly even better and more elegant methods than these! For this reason I ask the community to help me customize this script. It is important to insert the SQL password! SECURITY RISKO! otherwise the backup function will not work. In addition, the backup will be executed at 10.00 and 22.00 hours, these values can be changed as desired. An automatic cleaning after one week, for example, has to be added, of course, but I haven't yet been able to do that. To execute the script every 3h we create a crontab with the following command and select 2. /bin/nano. crontab -e 0 0,3,6,9,12,15,18,21 * * * /home/steam/ Of course, the time of the server should be adjusted with that of the crontab. I decided on the runtime of 2:59h. For the topic Arma 3 / Exile configuration I will add the tutorial a little later.
  3. Updated 21/06/17 Hello fellow server admins. I know there are guides around on how to get a server running on linux but Debian 7 requires a few extra things so I might aswell post a full setup guide. This setup should also apply for Ubuntu and such but you don't need to setup libc6 2.19 for this. Then again, I feel like I should mention that you can upgrade your debian to 8 without loosing any data if you do it right. You should do it because you can skip the lib stuff. Anyways, here we go: For the following guide comments on code will be written with // behind it like so: _variable { function1; //this is a comment function2; //more comment }; //////// sudo apt-get install somestuff //comment on a command If you're gonna copy a command or something, don't copy the comment, obviously. Now that's out of the way, let's get started. Note: I will not be covering the basics of handling Debian, just the more advanced stuff. Step 1: Prerequisites Before we can actually install our server, we need some stuff. First off, we will need either the root account or a user with sudo privileges. Using sudo is recommended and I will be using sudo. We want to create another user to run the server since using an administrator account would be risky if not downright stupid. Creating a user by the name of exile: (Change it to whatever you want your user to be called) sudo adduser exile Set a password of your choosing. We won't be using this account quite yet. Now we need some libs that steam and arma 3 depend on: sudo apt-get install lib32gcc1 sudo apt-get install lib32stdc++6 //This might fail, see below If you get an error along the lines of "The following packages have unmet dependencies: ia32-libs", add i386 as architecture using dpkg and install ia32-libs: dpkg --add-architecture i386 apt-get update apt-get install ia32-libs To install arma 3 we will need steamcmd, a command line version of steam. (duh ) ChangeDirectory to wherever you want steam and your server to be, download and unpack steam: sudo mkdir /games/steam/ //making a games directory in the root folder, need to be root for that. cd games/steam/ wget tar -xvzf steamcmd_linux.tar.gz //No, I can't remember the Syntax for tar either, I totally just looked that up chmod +x //you want to make it executable because it doesn't run via sh for some reason All set on the prerequisites, now let's take a look at Step 2: Installing Arma Start up steamcmd. screen ./steamcmd You should now see something like this: login as anonymous: (the arma 3 DS doesn't need a purchased copy of the game) Now set the path to wherever you want to install your server (../arma3 for me) and start installing. The validate option is just to verify we have not received broken files. force_install_dir ../arma3 app_update 233780 validate Steam will now be doing its thing. Depending on your server's connection this can take a few minutes. When the download is done you can exit steam by typing exit. STEP 3: Installing exile Now that your server is downloaded, we need to get the server and client files for Exile. cd to your server directory: cd ../arma3/ //or whatever it is for you Go to , copy the link addresses for the server and client files and download them. (1.0.3 "Lemon" at the time of this writing update. Hello from the past!) wget wget Done? Good. unpack 'em. sudo apt-get install unzip unzip unzip Since the server files only come with a version of extDB2 for windows we need to download it ourselves: NOTE: If extDB2 v71 is not the newest version at the time of you reading this, choose a newer one from This can be skipped now that exile includes the linux version again! Thanks devs! Step 4: Setting up your database Exile uses MySQL. Debian and also Ubuntu if I am not mistaken come with the mysql server pre-installed (Most dedicated hosting companies do this for you and give you the password.). If not, there is excellent guides on how to install it on the internet. Log in as the root mysql user and create the database and user: mysql -u root -p CREATE DATABASE exile; //don't forget the friggin semicolon GRANT ALL ON exile.* TO 'exile'@localhost IDENTIFIED BY 'password'; //You can name your user and password whatever you like exit; Now that you have a database you need to configure extDB to connect to it. cd @ExileServer/ vim extdb-conf.ini //use vim or whatever editor you like. Nano for instance //Old pic, it could look a little different for you. Above is my configuration (well, I redacted my rcon password, obviously ) which you can use as guidance. You want to change Name, Username and Password under [exile]. Name is your database name. (We set that to exile earlier) Username is your mysql user. (Also exile in our example) Password is... your mysql password. (We set that to password, you should have changed that.) Save the file. Step 5: Fixing libc6 Here's the part where it gets interesting. Debian 7 "wheezy" uses a pretty outdated version of libc6. For our purpose we need a newer version. Since we can't just update it because it is a base library of unix we need to manually download the proper libs and tell Arma to use those. (I spent like 6 hours trying to get arma to load them until I figured out how -.-) ONLY DO THIS STEP IF YOU ARE ON DEBIAN 7 OR SOME OBSCURE VERSION OF UNIX THAT DOESN'T USE LIBC6 2.15 OR GREATER //I since upgraded to debian 8 which is using newer software. Consider upgrading: Here is how to do that: wget mkdir libs/ //making a libs dir in our A3 server's root folder dpkg -x libc6_2.22-12_i386.deb libs/ //Just updated this with new URL since the old one was 404 - please tell me if this doesn't work. The libs are now in libs/ and you can make your start script with the right parameters. (On a side note, now two years after this thread was first conceived: There are better ways to do what I did here. While what I'm doing here isn't necessarily bad practice, I found out that my nerd friends will look at me angrily when I tell them about this solution. Someone also mentioned using debian backports. As I'm not too familiar with it I won't go into detail about it, but try googling and see what happens :P) Step 6: Start script Create a new file with an editor of your choice and name it something like . Now, to tell Arma to use the custom libs we installed previously, the file needs to begin with ./libs/lib/i386-linux-gnu/ --library-path ./:./libs/lib/i386-linux-gnu After that we can put ./arma3server and then any parameters we want to execute. My start script looks like this: ./libs/lib/i386-linux-gnu/ --library-path ./:./libs/lib/i386-linux-gnu ./arma3server -pid=2322 -cfg=@ExileServer/basic.cfg -config=@ExileServer/config.cfg -port=2322 -autoInit -ranking=plyrs.log -cpuCount=8 -exThreads=7 -mod=@allinarmaterrainpack\;@Esseker\;@Exile\;@Ryanzombies\;@L_Climb\;@JSRS2.2\; -servermod=@ExileServer\; I have a whole bunch of mods installed but I'll go over what each option does. ./arma3server : starts your server. Yeah. -pid=2322 : Sets my pid file. You can probably leave that but I'm just a geek like that. -cfg=@ExileServer/basic.cfg : Sets your basic config file. You should set that as I did because Exile comes with it. -config=@ExileServer/config.cfg : Sets your server config. See above. We will go over the config file in the next step. -port=2322 : Sets your server's port. Standard would be 2302 but as I have a arma 2 server running on that port I chose another one. -autoInit : Initializes your mission even if no player has connected. Useful for automatic restarts and should be set. Obsolete and broken now -ranking=plyrs.log : Ignore that That's just me messing around with startup parameters. -cpuCount=8 : Set the number of physical CPU cores with this. -exThreads=7 : sets extra threads. If you don't know what it does, don't include it. -mod=@Exile\; : Sets what mods will be used. This needs to say at least @Exile\; to run your exile server. NOTE: You need to put a backslash in front of semicolons ( ; ) or your server will stop loading whatever comes after! -servermod=@ExileServer\; : This sets what other mods will be used. These however will not be broadcast to the client. (Won't show up in their multiplayer window) Set the above to your liking and you should be good to go! You might want to edit the config.cpp in your @ExileServer/addons/ExileServer_config.pbo though. Unpack with PBOmanager or the like and configure. Then repack and reupload. Wow, this got longer than I thought it would If this tutorial helped you, give it a like please. If people like this maybe I'll provide more tutorials in the future. Hope this helps linux server admins so that they don't have to spend hours upon hours figuring stuff out like I did when I first installed a server. Thanks for reading. If there is any questions about this process don't hesitate to ask here or contact me via PM or mail. Regards,
  4. SillymeX

    Debian 8.1 startup script issues

    Hello everyone, I'm currently using this startup script and occasionally it works fine but for majority of the time when I launch my server through it, it will say "server is already running" when it's not. Occasionally when it did that, I managed to find out that some mods were having issues which did not allow the server to start. After fixing the issues, the startup script worked again. This time its different. Firstly I tried running the script with only exile mod just to be sure that it's not an issue in the mods. It would still say "server is already running" which means that it's not a mod issue. Also I always check if it actually starts the server by doing the top command. Unfortunately, I don't have any processes running, yet it repeats "server is already running". It will not make any logs since the server is not actually up. As soon as I go to my a3 root folder and launch it with the parameters, the server loads up with all of the mods with no errors. I would appreciate a working solution to this. Here is the script that I use: #!/bin/bash ### BEGIN INIT INFO # Provides: exile # Required-Start: $remote_fs $network # Required-Stop: $remote_fs $network # Should-Start: mysql # Should-Stop: mysql # Default-Start: 2 3 4 5 # Default-Stop: 0 1 6 # Description: ArmA 3 Exile init.d Script by Flodding ### END INIT INFO #======================================================================= #======== CONFIGURATION PARAMETERS ======== #======== MUST BE EDITED MANUALLY TO FIT YOUR SYSTEM PARAMETERS ======== #======================================================================= USERNAME="pirkka" # This user *MUST* exist on the system. EXILE_DIR="/home/${USERNAME}/arma3/" # Change to your path... NAME="cfg" # You can use any name here, your server, or clan... CONFIGFOLDER="${EXILE_DIR}/${NAME}" CONFIG="${NAME}/config.cfg" # Remember to move config files from @exileserver/*.cfg to YOUR_INSTANCE_NAME/! CFG="${NAME}/basic.cfg" # Remember to move config files from @exileserver/*.cfg to YOUR_INSTANCE_NAME/! BEPATH="${EXILE_DIR}/battleye" LOG_DIR="${CONFIGFOLDER}/logs" PORT=2302 PIDFILE="${CONFIGFOLDER}/${PORT}.pid" if [ -f ${PIDFILE} ]; then RUNNING=1 PID=$(cat ${PIDFILE} > /dev/null) else RUNNING=0 fi SERVICE="arma3server" MODS="@exile" SERVERMOD="@exileserver" #CPU_COUNT=2 # Some common options # -ip= # -port=2302 (default) # -mod=@exile;kart;mark;heli; # -servermod=@exileserver # -config=C:\Arma\Server\@exileserver\config.cfg # -cfg=C:\Arma\Server\@exileserver\basic.cfg # -name=INSTANCE # -profiles=INSTANCE # -log # -nolog # -world=empty # -nosplash # -nosound # -nopause # -malloc=system -malloc=tbbmalloc # -autoinit OPTIONS="-port=${PORT} -pid=${PIDFILE} -name=${NAME} -profiles=${NAME} -cfg=${CFG} -config=${CONFIG} -mod=@Exile\;@AllInArmaTerrainPack\;@esseker\; -servermod=@ExileServer\;@infiSTAR_Exile\;@enigma_exile\; -log -nopause -nosound -nosplash -autoinit" TMUX_SESSION="exile" # You can use any name here. #======================================================================= # CONFIG END #======================================================================= TMUX=$(which tmux) [ ! -x "$TMUX" ] && echo "Tmux not found" >&2 && exit 1 if [ ! -d "$LOG_DIR" ]; then echo "${LOG_DIR} not found. Creating..." mkdir -p $LOG_DIR fi exile_start() { if [ ! -f $EXILE_DIR/$SERVICE ] then echo "$SERVICE not found! Stopping..." sleep 1 exit else if [ ${RUNNING} -eq 1 ]; then echo "$SERVICE is already running!" else echo "Setting Permissions..." #chmod -R 0755 $EXILE_DIR chown -R $USERNAME:$USERNAME /home/$USERNAME echo "Starting $SERVICE..." cd $EXILE_DIR # Fix: find @exile/ -depth -exec rename 's/(.*)\/([^\/]*)/$1\/\L$2/' {} \; find @exileserver/ -depth -exec rename 's/(.*)\/([^\/]*)/$1\/\L$2/' {} \; if [ "${2}" == "-silent" ]; then su ${USERNAME} -c "${TMUX} new-session -d -s ${TMUX_SESSION} \"./${SERVICE} ${OPTIONS} > ${LOG_DIR}/exile.log 2> ${LOG_DIR}/errors.log\"" else su ${USERNAME} -c "${TMUX} new-session -d -s ${TMUX_SESSION} \"./${SERVICE} ${OPTIONS} 2> ${LOG_DIR}/errors.log | tee ${LOG_DIR}/exile.log\"" fi echo "Searching Process ${SERVICE}..." sleep 8 if pgrep -u $USERNAME -f $SERVICE > /dev/null then echo "$SERVICE is now running." RUNNING=1 else echo "Error! Could not start $SERVICE!" RUNNING=0 fi fi fi } exile_stop() { if [ ${RUNNING} -eq 1 ]; then echo "Stopping ${SERVICE}..." su $USERNAME -c "$TMUX kill-session -t $TMUX_SESSION" $TMUX kill-session -t $TMUX_SESSION killall -9 $SERVICE else echo "$SERVICE is stopped." fi if [ -f ${PIDFILE} ]; then rm -f ${PIDFILE} fi } exile_status() { if [ -f ${PIDFILE} ]; then PID=$(cat ${PIDFILE}) echo "Server is running (PID=${PID})..." else echo "Server not running..." exit 0 fi } case "$1" in start) exile_start ;; stop) exile_stop ;; restart) exile_stop exile_start ;; status) exile_status ;; attach) su $USERNAME -c "$TMUX at -t $TMUX_SESSION" ;; *) echo "$0 (start|stop|restart|status|attach)" exit 1 ;; esac exit 0
  5. I stuck on this screen(Waiting for server to load...) when i change any parameter on exile_server_config.pbo or Exile.Altis.pbo and re-pack with PBO Manager. With stock files everything run without any issues. Client Logs: Server Logs: extDB Logs: With Windows Server 2012 R2(64 bits) and Debian Jessie 8.2(64 bits). Same issue on both. I am using fresh install of ARMA3(with steamcmd) & Exile Nectarine. Any help is welcome. Thank you.
  6. SurvivalZ

    Läuft der Exile-Mod auf Debian Servern

    Hey Leute, Bin gestern über den Exilemod gestolpert und wollte wissen ob dieser Mod sich auch auf Debian bzw. Linux installieren lässt ? (ohne Wine etc.) mfg SurvivalZ