Jump to content
Sign in to follow this  
soulfly83

nohup: redirecting stderr to stdout

Recommended Posts

getting this message everytime i try start arm2 or oa server

nohup: redirecting stderr to stdout

root@:/home/arma2# ./arma2server restart

Stopping ArmA 2 server...

Starting ArmA 2 server...

root@:/home/arma2# nohup: redirecting stderr to stdout

root@e:/home/arma2# ./arma2server status

Server should be running...

root@:/home/arma2# ./arma2server check

ArmA 2 directory: /home/arma2 OK

Server executable: /home/arma2/server OK

Port number: 2302

Config file: server.cfg OK

PID file: /home/arma2/2302.pid

RUN file: /home/arma2/2302.run

root@:/home/arma2#

edit: cant find server

edit: error log

./arma2server: line 108: /home/arma2/server: No such file or directory

WATCHDOG (1957): [Wed Apr 17 00:31:39 MSK 2013] Server died, waiting to restart...

WATCHDOG (1957): [Wed Apr 17 00:31:44 MSK 2013] Starting server (port 2302)...

./arma2server: line 108: /home/arma2/server: No such file or directory

WATCHDOG (1957): [Wed Apr 17 00:31:44 MSK 2013] Server died, waiting to restart...

WATCHDOG (1957): [Wed Apr 17 00:31:49 MSK 2013] Starting server (port 2302)...

./arma2server: line 108: /home/arma2/server: No such file or directory

WATCHDOG (1957): [Wed Apr 17 00:31:54 MSK 2013] Server died, waiting to restart...

Edited by soulfly83

Share this post


Link to post
Share on other sites

Are you trying to run Arma2 or Arma2OA server?

Is everything in that /home/arma2/ dir?

Post up your arma2server script. Something in that script (at line 108) is referring to a file/path that doesn't exist.

Share this post


Link to post
Share on other sites

I want to run a oa server but ive tryed to start each one to see if any works, both have the same problem.

Yes all in home/arma2 or home/arma2arrowhead

Heres the arma2 server script:

#!/bin/bash
#
# armaserver: ArmA 2 Linux Dedicated Server Control Script
#  (c) 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=/home/arma2
CONFIG=/home/arma2/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

Arma2.cfg

// These options are created by default
language="English";
adapter=-1;
3D_Performance=1.000000;
Resolution_W=800;
Resolution_H=600;
Resolution_Bpp=32;


// These options are important for performance tuning

MinBandwidth = 131072;			// Bandwidth the server is guaranteed to have (in bps). This value helps server to estimate bandwidth available. Increasing it to too optimistic values can increase lag and CPU load, as too many messages will be sent but discarded. Default: 131072
MaxBandwidth = 10000000000;		// Bandwidth the server is guaranteed to never have. This value helps the server to estimate bandwidth available.

MaxMsgSend = 128;			// Maximum number of messages that can be sent in one simulation cycle. Increasing this value can decrease lag on high upload bandwidth servers. Default: 128
MaxSizeGuaranteed = 512;		// Maximum size of guaranteed packet in bytes (without headers). Small messages are packed to larger frames. Guaranteed messages are used for non-repetitive events like shooting. Default: 512
MaxSizeNonguaranteed = 256;		// Maximum size of non-guaranteed packet in bytes (without headers). Non-guaranteed messages are used for repetitive updates like soldier or vehicle position. Increasing this value may improve bandwidth requirement, but it may increase lag. Default: 256

MinErrorToSend = 0.001;			// Minimal error to send updates across network. Using a smaller value can make units observed by binoculars or sniper rifle to move smoother. Default: 0.001
MinErrorToSendNear = 0.01;		// Minimal error to send updates across network for near units. Using larger value can reduce traffic sent for near units. Used to control client to server traffic as well. Default: 0.01

MaxCustomFileSize = 0;			// (bytes) Users with custom face or custom sound larger than this size are kicked when trying to connect.

