Jump to content
Sign in to follow this  

ARMA 2: Operation Arrowhead - Linux Server beta 1.60.94342

Recommended Posts







MD5: 735B353EE6F2B7F04E91174B27DFD5D0

SHA-1: 0E40B5888AC961A5A1A9905117B06EFB74EA82B5

Last fix:

* code sync with win platform

* recent crashfixes (as for windows, were crossplaform)

* channel disabling support as for windows

*changes and tweaks from windows branch including for netcode

*some crashes and issues across all platforms

previous fix:

*resolved crash on custom face textures (please verify if custom faces work in MP)

*[89964] Fixed: Linux servers were never green in server list.

older fix:

*resolved long loading times (this time it should work :) )

*resolved issue with "Failed to load TextureHeaderManager" , no need use -noTexHeaders commandline parameter!

Warning: This is 1.60 branch release

Note that it requires Arma 2: Operation Arrowhead data to be updated to version 1.60 first in order to run properly.

ideal to combine with latest OA beta client:

Please provide us with feedback to this topic.

* this version brings linux in sync with actual windows server improvements and ai/mp fixes ...

Arma 2: Operation Arrowhead - Linux Standalone Server 1.60


Copyrigt © 2010 Bohemia Interactive Studio. All rights reserved.

For more information please visit


Installation instructions:


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] <pid>

5. Running server can be stopped by executing:

$ kill -s SIGINT <pid>

Where <pid> is process-id of mother server thread (printed out in

"nohup" command).

6. ArmA2 ArrowHead server has a feature: command-line parameter

"-pid=<pid_file>". It causes creation of <pid_file> with

PID of root ArmA2 process. If IP port specified in "-port=<nn>"

parameter is busy (in usage), ArmA2 will terminate immediately

and <pid_file> won't be written..

7. The "arma2server" script is provided for automatic server

start/restart/status query/etc. Please be sure to edit


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).

previous thread about 1.60.93616 beta linux :

Share this post

Link to post
Share on other sites
*[89964] Fixed: Linux servers were never green in server list.

This one is quite old now, isn't it? Been working the last five servers :)

Thank you any way Big D, BIS and community.

I have one "small" issue ftm, watchdog don't work in the two latest betas (not including this one). I've not reported it due to recent changes I've done on my server. Will check this one out, reconfigure server, and see if it's (most probably) my own fault..

Share this post

Link to post
Share on other sites

you see the build number next to the line right? you do realize i just copy and paste the content of the post? :)

Share this post

Link to post
Share on other sites

anyone get this in the logfile when the server starts?

WATCHDOG (20671): [sun Jul 1 12:49:57 CEST 2012] Starting server (port 2302)...

Cannot register unknown string STR_FXAA

Cannot register unknown string STR_SHARP

Cannot register unknown string STR_SMAA

Cannot register unknown string STR_ATOC_GRASS

Cannot register unknown string STR_ATOC_TREEOA

Cannot register unknown string STR_ATOC_TREEOA_GRASS

Cannot register unknown string STR_ATOC_TREEA2

Cannot register unknown string STR_ATOC_TREEA2_GRASS

Cannot register unknown string STR_ATOC_TREEOA_TREEA2

Cannot register unknown string STR_ATOC_TREEOA_TREEA2_GRASS

12:50:03 Dedicated host created.

12:50:04 BattlEye Server: Initialized (v1.126)

12:50:04 Host identity created.



Share this post

Link to post
Share on other sites

There are new text strings in the betas that aren't there in the stock 1.60 game data files. Upload the expansion\beta\expansion folder from your Windows installation to the Linux server and then add the following to the OTHERPARAMS line in the Linux server startup script ("arma2oaserver"):


As an example, the OTHERPARAMS line would look something like this afterwards:

OTHERPARAMS='-cpucount=2 -beta=expansion/beta;expansion/beta/expansion'

That will fix the "unknown string" errors.

Edited by Killswitch

Share this post

Link to post
Share on other sites

thanks a lot, that fixed it... i never used beta for the client. But now i do too. ;)

Share this post

Link to post
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in

Sign In Now
Sign in to follow this