Linux server issues

[brightness]

Alright install and everything works fine till I run ./server and in turn it hands me over a error,


Item str_disp_server_control listed twice
11:24:57 Dedicated host created.
Error context ¥Ü·(¥Ü·h·Zh·Z
File , line 0: '.': '(' encountered instead of '='
Critical:Destroying running thread!


Ideas to fix?

[.kju [PvPscene]]

remove all custom missions and try again. it seems there is a corrupted/buggy among em

[Killswitch]

Alright install and everything works fine till I run ./server and in turn it hands me over a error,


Item str_disp_server_control listed twice
11:24:57 Dedicated host created.
Error context ¥Ü·(¥Ü·h·Zh·Z
File , line 0: '.': '(' encountered instead of '='
Critical:Destroying running thread!


Ideas to fix?
Yes. Don't start the server by using "./server". Instead, edit the arma2oaserver script as instructed in step 7 of the readme.txt and then launch the server via

./arma2oaserver start

[Overlord]

Remember to correct your paths in the default script

[brightness]

Fixed, Just had to launch in ./arma2oaserver start now the issues come .. If I launch the server in arma2oaserver then my -mod thingy won't work but if I launch it in ./server it launches the mod I point in -mod.

I am using the -mod option like this,


${SERVER} >>${LOGFILE} 2>&1 -server -config=${CONFIG} -port=${PORT} -pid=${PIDFILE} -mod=${MOD} -cfg=arma2oa.cfg

Ideas??

[.kju [PvPscene]]

how does your MOD parameter look like?

[brightness]

MOD=@<hidden>\;@<hidden>\;@<hidden>\;@<hidden>\;@<hidden>\;@<hidden>\;@<hidden>\;@<hidden>\;@<hidden>\;

[.kju [PvPscene]]

remove the last \;

the semicolon is a separator here

[brightness]

Done it still not starting mods up

[VisceralSyn]

Script should look like this:



#!/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=.
CONFIG=arma.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


You should be configuring this script there, add the following:



#!/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=.
CONFIG=arma.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
OTHERPARAMS=-mod=@<hidden>\;@<hidden>\;@<hidden>\;@<hidden>\;@<hidden>\;@<hidden> _sm\;@<hidden>\;@<hidden>\;@<hidden>



...Syn...

[brightness]

Thing is that it won't recognize that and won't run it :S

[VisceralSyn]

post your arma2server script.

...Syn...

[brightness]

#!/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/alwandy 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
OTHERPARAMS=-cpucount=1
OTHERPARAMS=-mod="@<hidden>;@<hidden>;@<hidden>;@<hidden>;@<hidden>;@<hidden>;@<hidden>;@<hidden>"
#=======================================================================
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} -cfg=arma2oa.cfg
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


Thats what I am using now(Used your example) and that didn't work either.

[VisceralSyn]

OTHERPARAMS=-mod="@<hidden>;@<hidden>;@<hidden>;@<hidden>;@<hidden>;@<hidden> a;@<hidden>;@<hidden>"


Doesn't not look like:



OTHERPARAMS=-mod=@<hidden>\;@<hidden>\;@<hidden>\;@<hidden>\;@<hidden>\;@<hidden>\;@<hidden>\;@<hidden>\;@<hidden>


also, none of those folders filenames can have spaces. Linux isn't windows, if you do do not follow syntax. Nothing works.

[brightness]

Shouldn't have spaces??

[VisceralSyn]

correct, SHOULD NOT have spaces.

...Syn...

[brightness]

I meant that it doesn't have any spaces in nano ^^ Maybe because I copied the thing from windows.

Anyways, I re did it and copied your way but still no succees launching server in ./arma2oaserver with mods .. It launches without but with ./server -mod=@<hidden>\;@<hidden>\;@<hidden>\;@<hidden>\;@<hidden>\;@<hidden> _sm\;@<hidden>\;@<hidden>\;@<hidden>

It launches the mods.

[VisceralSyn]

if ./server works as you intend, then run with it. The script however provides some redundancy.

[brightness]

Thats the thing, Why can't I get it running with ./arma2oaserver .. Any other ways??

[VisceralSyn]

I'm not at home to check my script, the wiki has the correct syntax for it. I can't access the wiki from work to link you to it as well.

...Syn...

[Riffler]

OTHERPARAMS=-mod="@<hidden>;@<hidden>;@<hidden>;@<hidden>;@<hidden>;@<hidden>cb a;@<hidden>;@<hidden>"

[VisceralSyn]

The quotes do not belong there either, i do believe the space in that particular one was due to formatting.

...Syn...

[brightness]

I never uploaded the arma2oaserver from windows, I totally edited all my files through nano

[Killswitch]

VisceralSyns variant does work:

OTHERPARAMS=-mod=@<hidden>\;@<hidden>\;@<hidden>\;@<hidden>\;@<hidden>\;@<hidden>\;@<hidden>
Here's a variant that also works (note the single qoute characters which alleviate the need to escape the semicolons)

OTHERPARAMS='-mod=@<hidden>;@<hidden>;@<hidden>;@<hidden>;@<hidden>;@<hidden>;@<hidden>'
...and a variant with more than one extra launch parameter:

OTHERPARAMS='-cpucount=2 -mod=@<hidden>;@<hidden>;@<hidden>;@<hidden>;@<hidden>;@<hidden>;@<hidden>'

I have verified that all three variants work.

NOTE: You don't need to load @<hidden> on a dedicated server - see the instructions for ACRE.

If you still can't make it work, there's a chance that the arma2oaserver script has been "infected" with DOS-style line endings (CRLF), which usually results in very strange behaviours.


dos2unix arma2oaserver

(In some distributions, that tool is called "fromdos")

[brightness]

Still no freaking success, Guys I KNOW what I am doing. arma2oaserver just don't wanna start the freaking mods somehow and just starts up without EM

[sImArmA]

OTHERPARAMS=-cpucount=2
OTHERPARAMS=-mod=@<hidden>\;@<hidden>\;@<hidden>\;@<hidden>\;@<hidden>\;@<hidden> _sm\;@<hidden>\;@<hidden>\;@<hidden>

i think it's quit simple... OTHERPARAMS declared twice ...:butbut:
Try
OTHERPARAMS=-cpucount=2
OTHERPARAMSACE=-mod=@<hidden>\;@<hidden>\;@<hidden>\;@<hidden>\;@<hidden>\;@<hidden> _sm\;@<hidden>\;@<hidden>\;@<hidden>

See ya

[VisceralSyn]

there is no limit on how many 'OTHERPARAMS' declarations.



OTHERPARAMSACE=-mod=@<hidden>\;@<hidden>\;@<hidden>\;@<hidden>\;@<hidden>\;@<hidden> _sm\;@<hidden>\;@<hidden>\;@<hidden>


Will not work.

...Syn...

[Overlord]

try
MOD="@<hidden>;@<hidden>;@<hidden>;@<hidden>;@<hidden> _sm;@<hidden>;@<hidden>;@<hidden>"
this is instead of
OTHERPARAMSACE=-mod=@<hidden>\;@<hidden>\;@<hidden>\;@<hidden>\;@<hidden>\;@<hidden> _sm\;@<hidden>\;@<hidden>\;@<hidden>

and add (in red)
${SERVER} >>${LOGFILE} 2>&1 -server -config=${CONFIG} -port=${PORT} -pid=${PIDFILE} -mod=${MOD} ${OTHERPARAMS} -cfg=arma2oa.cfg

[sImArmA]

@<hidden> VisceralSyn:
----------------------------------------------------------
OTHERPARAMSACE=-mod=@<hidden>\;@<hidden>\;@<hidden>\;@<hidden>\;@<hidden>\;@<hidden> _sm\;@<hidden>\;@<hidden>\;@<hidden>

Will not work......
-----------------------------------------------------------
... is quiet nonsense! :yay:

using ${OTHERPARAMACE} or something ever else in script works fine
${SERVER} >>${LOGFILE} 2>&1 -server -config=${CONFIG} -cfg=${CFG} ${OTHERPARAMS} ${OTHERPARAMSACE}
--------------------------------------------------------------------------
params1=x
params2=y
params3=... dta ->>
${SERVER} >>${LOGFILE} 2>&1 -server -config=${CONFIG} -cfg=${CFG} ${params1} ${params2} ${params3}
....
NOT!!
OTHERPARAMS=XXXX
OTHERPARAMS=YYYY

[VisceralSyn]

Your 'quiet nonsese' is quite not making any sense.

But if you say it works for you, I'm just not goin ta smoke from the pot, you are smoking from.

...Syn...

---------- Post added at 11:15 AM ---------- Previous post was at 11:12 AM ----------

I also do not edit the 'Watchdog' Section of the script. I edit the script where it says to perform editing.



#================================================= ======================
#======== CONFIGURATION PARAMETERS ========
#======== MUST BE EDITED MANUALLY TO FIT YOUR SYSTEM PARAMETERS ========
#================================================= ======================
ARMA_DIR=/home/alwandy 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
OTHERPARAMS=-cpucount=1
OTHERPARAMS='-mod=@<hidden>;@<hidden>;@<hidden>;@<hidden>;@<hidden>;@<hidden>;@<hidden>;@<hidden>'
#=======================================================================


There is not a limit to how many extra 'OTHERPARMS' declarations. You could do one for each mod if you want, the above is just cleaner.

[Overlord]

I also do not edit the 'Watchdog' Section of the script. I edit the script where it says to perform editing.
Then your mods won't be loaded if server crash....

[VisceralSyn]

Erm, incorrect...

It re-reads the script restarting the server. What makes you think it would not re-read the script, after a crash? Hell, that's half the reason for the script!

...Syn...

[Overlord]

Afik Watchdog do what "he's" told to do in "Watchdog section" of script, just start server again (if it dies).
If it's no extra mods listed, I doubt he'll load'em either. Not tested this myself, have hard time crashing server (no bragging, it's just how it is).
Anyway, I added it. From OFP times, mods just had to be listed there if you wanted server online again, we still talk about Lin servers I guess?