Arma2 server cfg

//
// server.cfg
//
// comments are written with "//" in front of them.


// GLOBAL SETTINGS
hostname = "Celtic Alliance Clan";			// The name of the server that shall be displayed in the public server list
password = "";						// Password for joining, eg connecting to the server
passwordAdmin = "xyz";					// Password to become server admin. When you're in Arma MP and connected to the server, type '#login xyz'
//reportingIP = "armedass.master.gamespy.com";		// For ArmA1 publicly list your server on GameSpy. Leave empty for private servers
//reportingIP = "arma2pc.master.gamespy.com";		// For ArmA2 publicly list your server on GameSpy. Leave empty for private servers
reportingIP = "arma2oapc.master.gamespy.com";		// For Arma2: Operation Arrowhead
logFile = "server_console.log";				// Tells ArmA-server where the logfile should go and what it should be called


// WELCOME MESSAGE ("message of the day")
// It can be several lines, separated by comma
// Empty messages "" will not be displayed at all but are only for increasing the interval
motd[] = {
"", "",  
"Two empty lines above for increasing interval",
"Welcome to our server",
"", "",  
"We are looking for fun - Join us Now !",
"http://www.example.com",
"One more empty line below for increasing interval",
""
};
motdInterval = 5;					// Time interval (in seconds) between each message


// JOINING RULES
checkfiles[] = {};					// Outdated.
maxPlayers = 64;					// Maximum amount of players. Civilians and watchers, beholder, bystanders and so on also count as player.
kickDuplicate = 1;					// Each ArmA version has its own ID. If kickDuplicate is set to 1, a player will be kicked when he joins a server where another player with the same ID is playing.
verifySignatures = 2;					// Verifies .pbos against .bisign files. Valid values 0 (disabled), 1 (prefer v2 sigs but accept v1 too) and 2 (only v2 sigs are allowed). 
equalModRequired = 0;					// Outdated. If set to 1, player has to use exactly the same -mod= startup parameter as the server.
//requiredBuild = 12345					// Require clients joining to have at least build 12345 of game, preventing obsolete clients to connect


// VOTING
voteMissionPlayers = 1;					// Tells the server how many people must connect so that it displays the mission selection screen.
voteThreshold = 0.33;					// 33% or more players need to vote for something, for example an admin or a new map, to become effective


// INGAME SETTINGS
disableVoN = 1;						// If set to 1, Voice over Net will not be available
vonCodecQuality = 0;					// since 1.62.95417 supports range 1-20 //since 1.63.x will supports range 1-30 //8kHz is 0-10, 16kHz is 11-20, 32kHz is 21-30
persistent = 1;						// If 1, missions still run on even after the last player disconnected.
timeStampFormat = "short";				// Set the timestamp format used on each report line in server-side RPT file. Possible values are "none" (default),"short","full".
BattlEye = 1;                                           // Server to use BattlEye system


// SCRIPTING ISSUES
onUserConnected = "";					//
onUserDisconnected = "";				//
doubleIdDetected = "";					//
//regularCheck = "{}";                                  //  Server checks files from time to time by hashing them and comparing the hash to the hash values of the clients. Causes heavy I/O, uncomment to disable feature - READ WARNING ABOVE - makes cheating possible!


// SIGNATURE VERIFICATION
onUnsignedData = "kick (_this select 0)";		// unsigned data detected
onHackedData = "ban (_this select 0)";			// tampering of the signature detected
onDifferentData = "";					// data with a valid signature, but different version than the one present on server detected


// MISSIONS CYCLE (see below)
class Missions {};

And OA server cfg

//
// server.cfg
//
// comments are written with "//" in front of them.


