Linux Standalone Server 1.62
Description:
It requires Arma 2: Operation Arrowhead data to be updated to version 1.63 first in order to run properly.
Ideal to combine with latest OA beta client:
Please provide us with feedback to this topic.
Installation:
1. Following programs must have been installed on your Linux-box:
tar, gcc. Optional: md5sum (for setup integrity check)
1a. On some verions of Linux (this was reported for RedHat 9
and Gentoo linux 2.4.20) the NSCD deamon must be installed to
run ArmA 2 server successfully. Caching of DNS would be sufficient.
2. Copy the whole «ArmA 2 Operation Arrowhead» directory from Windows
to some Linux-directory (arma2arrowhead). DON’T DO ANY DATA CONVERSIONS
(even «dos2unix» translation of text files is not necessary).
Example: you can use PKZIP (WinZip, PowerArchiver, etc.) on
Windows and «unzip» on Linux.
Don’t use upper case letters in the ArmA2 directory name
(/home/bob/arma2arrowhead will be good, /home/bob/ArmA2ArrowHead
may cause some troubles).
ArmA2 directory should contain subdirectories «Addons», «Bin»,
«Campaigns», etc.
3. Copy the «server-x.xx.tar.gz» (x.xx is version number) file into
the arma2arrowhead directory. Unpack and install it with commands:
arma2arrowhead$ tar -xjf server-x.xx.tar.bz2
arma2arrowhead$ ./install
Watch the messages — they will inform you whether your installation
is successful.
4. Dedicated server can be started in foreground:
arma2arrowhead$ ./server
Or in background:
o$ nohup ./server > out.txt 2> err.txt &
[1]
5. Running server can be stopped by executing:
$ kill -s SIGINT
is process-id of mother server thread (printed out in
«nohup» command).
6. ArmA2 ArrowHead server has a feature: command-line parameter
«-pid=
«. It causes creation of
with
PID of root ArmA2 process. If IP port specified in «-port= »
parameter is busy (in usage), ArmA2 will terminate immediately
and
won’t be written..
7. The «arma2server» script is provided for automatic server
start/restart/status query/etc. Please be sure to edit
CONFIGURATION PARAMETERS in lines 12 to 18 !
After this is done, install (hard-link?) the script into
«/etc/rc.d/init.d/arma2server» file. After that it can be managed
by «chkconfig» (see info/man).
Chnagelog:
v1.62.102451 alpha
* Contains some bug fixed not linux specific + timestamp in logfile (linux specific)
* Fixed: Linux Date format wrong
* this version brings OA dedicated linux server into sync with actual windows server improvements and ai/mp fixes (only up to it’s nr. not higher).
v1.62.101906 alpha
* Contains some bug fixed not linux specific + timestamp in logfile (linux specific)
* Fixed: Linux Date format wrong
* this version brings linux in sync with actual windows server improvements and ai/mp fixes (only up to it’s nr. not higher).
v1.62.100000 alpha
— Contains some bug fixed not linux specific + timestamp in logfile (linux specific)
— Fixed: Linux Date format wrong
— this version brings linux in sync with actual windows server improvements and ai/mp fixes (only up to it’s nr. not higher).
v1.62.96458 alpha
— some more bugs fixed, some still present
v1.62.95946 alpha
Recent fix: resolved issue with «Failed to load TextureHeaderManager» , no need use -noTexHeaders commandline parameter!
— STEAM libraries
You are using our website as a guest. Guest have the lowest downloadspeeds and will download from our public file servers. If you would like to know how you can download with higher speeds and have to wait less while downloading check out the Armaholic subscription system.
When you have already subscribed and your account is not upgraded within 24 hours it means you probably forgot to include your username. If that is the case please contact us as soon as possible!
Arma 2: Dedicated Server
Contents
Introduction
This article covers some of the aspects of the dedicated server for Arma 2
Some of the information on this page covers beta versions of the software and documentation.
This software is released under end user agreement terms as the original game so you should agree with the terms of the end user agreement of Arma 2 as found in the manual before installing and using this software.
Installation
We recommend using 2 GHz machine, with 512 MB RAM and a 1 Mbps upload network bandwidth.
Arma 2: You need a Microsoft Windows XP/2000/Vista/2008/Seven computer to run an Arma 2 dedicated server, yet a version of Linux server is also available.
The rest of this section covers installation on a Windows computer. For installation on a Linux computer see the Linux section.
There are two possible ways to install the dedicated server. When you have installed the ArmA game, you can use the main executable (ArmA.exe) with the command line argument –server to start a dedicated server. While this is easy, it requires the ArmA DVD to be present in the drive during server operation and also original serial number. (However with the latest patch version 1.05 the DVD is no longer needed.).If you want to run a server without the DVD and serial number, you have to use the standalone dedicated server executable.
The latest version of this executable is always available from the Downloads section.
To install a standalone server
- Install the corresponding version of the game on any machine (you will need ArmA DVD for this)
- Add the arma2server.exe/arma2oaserver.exe file to the same directory as ArmA2.exe/ArmA2OA.exe. Copy your already installed ArmA2/ArmA2OA directory on to the server.
- Create a configuration file for your server. See server.cfg for further information.
Installing a patch on the dedicated server
To install a patched version on the dedicated server, you can either install the patch on some machine with the full game installed and then transfer the full patched game, or you can download the patch to the dedicated server, make sure there exists a registry entry on the server so that the patch can find the game location, verify the CD key, and apply the patch directly on the server.
The registry entry can be created by exporting a registry key HKEY_LOCAL_MACHINE\SOFTWARE\Bohemia Interactive Studio\ArmA from the machine where the game is installed. The file should look like this:
To install updates on Windows Server 2003 (64bit) and all the other options have not worked please try this work around instead you will still need to edit the paths «Main»=»C:\\Your\\ArmA\\Path\\ArmA»
- note: the installer might use PATH instead of default MAIN key, this is unstandard fix and might not work with latest patches
Windows server 2003 (64bit)
Startup Options
Server Crashes
In the event of a server crash, please help BI to fix the problem by sending the crash files arma.rpt and arma.bidmap files that will be created on each crash. For the location of these files and where to send them to, see Crash Files.
Server Security
There are several settings you might want to consider which improve the security and integrity of the dedicated server which are found in the server.cfg.
Server Administration
You can administer the server as a player through various Multiplayer Server Commands. It is also possible to remotely administer the server through BattlEye’s RCon administration tool
Banning
To ban a user you have to know their unique online ID (called Player ID). This can be checked in the players overview screen (‘P’ key) during the game, or with the #userlist command. To ban a user you have to add their Player ID to file ban.txt residing in the main ARMA directory. If there is no such file there, create a new one. The format of ban.txt is a plain ASCII text list of decimal Player IDs delimited with space, tabulator or end-of-line characters.
Firewall issues
By default the Armed Assault server is reporting to Gamespy and it also uses the Gamespy server to negotiate a NAT traversal. If this does not work reliably for you (e.g. when running behind very strict firewall), you may need to open and/or forward following incoming ports:
Following outgoing ports need to be open as well:
Default value of port is 2302, but you may change it by -port command line argument.
Proxy issues
You may enforce proxy server used to download xml squad page etc. Using the value «proxy» in server.cfg.
Performance Tuning Options
Running Server as a Service
You may also consider running the ArmA server as a service, and enabling automatic restart in case of crash. In this case, you may want to disable DrWatson crash monitoring utility on your computer, as it often prevents ArmA server to shutdown properly (by displaying a message box that requires an operator to confirm application termination).
A HowTo for user-defined services can be found at http://support.microsoft.com/kb/137890/en-us. This How-To is only utilized on Windows 2000/NT systems. For the article on Windows Server 2003 onwards, please reference this article: http://support.microsoft.com/kb/251192/en-us?p=1.
Linux
Linux dedicated servers are also supported.
A first description of how-to setup an ArmA linuxserver has been posted on the official BI forums. You may follow these few steps that illustrate a setup on a Debian-based machine:
Please note that you can create other users than the standard player to configure different quality settings. All you need is an directory named and therein a .armaprofile as the configuration file. Then simply start the server with the optional parameter -name= .
When you’re a Linux beginner and encounter problems without adequate error messages, then your distribution is probably missing necessary packages.
For instance Unbuntu hardy 8.04 LTS amd64 (64bit) Desktop:
- package build-essential (11.3ubuntu1) and all of it is required packages for the ArmA install script to work
- package ia32-libs (2.2ubuntu11) and all of it is required packages for the ArmA 32bit server application to run on the 64bit operation system.
In case your linux distribution doesnt have a package set of libraries like the ia32-libs are, I managed to get the server running on Archlinux 64bit by installing the following packages as 32bit versions:
In case you encounter «Server died, waiting to restart. » instantly after the server was created, you may have SElinux enabled. (Fedora Core)
Number of open files limit
If you are running some mods and/or have a lot of missions on the server, you will hit the limit of open files allowed. This is a Linux/Unix specific issue. There are different settings you may need to tweak.
For once you may need to tweak the system-wide setting for max-files-open (See [1]). Then you might still need to allow the individual user that runs the Arma server to open enough files. The standard setting on Ubuntu 11.0 64-Bit was 1024 which might be too low.
Solution: Change /etc/security/limits.conf.
To raise this limit for every user put the following in at the bottom and save: