ARMA 2: Operation Arrowhead - Linux Dedicated server - 1.57.76894 & beta 1.57.76934

[Dwarden]

A2: OA linux dedicated server build 1.57.76894 download:
http://www.arma2.com/index.php?optio...rver-1-57&lang=

A2: OA linux dedicated server build 1.57.76934 beta download:
ftp://downloads.bistudio.com/arma2.c....76934.tar.bz2
MD5: 6ff243dec361dd89e90bb3848657057b

* beta has working multihome -ip= paramater and all fixes as in the public beta 1.57.76934 http://www.arma2.com/beta-patch.php


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

Please provide us with feedback to this topic.

Arma 2: Operation Arrowhead - Linux Standalone Server 1.57
================================================== =============

Copyrigt (c) 2010 Bohemia Interactive Studio. All rights reserved.

For more information please visit
http://community.bistudio.com/wiki/ArmA:_Dedicated_Server


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

previous thread about 1.56 beta linux : Spoiler:

show spoiler

http://forums.bistudio.com/showthread.php?t=110772

[MiBF]

Changelog are the same as in Win Server?

[76870] Fixed: Flood in RPT file caused by lines like "Object 2:200 (type Type_268) not found."
[76837] Fixed: Fake server monitor line after client connects.

[Dwarden]

Changelog are the same as in Win Server?

yes but the linux server contains all the changes between last 1.56 beta one and the win

[Dwarden]

beta 1.57.76934 released, happy Xmas to everyone

[Defunkt]

When using multihomed parameter (-ip=) with the post-1.57.76934 beta I get...

23:09:42 Dedicated host created.
23:09:43 Cannot start host on port 2302.
Error: createPeer failed
Error: createPeer failed
Error: createPeer failed
Error: createPeer failed
Error: createPeer failed
Error: createPeer failed

I was hoping the option to declare IP explicitly would help with a GameSpy reporting issue I'm experiencing (described HERE). Instead I get no listing (rather than a listing with 2500 ping) and the server cannot be reached at all (even when entering the IP via Remote) though the process continues to run. Thanks.

[thhamm]

beta 1.57.76934 released, happy Xmas to everyone

[Killswitch]

When using multihomed parameter (-ip=) with the post-1.57.76934 beta I get...

23:09:42 Dedicated host created.
23:09:43 Cannot start host on port 2302.
Error: createPeer failed
Error: createPeer failed
Error: createPeer failed
Error: createPeer failed
Error: createPeer failed
Error: createPeer failed

I was hoping the option to declare IP explicitly would help with a GameSpy reporting issue I'm experiencing (described HERE). Instead I get no listing (rather than a listing with 2500 ping) and the server cannot be reached at all (even when entering the IP via Remote) though the process continues to run. Thanks.

I can launch the Linux 1.57.76934 server with -ip=aaa.bbb.ccc.ddd just fine, so I don't think that's the cause of your problem. Notice the

23:09:43 Cannot start host on port 2302.

Sometimes, when you do ./arma2oaserver stop to stop the dedi, it isn't actually stopped, so double-check that there isn't an ArmA II process running when you try to launch it again. If there already is a server running, it will have "taken" port 2302 and that explains the error message you're seeing. You can use the ps command to show the currently running processes. If an ArmA II server is running there will be two processes related to that - the server itself and a bash process which runs the start script watchdog:

$ ps aux
...
...
16635 pts/0    S      0:00 /bin/bash ./arma2oaserver watchdog
16637 pts/0    Sl     0:18 /srv/arma2/server -server -config=server.cfg -port=2302 -pid=/srv/arma2/2302.pid -cpucount=2 -ip=aaa.bbb.ccc.ddd
...
...

If you then run ./arma2oaserver stop and those two processes aren't gone after that, use the kill command to stop them. Using the results of the above ps command output, I would run

$ kill 16635 16637

to really stop the ArmA II server. The actual process ID numbers will vary, of course.

[Defunkt]

Must have been the case as I just tried it again and the server launched okay and is viewable in the server list (but still with the 2500 ping unfortunately).

[Dwarden]

good , at least we know the multihome is working properly (multiple users confirmed) even on linux

i'm afraid the problem with packets must be dealt with Amazon (theirs routers/firewalls/server hosting) or GameSpy (theirs protocol and master server)

[byteslam]

...I am abroad and unable to patch/update the server for our gamers (just online with usb stick) until 4th January.
Unfortunatly, BI is still unable to provide a update package for Linux with everything included. Can someone help me out with an rsync source to a already patched server?