// GLOBAL SETTINGS
hostname = "Celtic Alliance Clan";			// The name of the server that shall be displayed in the public server list
password = "";						// Password for joining, eg connecting to the server
passwordAdmin = "xyz";					// Password to become server admin. When you're in Arma MP and connected to the server, type '#login xyz'
//reportingIP = "armedass.master.gamespy.com";		// For ArmA1 publicly list your server on GameSpy. Leave empty for private servers
//reportingIP = "arma2pc.master.gamespy.com";		// For ArmA2 publicly list your server on GameSpy. Leave empty for private servers
reportingIP = "arma2oapc.master.gamespy.com";		// For Arma2: Operation Arrowhead
logFile = "server_console.log";				// Tells ArmA-server where the logfile should go and what it should be called


// WELCOME MESSAGE ("message of the day")
// It can be several lines, separated by comma
// Empty messages "" will not be displayed at all but are only for increasing the interval
motd[] = {
"", "",  
"Two empty lines above for increasing interval",
"Welcome to our server",
"", "",  
"We are looking for fun - Join us Now !",
"http://www.example.com",
"One more empty line below for increasing interval",
""
};
motdInterval = 5;					// Time interval (in seconds) between each message


// JOINING RULES
checkfiles[] = {};					// Outdated.
maxPlayers = 64;					// Maximum amount of players. Civilians and watchers, beholder, bystanders and so on also count as player.
kickDuplicate = 1;					// Each ArmA version has its own ID. If kickDuplicate is set to 1, a player will be kicked when he joins a server where another player with the same ID is playing.
verifySignatures = 2;					// Verifies .pbos against .bisign files. Valid values 0 (disabled), 1 (prefer v2 sigs but accept v1 too) and 2 (only v2 sigs are allowed). 
equalModRequired = 0;					// Outdated. If set to 1, player has to use exactly the same -mod= startup parameter as the server.
//requiredBuild = 12345					// Require clients joining to have at least build 12345 of game, preventing obsolete clients to connect


// VOTING
voteMissionPlayers = 1;					// Tells the server how many people must connect so that it displays the mission selection screen.
voteThreshold = 0.33;					// 33% or more players need to vote for something, for example an admin or a new map, to become effective


// INGAME SETTINGS
disableVoN = 1;						// If set to 1, Voice over Net will not be available
vonCodecQuality = 0;					// since 1.62.95417 supports range 1-20 //since 1.63.x will supports range 1-30 //8kHz is 0-10, 16kHz is 11-20, 32kHz is 21-30
persistent = 1;						// If 1, missions still run on even after the last player disconnected.
timeStampFormat = "short";				// Set the timestamp format used on each report line in server-side RPT file. Possible values are "none" (default),"short","full".
BattlEye = 1;                                           // Server to use BattlEye system


// SCRIPTING ISSUES
onUserConnected = "";					//
onUserDisconnected = "";				//
doubleIdDetected = "";					//
//regularCheck = "{}";                                  //  Server checks files from time to time by hashing them and comparing the hash to the hash values of the clients. Causes heavy I/O, uncomment to disable feature - READ WARNING ABOVE - makes cheating possible!


// SIGNATURE VERIFICATION
onUnsignedData = "kick (_this select 0)";		// unsigned data detected
onHackedData = "ban (_this select 0)";			// tampering of the signature detected
onDifferentData = "";					// data with a valid signature, but different version than the one present on server detected


// MISSIONS CYCLE (see below)
class Missions {};

The cfg files will probaly need tweeking but they should be good enough to start server

If you need anything help to find problem let me know, thanks for help

Share this post


Link to post
Share on other sites

Post the output of

ls -al /home/arma2

and

ls -al /home/arma2arrowhead

I think you must have the files/dirs not quite right.

Also, if you want OA then lets work on that and not A2. Post up you arma2oaserver and we will work on getting OA going.

Share this post


Link to post
Share on other sites
Post the output of

ls -al /home/arma2

and

ls -al /home/arma2arrowhead

I think you must have the files/dirs not quite right.

Also, if you want OA then lets work on that and not A2. Post up you arma2oaserver and we will work on getting OA going.

Arma 2