[VisceralSyn]

Since the documentation for configuring the Linux deddy server is vague. There is a lot of hit and miss. I've never had the 'Watchdog' not re-read the entire script, and yes, that means it reloads mods with the server.

Not a 'AFIK'

...Syn...

[Rexxenexx]

Something like:
OTHERPARAMS='-cpucount=2 -exThreads=1 -mod=@<hidden>;@<hidden>;@<hidden>;@<hidden>;@<hidden>'

is good enough. Single quotes and put in whats normal. Also check that "server" is not already running by opening System Monitor and looking under Processes.

EDIT: brightness, download my GUI from my sig or pm me your email an I'll email it to you if you don't want to login etc.

[Overlord]

Don't wanna claim astronomical knowledge to Linux or AA2 DS, but remove MOD parameters, and tell me where WD load'em from?

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} -mod=${MOD} ${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

Script is clear enough (in my blue eyes), it reads your config file and {OTHERPARAMS}, but no mods (if not added).

If you add OTHERPARAMS1 and OTHERPARAMS2, you still need to add them here, and the WD section is editet again....

@<hidden>
I don't run ACE myself, but why is it necessary to load it twice (even if it would work)?

MOD=@<hidden>\;@<hidden>\;@<hidden>\;@<hidden>\;@<hidden>\;@<hidden> _sm\;@<hidden>\;@<hidden>\;@<hidden>\;

[VisceralSyn]

The default watchdog script:



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} -cfg=arma2oa.cfg
if [ -f ${RUNFILE} ];


a correct OTHERPARAMS line is read by the script, at ${OTHERPARAMS}, if that section of the script is configured correctly. Then the script reads the OTHERPARAMS every time. No need to junk up the script, adding stuff all willy-nilly.

The mod line that was being used, was an example. After several copy and pastes, formatting has added spaces, and doubles.. etc...
...Syn...

[Overlord]

I agree with your line of thought VisceralSyn, it's a good way to configure server. On the other hand, it still requite, as you point out, a correct OTHERPARAMS line.

The mod-entry ain't that complicated, along with other stuff I add to the script, it works just perfectly well. As I said I'm no Wizard in either Linux or AA2, but it's not that complicated to edit the scrip.

Of course you must know what you are doing (as you sounds like), so I'm tempted to vote for your solution for "newbies", as they can leave the broad part of startscript unchanged.