Segmentation Fault error.

[Killswitch]

I'll echo what MaSSive said: don't run the A2 game servers as the root user. Create a new, normal user account for that.

Now, regarding your "Segmentation fault" error. Seeing as how you're using CentOS, it is possible that SELinux is the culprit. See my post #4 in this thread: Linux-ArmA-and-Servers-Oh-my.

The short version is: if SELinux is in enforcing mode (and it should be), re-label the Arma server executables to allow them to use BattlEye:

chcon -t java_exec_t /home/games/arma2/server /home/games/arma2oa/server

You can remove the folder /home/games/arma2/BattlEye since you already have the lower-case variant named "battleye" with beserver.so in it.

[vladthemad]

Alright, sorry I've been busy working. I'll give this stuff a shot tomorrow. The third party download was what the forum post you posted links to. It eventually takes you to:

http://www.arma2.com/index.php?optio...r-1-10&lang=en

...and that karman.cc site is listed there.

Hmm...I was wondering if I needed to chmod the perms, as I've had to do that for other games, but I hadn't seen that anywhere in any of the wiki. Anyway, I'll try again tomorrow and update!

Thanks for the help so far guys!

[vladthemad]

Ok, I figured out the reason I had two battleye folders, one caps and one not...but as Killswitch said, the caps one doesnt seem to be needed. I also executed the chmod and the chcon commands as suggested. Still isn't running properly. Before I create a special account just to run this one program, can anyone explain why it shouldn't be run in root? I plan to set it up to auto start on power up after loss of power and reboot and it's just more to deal with if I have multiple accounts.

What I get now when I execute ./arma2server start is...



[root@vladserver arma2]# ./arma2server start
Starting ArmA 2 server...
./arma2server: line 31: ./home/games/arma2/2302.run: No such file or directory
[root@vladserver arma2]# nohup: redirecting stderr to stdout

[root@vladserver arma2]# ./arma2server status
Server should not be running...
[root@vladserver arma2]#


So...what the heck is 2302.run??!?

[Overlord]

2302.run (along with a file called 2302.pid) is files created, and used, by server. To do what? Just to check if server is running (and restart server if that file is missing). The 2302.pid file only holds the PID of main server process (open it in gedit and it only holds one number). Those files are deleted if server is shot down.

Your trouble regarding two be-folders:
Short description: Linux don't like capital letters!
A longer one; Linux actually see difference on small/CAPITAL letters, unlike windows which handles everything like. So what folder should the server use?
Arma 2 server will crash if you have capital letters in missions names, by default there is at least one in every mission you make, the first letter in island name. A short-cut to overcome this is to add tolower command in your start script. Then all capital letters (if any) will be converted to lower-case every time server start. Upload missions, restart server, problem solved.


SELinux or Security-Enhanced Linux is as it says, a distro focusing on security (which will impact different rights to different accounts). You should know what you're doing when setting up a game server on such distro, since a game server, by nature, is "open" (including addons). Or it will at least need some features which I suspect is disabled in SEL by default.
Not to offend anyone, but someone using root account as a normal account don't need SEL. And since it's a such a rigid distro, you'll run into lots of trouble which is non-existent on other distros (Debian/Ubuntu or what ever).

[Killswitch]

What I get now when I execute ./arma2server start is...

[root@vladserver arma2]# ./arma2server start
Starting ArmA 2 server...
./arma2server: line 31: ./home/games/arma2/2302.run: No such file or directory
[root@vladserver arma2]# nohup: redirecting stderr to stdout

See leading dot in the path? You probably have a typing error in the start script on the ARMA_DIR line. I'm guessing it looks like this:

ARMA_DIR=./home/games/arma2

Remove the dot at the beginning of the path:

ARMA_DIR=/home/games/arma2

Why should you not run the Arma servers as root? There are severaly reasons why, and they apply to server software in general:

• Because they don't need to.
• It's potentially unsafe to do so:
  
  • You could make a mistake when you are working with the servers logged in as root. You might accidentally delete important system files elsewhere.
  • There could be a bug in the software that could damage the rest of the server if the software was run as the superuser.

It's simply good practice to run a server with the minimum level of privileges it needs to do the job.