root@:~# ls -al /home/arma2
total 27212
drwxr-xr-x 11 root root     4096 Apr 16 22:20 .
drwxr-xr-x  6 root root    20480 Apr 16 23:44 ..
-rw-r--r--  1 root root        3 Apr 16 22:20 2302.run
-rw-r--r--  1 root root     1581 Mar 22 00:24 33910_install.vdf
drwxr-xr-x  2 root root     4096 Jan 27 16:52 BattlEye
-rw-r--r--  1 root root  5472152 Dec 16  2011 a2-server-1.11.87389.tar.bz2
drwxr-xr-x  2 root root    12288 Apr 16 22:15 addons
-rw-r--r--  1 root root     1837 Apr 17 14:23 arma2.cfg
-rw-r--r--  1 root root      545 Jan 27 12:04 arma2.changelog109
-rw-r--r--  1 root root       74 Jan 27 12:02 arma2_ogg.cmd
-rwxrwxr-x  1  501  502     2794 Apr 17 00:34 arma2server
drwxr-xr-x  2 root root     4096 Apr 16 22:15 battleye
drwxr-xr-x  2 root root     4096 Apr 16 22:15 besetup
-rw-r--r--  1 root root      148 Jan 27 12:00 bis.url
-rw-r--r--  1 root root      254 Jan 27 16:34 checkfilelist.lst
drwxr-xr-x  2 root root    12288 Apr 16 22:15 directx
drwxr-xr-x  2 root root     4096 Feb 14 21:14 dta
-rwxrwxrwx  1  501  502      227 Jun  8  2011 install
drwxr-xr-x  2 root root     4096 Feb 14 21:14 keys
-rw-r--r--  1 root root  6235779 Apr 18 12:21 log.2302.txt
drwxr-xr-x  2 root root     4096 Feb 14 21:14 missions
drwxr-xr-x  2 root root     4096 Feb 14 21:14 mpmissions
-rw-rw-rw-  1  501  502     2315 Jun  8  2011 readme.txt
-rwxr-xr-x  1  501  502 16004012 Dec 16  2011 server
-rw-r--r--  1 root root     3743 Apr 16 17:05 server.cfg
-rwxr-xr-x  1 root root    13212 Apr 16 22:15 tolower
-rw-rw-rw-  1  501  502     3040 Sep 13  2007 tolower.c

OA

