A2OA Linux Server Beta 1.57.77737

[Maruk]

A2: OA linux dedicated server build 1.57.77737 beta download:
ftp://downloads.bistudio.com/arma2.com/update/a2oa-server-1.57.77737.tar.bz2.

Most important are stability and security related fixes.


* 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 (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 : http://forums.bistudio.com/showthread.php?t=110772

[=WFL= Sgt Bilko]

Will latest client full patch (1.57.76815) run with this server version?

---------- Post added at 11:34 PM ---------- Previous post was at 11:33 PM ----------

I guess this answered my question:
Note that it requires Arma 2: Operation Arrowhead data to be updated to version 1.57 first in order to run properly.

Sorry!

[djczing]

Oh yeah ! Thanks for remembering us linux servers !

This latest patchlevel is great btw - nice to see it in Linux form !

[ShadowHatesYou]

I'm running in to this problem using the linux dedicated server:


13:11:17 Dedicated host created.
13:11:18 BattlEye Server: Initialized (v1.113)
13:11:18 Host identity created.
ArmA 2 OA Console version 1.57 : port 2302 - Sockets
13:11:33 ShadowHatesYou uses modified data file - Arma 2: British Armed Forces (Lite);Arma 2: Private Military Company (Lite);arm
13:11:33 Player ShadowHatesYou connecting.
13:11:34 Player ShadowHatesYou connected (id=4986502).
13:11:42 Admin ShadowHatesYou logged in.
Cannot open file 'MPMissions\co30_Domination_2_54A2_West_OA.Takistan.pbo'
111/00/28, 13:11:45 Critical:Destroying running thread!
WATCHDOG (29980): [Fri Jan 28 13:11:45 UTC 2011] Server died, waiting to restart...


So, I login and no mission is loaded. I login as admin, and then do #missions, and the dedi crashes. Any ideas about this? The only thing that stands out to me is that the wrong slash is used.
MPMissions\co30_Domination_2_54A2_West_OA.Takistan.pbo isn't a valid path in linux, where as
MPMissions/co30_Domination_2_54A2_West_OA.Takistan.pbo is a valid path. \ is used for escaping, / is used for directories. The file *does* exist, it *does* have the proper permissions, and I've even 777ed it.



edit: Finally managed to get strace to give me meaningful output by attaching after the server initialized (via strace -f -p <PID)>


[pid 5418] open("mpmissions/", O_RDONLY|O_NONBLOCK|O_LARGEFILE|O_DIRECTORY|O_CLOEXEC) = 155
[pid 5418] getdents(155, /* 1 entries */, 32768) = 168
[pid 5418] stat64("mpmissions/.", {st_mode=S_IFDIR|0755, st_size=117, ...}) = 0
[pid 5418] stat64("mpmissions/..", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
[pid 5418] stat64("mpmissions/co30_Domination_2_54A2_West_OA.Takistan.pbo", {st_mode=S_IFREG|0644, st_size=2531113, ...}) = 0
[pid 5418] stat64("mpmissions/co30_Domination_2_54A2_West_OA.Takistan.pbo", {st_mode=S_IFREG|0644, st_size=2531113, ...}) = 0


I've symlinked mpmissions to MPMissions, and it's still crashing. Later on in the strace, there's this:


[pid 5419] open("/home/shadow/arma/arma2oa/mpmissions/co30_domination_2_54a2_west_oa.takistan.pbo", O_RDONLY <unfinished ...>


What the hell? I make another symlink, and now everything works. FIX YOUR ERROR OUTPUT!

[Sickboy]

Doesn't seem like you ran toLower to lower-case all the files and folders in the server folder?
Not sure about the implications.

[Dwarden]

I'm running in to this problem using the linux dedicated server:



So, I login and no mission is loaded. I login as admin, and then do #missions, and the dedi crashes. Any ideas about this? The only thing that stands out to me is that the wrong slash is used. isn't a valid path in linux, where as is a valid path. \ is used for escaping, / is used for directories. The file *does* exist, it *does* have the proper permissions, and I've even 777ed it.

what's your startup commandline for the server ?

also what you got inside the MPmissions on the server

[ShadowHatesYou]

For debugging purposes I started using "./server -ip 208.71.118.187 -config=server.cfg -cpuCount=12". The problem was case sensitivity, despite the error log telling me it was looking in MPMissions and not mpmissions, as well as looking for co30_domination_2_54a2_west_oa.takistan.pbo instead of co30_Domination_2_54A2_West_OA.Takistan.pbo like it said.


edit: Last 1000 lines of strace:

http://squatthis.net/strace.txt

You can see how this doesn't match up with the errors generated.

[djczing]

Yup. Upper case missions will crash your linux server every time - even when just trying to list missions.

[{SF} Astra]

Just installed - running good so fare.
Thanks a lot.

[Clawhammer]

We have the same problem like ShadowHatesYou with our Ubuntu Server in combination with ACE1.8

With ACE 1.7 or without ACE1.8 everythink works fine

Hope you can help us, we have the same problems (server crash, missing missions)

Really thank you!

[djczing]

I started using this server, wiht the latest client beta (77819 iirc).

I got a server crash after a couple of hours, but the log file indicated many many script errors from the mission, so its hard to blame it on the server. The server/client were also heavily modded (my normal state of operation).

The remaining question is this: Can I run the 77819 client beta against this server rev ?

[Dwarden]

yes this server will work fine against beta client 77819

[djczing]

Thanks Dwarden.

Ran a BE Warfare (ACE) mission over the last couple of days.

No issues. Nice job. Performance (server FPS) was higher than im used to seeing it. Use of other cores was really good. I dont know if im imagining it, but the linux server appears to use the other cores more efficiently (more load on the non-AI thread cores) than the windows server, and the linux server appears to have better overall performance. Cant say for sure, but that has been my observation for awhile now (like since 1.56??).

The new vehicle/convoy/moving code is really very nice, as is the new soldier AI.

Great job - thanks !

[djczing]

Well after using this server for awhile now, my conclusion is that it is less stable than previous releases -- it crashes much more than previous releases, and is hard to nail down why.

The stdout/stderr output has nothing revealing, but I do have several core files...

[Fireball]

The stdout/stderr output has nothing revealing, but I do have several core files...

Open a ticket in the CIT (http://dev-heaven.net/projects/cis/wiki) and attach the zipped core files, assign to Dwarden.

[byteslam]

Hi, we recognized a possibility to switch teams (warefare) without kick. This is possible in all betas after the official version v1.57.76894.
We can confirm that stability and performance are enhanced in the latest release, but to swap team while a match is running is such a big disadvantage that we use the latest official release.

Will this problem be fixed in the next Beta for Linux?

Thanks in advance

[djczing]

Mmmm I /think/ there is an issue with the linux server hitting > 128 missions in mpmissions causing server crash ?

Anyone seen this ?

[Sickboy]

Mmmm I /think/ there is an issue with the linux server hitting > 128 missions in mpmissions causing server crash ?

Anyone seen this ?

http://dev-heaven.net/issues/17018#note-8

[djczing]

Hmm Ill see if I can isolate it further.

What I did to make it work was to put mission files in mpmissions into another folder until it stopped.

Im running no sound (acex_sm or any other) on the server side.

Might be something as simple as exceeding openfiles_max or whatever the linux equiv is.

Thanks as always sickboy. Ill post if/when I narrow down the conditions a bit more.

[djczing]

Yeah that got it.

It seems adding CAA1 to ACE and the rest of my mods pushed me over the limit.

Doubled user 'arma's file limits and its working fine now.

[Reezo]

At SR5 Tactical we've been running this server build since it was released and we've had no problems at all. Gameplay is smooth, no crashes at all. We run ACE2, ACRE and some other mods, mostly scenarios.

[daikan]

Has anyone been able to configure the server for /etc/init.d/arma2oaserver automated startup so it runs as a non-root user?

The provided script will run the server as root which is not a very smart thing to do...

I tried with changing the start command to this:


...
USER=arma2user
...
su ${USER} -c "<OLD START CMD>"
...

but I'm getting errors like "invalid option -- o" from su... seems like a variable expansion problem (btw this is on Debian Lenny).

Any help is greatly appreciated.