arma2 on Ubuntu server running on another port?

[m0dg0d 1]

Hello guys,

As my title: arma2 on Ubuntu server running on another port.

Its running fine and everyone can acces it but i can not connect it with a Rcon tools..

Yes i have BEserver.cfg but if i ''port check'' my server it says 2302 is closed while its on and people acces it.

Does anyone knows a command to run it port 2302?

I run it by ./arma2server start

Thanks,

m0dg0d

[Overlord 0]

Ports are declared in your start-script

PORT=2302

[m0dg0d 1]

Right, how i edit my start-script? what is it named? i mean the file

[redshirt_ensign 11]

"arma2server" is the start script.

run command "less arma2server" to view contents (press Q to exit when done).

If you haven't edited it, it is doubtful that your port is non standard. Are you sure you are putting the beserver.cfg in the right directory?

EDIT: What did you "port check" with anyway? You know it is UDP port 2302 right?

If people are playing arma on port 2302 then that is the port BE will be using (but it won't run at all if it doesn't find the cfg file where it expects it to be).

You will know if your beserver.cfg file has actually been found by BE if the filename gets changed to beserver-RANDOM.cfg ("RANDOM" will just be some random chars)

Edited July 16, 2013 by redshirt_ensign

[m0dg0d 1]

This is all in the arma2server file:

#!/bin/bash

#

# armaserver: ArmA 2 Linux Dedicated Server Control Script

# © 2011 BIStudio

# ArmA 2 binary version must be 1.04 or later

#

#=======================================================================

#======== CONFIGURATION PARAMETERS ========

#======== MUST BE EDITED MANUALLY TO FIT YOUR SYSTEM PARAMETERS ========

#=======================================================================

ARMA_DIR=/opt/arma2

CONFIG=server.cfg

PORT=2302

PIDFILE=${ARMA_DIR}/${PORT}.pid

RUNFILE=${ARMA_DIR}/${PORT}.run

LOGFILE=${ARMA_DIR}/log.${PORT}.txt

SERVER=${ARMA_DIR}/server

#=======================================================================

ulimit -c 1000000

case "$1" in

start)

if [ -f ${RUNFILE} ]; then

$0 stop

fi

echo "Starting ArmA 2 server..."

# file to mark we want server running...

echo "go" >${RUNFILE}

# launch the background watchdog process to run the server

nohup </dev/null >/dev/null $0 watchdog &

;;

stop)

echo "Stopping ArmA 2 server..."

if [ -f ${RUNFILE} ]; then

# ask watcher process to exit by deleting its runfile...

rm -f ${RUNFILE}

fi

# and terminate ArmA 2 server process

if [ -f ${PIDFILE} ]; then

kill -TERM $(< ${PIDFILE})

if [ -f ${PIDFILE} ]; then

rm -f ${PIDFILE}

fi

fi

;;

status)

if [ -f ${RUNFILE} ]; then

echo "Server should be running..."

else

echo "Server should not be running..."

fi

if [ -f ${PIDFILE} ]; then

PID=$(< ${PIDFILE})

echo "PID file exists (PID=${PID})..."

if [ -f /proc/${PID}/cmdline ]; then

echo "Server process seems to be running..."

fi

fi

;;

check)

echo -n "ArmA 2 directory: ${ARMA_DIR} "

if [ -d ${ARMA_DIR} ]; then

echo "OK"

else

echo "MISSING!"

fi

echo -n "Server executable: ${SERVER} "

if [ -x ${SERVER} ]; then

echo "OK"

else

echo "ERROR!"

fi

echo "Port number: ${PORT}"

echo -n "Config file: ${CONFIG} "

if [ -f ${CONFIG} ]; then

echo "OK"

else

echo "MISSING!"

fi

echo "PID file: ${PIDFILE}"

echo "RUN file: ${RUNFILE}"

;;

restart)

$0 stop

$0 start

;;

watchdog)

# this is a background watchdog process. Do not start directly

while [ -f ${RUNFILE} ]; do

# launch the server...

cd ${ARMA_DIR}

echo >>${LOGFILE} "WATCHDOG ($$): [$(date)] Starting server (port ${PORT})..."

${SERVER} >>${LOGFILE} 2>&1 -server -config=${CONFIG} -port=${PORT} -pid=${PIDFILE}

if [ -f ${RUNFILE} ]; then

echo >>${LOGFILE} "WATCHDOG ($$): [$(date)] Server died, waiting to restart..."

sleep 5s

else

echo >>${LOGFILE} "WATCHDOG ($$): [$(date)] Server shutdown intentional, watchdog terminating"

fi

done

;;

*)

echo "$0 (start|stop|restart|status|check)"

;;

esac

BEserver.cfg must be in the battleye folder right? With BE or be?

is my startup script good for RCON acces?

Thanks

[redshirt_ensign 11]

Yep, that script is completely default. You will be running on 2302 (but we already pretty much knew that).

You have to understand, Arma2 doesn't have RCON natively. It is BattlEye that provides an RCON interface to the server. So (with the exception of manually defining a new -bepath param) there is nothing in the startup script that will affect you getting RCON access. You need to concentrate on BattlEye.

With the linux install (assuming you have done it all correctly), your linux BattlEye lib "beserver.so" should be at

[ARMA2DIR]/expansion/battleye/beserver.so

and you should make the cfg file at

[ARMA2DIR]/expansion/battleye/beserver.cfg

along with

[ARMA2DIR]/expansion/battleye/bans.txt

[ARMA2DIR]/expansion/battleye/scripts.txt

[ARMA2DIR]/expansion/battleye/remoteexec.txt

etc etc

and Yes, every single file (including mission PBOs) should be in lowercase for linux.

Like I said, you will know if you have got the cfg file successfully found if it gets renamed to "beserver_active_abc1234.cfg" after you start the server (where abc1234 is some random value).

If the cfg file doesn't get renamed, don't even bother trying to connect an RCON client as it won't be listening for it.

[m0dg0d 1]

Got Rcon working now,

Thank you very much