root@:~# ls -al /home/arma2arrowhead
total 44472
drwxr-xr-x 16 root root     4096 Apr 17 00:35 .
drwxr-xr-x  6 root root    20480 Apr 16 23:44 ..
-rw-r--r--  1 root root        3 Apr 17 00:35 2302.run
-rw-r--r--  1 root root     2306 Mar 23 21:56 33930_install.vdf
-rw-r--r--  1 root root     1752 Jan 27 12:11 33933_install.vdf
-rw-r--r--  1 root root     1443 Mar 23 21:56 33934_install.vdf
-rw-r--r--  1 root root     1449 Jan 27 17:24 65700_install.vdf
-rw-r--r--  1 root root     1459 Jan 27 17:24 65720_install.vdf
drwxr-xr-x  3 root root     4096 Apr 16 23:47 @dayz
drwxr-xr-x  7 root root     4096 Jan 27 17:02 Expansion
-rw-r--r--  1 root root     2911 Jan 27 13:08 _runa2co.cmd
-rw-r--r--  1 root root     2166 Jan 27 13:09 _runa2co_beta.cmd
-rw-r--r--  1 root root  5635468 Feb 25 13:14 a2oa-server-1.62.102451.tar.bz2
drwxr-xr-x  3 root root     4096 Apr 16 23:47 acr
-rw-r--r--  1 root root  5185156 Jan 27 12:38 arma2oa_manual.pdf
-rw-r--r--  1 root root       74 Jan 27 12:38 arma2oa_ogg.cmd
-rw-r--r--  1 root root    25819 Jan 27 12:38 arma2oa_patch_1_59_readme.txt
-rw-r--r--  1 root root    14269 Jan 27 12:38 arma2oa_update_162_readme.txt
-rwxrwxrwx  1 root root     2842 Apr 17 00:35 arma2oaserver
drwxr-xr-x  3 root root     4096 Apr 16 23:47 baf
drwxr-xr-x  2 root root     4096 Apr 16 23:47 besetup
-rw-r--r--  1 root root      226 Jan 27 12:11 bis.url
-rw-r--r--  1 root root      375 Mar 11 22:12 checkfilelist.lst
drwxr-xr-x  2 root root    12288 Apr 16 23:47 common
drwxr-xr-x  2 root root    12288 Apr 16 23:47 directx
drwxr-xr-x  5 root root     4096 Apr 16 23:47 dlcsetup
drwxr-xr-x  2 root root     4096 Jan 27 17:31 dll
drwxr-xr-x  3 root root     4096 Apr 16 23:47 expansion
-rwxrwxrwx  1 root root      351 Aug  3  2012 install
-rw-r--r--  1 root root      940 Mar 24 14:44 installscript.vdf
drwxr-xr-x  2 root root     4096 Jan 27 13:08 keys
-rw-r--r--  1 root root 18777282 Apr 18 12:22 log.2302.txt
drwxr-xr-x  2 root root     4096 Jan 27 13:10 missions
drwxr-xr-x  2 root root     4096 Jan 27 13:10 mpmissions
drwxr-xr-x  3 root root     4096 Apr 16 23:47 pmc
-rwxrwxrwx  1 root root     4089 Feb  6  2012 readme.txt
-rw-r--r--  1 root root     1986 Jan 27 17:31 readme_fxaa.txt
-rw-r--r--  1 root root     3387 Jan 27 13:03 readme_oa.txt
-rw-r--r--  1 root root     1930 Jan 27 17:31 readme_smaa.txt
-rwxrwxrwx  1 root root 15676336 Feb 25 13:14 server
-rw-r--r--  1 root root     3744 Apr 16 23:48 server.cfg
-rw-r--r--  1 root root        7 Jan 27 17:24 steam_appid.txt
-rwxr-xr-x  1 root root    13212 Apr 16 23:47 tolower
-rwxrwxrwx  1 root root     3137 Sep 13  2007 tolower.c

OA arma2oaserver

#!/bin/bash
#
# armaserver: ArmA 2 Linux Dedicated Server Control Script
#  (c) 2010 BIStudio
#  ArmA 2 binary version must be 1.04 or later
#

#=======================================================================
#========               CONFIGURATION PARAMETERS                ========
#======== MUST BE EDITED MANUALLY TO FIT YOUR SYSTEM PARAMETERS ========
#=======================================================================
ARMA_DIR=/home/arma2arrowhead
CONFIG=/home/arma2arrowhead/server.cfg
PORT=2302
PIDFILE=${ARMA_DIR}/${PORT}.pid
RUNFILE=${ARMA_DIR}/${PORT}.run
LOGFILE=${ARMA_DIR}/log.${PORT}.txt
SERVER=${ARMA_DIR}/server
OTHERPARAMS=-cpucount=2
#=======================================================================
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} ${OTHERPARAMS}
    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

log

./arma2oaserver: line 109: /home/arma2arrowhead/server: No such file or directory
./arma2oaserver: line 109: /home/arma2arrowhead/server: No such file or directory
WATCHDOG (15297): [Thu Apr 18 14:32:45 MSK 2013] Server died, waiting to restart...
WATCHDOG (7191): [Thu Apr 18 14:32:45 MSK 2013] Server died, waiting to restart...
WATCHDOG (7003): [Thu Apr 18 14:32:45 MSK 2013] Server died, waiting to restart...
WATCHDOG (13120): [Thu Apr 18 14:32:45 MSK 2013] Server died, waiting to restart...
WATCHDOG (15297): [Thu Apr 18 14:32:50 MSK 2013] Starting server (port 2302)...
WATCHDOG (7191): [Thu Apr 18 14:32:50 MSK 2013] Starting server (port 2302)...
./arma2oaserver: line 109: /home/arma2arrowhead/server: No such file or directory
WATCHDOG (7003): [Thu Apr 18 14:32:50 MSK 2013] Starting server (port 2302)...
./arma2oaserver: line 109: /home/arma2arrowhead/server: No such file or directory
WATCHDOG (13120): [Thu Apr 18 14:32:50 MSK 2013] Starting server (port 2302)...
./arma2oaserver: line 109: /home/arma2arrowhead/server: No such file or directory
./arma2oaserver: line 109: /home/arma2arrowhead/server: No such file or directory
WATCHDOG (15297): [Thu Apr 18 14:32:50 MSK 2013] Server died, waiting to restart...
WATCHDOG (7191): [Thu Apr 18 14:32:50 MSK 2013] Server died, waiting to restart...
WATCHDOG (7003): [Thu Apr 18 14:32:50 MSK 2013] Server died, waiting to restart...
WATCHDOG (13120): [Thu Apr 18 14:32:50 MSK 2013] Server died, waiting to restart...
WATCHDOG (15297): [Thu Apr 18 14:32:55 MSK 2013] Starting server (port 2302)...
WATCHDOG (7191): [Thu Apr 18 14:32:55 MSK 2013] Starting server (port 2302)...
./arma2oaserver: line 109: /home/arma2arrowhead/server: No such file or directory
WATCHDOG (7003): [Thu Apr 18 14:32:55 MSK 2013] Starting server (port 2302)...
./arma2oaserver: line 109: /home/arma2arrowhead/server: No such file or directory
WATCHDOG (13120): [Thu Apr 18 14:32:55 MSK 2013] Starting server (port 2302)...
./arma2oaserver: line 109: /home/arma2arrowhead/server: No such file or directory
./arma2oaserver: line 109: /home/arma2arrowhead/server: No such file or directory
WATCHDOG (15297): [Thu Apr 18 14:32:55 MSK 2013] Server died, waiting to restart...
WATCHDOG (7191): [Thu Apr 18 14:32:55 MSK 2013] Server died, waiting to restart...
WATCHDOG (13120): [Thu Apr 18 14:32:55 MSK 2013] Server died, waiting to restart...
WATCHDOG (7003): [Thu Apr 18 14:32:55 MSK 2013] Server died, waiting to restart...
WATCHDOG (15297): [Thu Apr 18 14:33:00 MSK 2013] Starting server (port 2302)...
./arma2oaserver: line 109: /home/arma2arrowhead/server: No such file or directory
WATCHDOG (7191): [Thu Apr 18 14:33:00 MSK 2013] Starting server (port 2302)...
./arma2oaserver: line 109: /home/arma2arrowhead/server: No such file or directory
WATCHDOG (13120): [Thu Apr 18 14:33:00 MSK 2013] Starting server (port 2302)...
./arma2oaserver: line 109: /home/arma2arrowhead/server: No such file or directory
WATCHDOG (15297): [Thu Apr 18 14:33:00 MSK 2013] Server died, waiting to restart...
WATCHDOG (7003): [Thu Apr 18 14:33:00 MSK 2013] Starting server (port 2302)...
WATCHDOG (7191): [Thu Apr 18 14:33:00 MSK 2013] Server died, waiting to restart...
./arma2oaserver: line 109: /home/arma2arrowhead/server: No such file or directory
WATCHDOG (13120): [Thu Apr 18 14:33:00 MSK 2013] Server died, waiting to restart...
WATCHDOG (7003): [Thu Apr 18 14:33:00 MSK 2013] Server died, waiting to restart...

Cheers

Edited by soulfly83

Share this post


Link to post
Share on other sites

Oh wow, yeah you got a lot of stuff not right there. In a nutshell you need to make a new dir and just put the necessary content dirs from both into that. The on top of that you will have the usual Expansion tolower bug with the installer.

Run the following (as root):

mkdir /home/arma2oa

cd /home/arma2

cp -av addons dta arma2.cfg /home/arma2oa/

cd /home/arma2arrowhead

cp -av Expansion common keys mpmissions server.cfg a2oa-server-1.62.102451.tar.bz2 /home/arma2oa/

cd /home/arma2oa

tar -xvfj a2oa-server-1.62.102451.tar.bz2

mv expansion expansion-tmp

./install

mv expansion-tmp/battleye/beserver.so expansion/battleye/

rm -rf expansion-tmp

Then edit your arma2oaserver script to set paths and config. I would suggest adding the following as OTHERPARAMS (adjust cpu count accordingly):

OTHERPARAMS="-beta=expansion/beta;expansion/beta/expansion -cfg=./arma2.cfg -cpucount=2 -maxMem=2047"

This still leaves the whole player profile config stuff aside (difficulty levels, etc - we will get to that later) but lets just get your server running first ;)

EDIT: Oh and when you run the server, you want to be looking at the output log "log.2302.txt" (equivalent of RPT file on win dedi).

tail -f log.2302.txt will show it to you in realtime (until you stop it with CTRL+C)

Edited by redshirt_ensign

Share this post


Link to post
Share on other sites

Your server install method was alittle different from mine mate, ive followed yoru intructions and have the same message when i start the

server nohup: redirecting stderr to stdout 

and also same in log:

./arma2oaserver: line 109: /home/arma2oa/server: No such file or directory
WATCHDOG (1758): [Fri Apr 19 13:02:57 MSK 2013] Server died, waiting to restart...
WATCHDOG (1758): [Fri Apr 19 13:03:02 MSK 2013] Starting server (port 2302)...
./arma2oaserver: line 109: /home/arma2oa/server: No such file or directory
WATCHDOG (1758): [Fri Apr 19 13:03:02 MSK 2013] Server died, waiting to restart...
WATCHDOG (1758): [Fri Apr 19 13:03:07 MSK 2013] Starting server (port 2302)...
./arma2oaserver: line 109: /home/arma2oa/server: No such file or directory
WATCHDOG (1758): [Fri Apr 19 13:03:07 MSK 2013] Server died, waiting to restart...
WATCHDOG (1758): [Fri Apr 19 13:03:12 MSK 2013] Starting server (port 2302)...
./arma2oaserver: line 109: /home/arma2oa/server: No such file or directory
WATCHDOG (1758): [Fri Apr 19 13:03:12 MSK 2013] Server died, waiting to restart...
WATCHDOG (1758): [Fri Apr 19 13:03:17 MSK 2013] Starting server (port 2302)...
./arma2oaserver: line 109: /home/arma2oa/server: No such file or directory
WATCHDOG (1758): [Fri Apr 19 13:03:17 MSK 2013] Server died, waiting to restart...
WATCHDOG (1758): [Fri Apr 19 13:03:22 MSK 2013] Starting server (port 2302)...
./arma2oaserver: line 109: /home/arma2oa/server: No such file or directory
WATCHDOG (1758): [Fri Apr 19 13:03:22 MSK 2013] Server died, waiting to restart...
WATCHDOG (1758): [Fri Apr 19 13:03:27 MSK 2013] Starting server (port 2302)...
./arma2oaserver: line 109: /home/arma2oa/server: No such file or directory
WATCHDOG (1758): [Fri Apr 19 13:03:27 MSK 2013] Server died, waiting to restart...
WATCHDOG (1758): [Fri Apr 19 13:03:33 MSK 2013] Starting server (port 2302)...
./arma2oaserver: line 109: /home/arma2oa/server: No such file or directory
WATCHDOG (1758): [Fri Apr 19 13:03:33 MSK 2013] Server died, waiting to restart...

some extra info

ArmA 2 directory: /home/arma2oa OK
Server executable: /home/arma2oa/server OK
Port number: 2302
Config file: /home/arma2oa/server.cfg OK
PID file: /home/arma2oa/2302.pid
RUN file: /home/arma2oa/2302.run

root@:/home/arma2oa# ls -al /home/arma2oa
total 20944
drwxr-xr-x 7 root root     4096 Apr 19 13:02 .
drwxr-xr-x 7 root root    20480 Apr 19 12:41 ..
-rw-r--r-- 1 root root        3 Apr 19 13:02 2302.run
-rw-r--r-- 1 root root  5635468 Feb 25 13:14 a2oa-server-1.62.102451.tar.bz2
drwxr-xr-x 2 root root    12288 Apr 16 22:15 addons
-rw------- 1 root root        0 Apr 19 12:46 arma2.cfg
-rwxrwxrwx 1 root root     2915 Apr 19 13:01 arma2oaserver
drwxr-xr-x 2 root root    12288 Apr 16 23:47 common
drwxr-xr-x 7 root root     4096 Apr 19 12:59 expansion
-rwxrwxrwx 1 root root      351 Aug  3  2012 install
drwxr-xr-x 2 root root     4096 Jan 27 13:08 keys
-rw-r--r-- 1 root root    21330 Apr 19 13:09 log.2302.txt
drwxr-xr-x 2 root root     4096 Jan 27 13:10 mpmissions
-rwxrwxrwx 1 root root     4089 Feb  6  2012 readme.txt
-rwxrwxrwx 1 root root 15676336 Feb 25 13:14 server
-rw-r--r-- 1 root root     3744 Apr 16 23:48 server.cfg
-rwxr-xr-x 1 root root    13212 Apr 19 12:59 tolower
-rwxrwxrwx 1 root root     3137 Sep 13  2007 tolower.c

Edited by soulfly83

Share this post


Link to post
Share on other sites
Your server install method was alittle different from mine mate,

Those aren't technically "install" instructions as they are tailored to the fact that you already have some of the folder names changed to lowercase ... but essentially that exactly how I have build my server and it runs great (I am running wasteland but that is still arma2oa). You may have previously been able to run just arma2server without combining the folders but I doubt you could run arm2oaserver (under linux) without doing it.

ive followed yoru intructions and have the same message when i start the

server nohup: redirecting stderr to stdout 

OK, sorry I should have mentioned in the first place, that is not an error. It is just telling you that STDERR is now > STDOUT (which was 2>&1 does in the start script)

Anyway based on the rest of that stuff ... 2 questions:

Where is the dta folder? That should also be in /home/arma2oa/

Are you running it from the right place?

cd /home/arma2oa

./arma2oaserver

Edited by redshirt_ensign

Share this post


Link to post
Share on other sites

am sure its all set correct

---------- Post added at 16:34 ---------- Previous post was at 15:27 ----------

ok mate ive reinstalled etc and still have the same problem

Share this post


Link to post
Share on other sites

EDIT: got the server up and runing thanks to redshirt_ensign :D

Edited by soulfly83

Share this post


Link to post
Share on other sites

Help me please. I have CentOS 7 64bit Dedic (Intel i3 3.3 ГГц, 4 Гб DDR3).

 

What have I done  step by step:

 

  1. install glibc-devel.i686 and libstdc++-devel.i686.
  2. Copy ArmA 2: Operation Arrowhead directory on server (/var/www/user/data/arma2oa/)
  3. Copy and unpack a2oa-server-1.63.112555 files. Use tolower script.
  4. Create server.cfg and basic.cfg and put it in arma2oa.
  5. [root@arma2oa]# ./arma2oaserver start

 

Got the message:

nohup: redirecting stderr to stdout

P.S. install CSF firewall and allow TCP_IN & TCP_OUT 2302 port

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  

×