ARMA2 OA Linux server problem

[Spike1986 10]

Hi

i confed all and got this problem:

WATCHDOG (14695): [Thu Nov 18 16:48:42 CET 2010] Server died, waiting to restart...

WATCHDOG (14695): [Thu Nov 18 16:48:47 CET 2010] Starting server (port 80)...

./arma2oaserver: line 109: .: -s: invalid option

help please

Spike

WATCHDOG (7237): [Wed Nov 17 20:54:28 CET 2010] Server died, waiting to restart...

WATCHDOG (7237): [Wed Nov 17 20:54:33 CET 2010] Starting server (port 2302)...

Edited November 18, 2010 by Spike1986

[larsiano 12]

welcome to the forum!!

has it ever worked?

what linux vers.?

what arma2 patch?

etc.

Need input:

[Spike1986 10]

no, it never works before

Distributor ID: SUSE LINUX

Description: openSUSE 11.1 (i586)

Release: 11.1

(Linux vserver2311 2.6.30.2-domU-v4 #4 SMP Fri Jul 31 15:57:07 CEST 2009 i686 i686 i386 GNU/Linux)

newest arma2 + oa patches (uploaded yesterday)

no errors, just the 1 in the logfile

dont know

---------- Post added at 05:30 PM ---------- Previous post was at 05:21 PM ----------

line 109:

server (port ${PORT})..."

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

Edited November 18, 2010 by Spike1986

[Spike1986 10]

no solutions`? :(:(:(

[larsiano 12]

I wish i knew more about Linux i just wanted to help you get the troubleshooting going! What does google say? Maybe you can give a step by step installation guide for a noob like me (if you feel like it).

[Spike1986 10]

google dont knows this problem, i already googled it (im not writing here without googled the prob before).

it looks like im alone with this prob.

[killswitch 19]

Spike1986, could you post the part of the arma2oaserver script where you set the configuration parameters. Sometimes, an extra character in a bad place can cause problems further down in shell scripts. I'm referring to this section of the script:

#=======================================================================
#========               CONFIGURATION PARAMETERS                ========
#======== MUST BE EDITED MANUALLY TO FIT YOUR SYSTEM PARAMETERS ========
#=======================================================================
ARMA_DIR=
CONFIG=
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
#=======================================================================

[Spike1986 10]

hm... thanks for the answer

#!/bin/bash

#

# armaserver: ArmA 2 Linux Dedicated Server Control Script

# © 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=/srv/www/htdocs/web0/html/ftp/server/gameserver/arma2

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

[killswitch 19]

That looks OK(*). I wonder if there are invisible, "strange" characters in that file put there when you edited the file. How did you edit the file? Did you use a text editor on the server itself? Did you edit the file on your Windows computer and then upload it? What editor did you use? (If you used the Windows Notepad.exe editor, perhaps there are some hidden DOS-type line endings in the arma2oaserver file that are causing trouble)

(*) The line CONFIG=arma2.cfg is suspicios. The file named "arma2.cfg" is automatically generated when you start the old ArmA II 1.0x Linux server and usually contains this:

language="English";
adapter=-1;
3D_Performance=1;
Resolution_Bpp=32;

The file intended for the CONFIG parameter is the one usually called "server.cfg" and would contain lines like this:

// GLOBAL SETTINGS
hostname="My ArmA II server"
password = ""     // Password for joining eg connecting to the server
passwordAdmin = "secret" // Password to become server admin

...
... more stuff here
...

Naturally, if your "arma2.cfg" contains game server config lines like the second example above, everything is alright. (I would rename it "server.cfg" or anything except "arma2.cfg" since that name is used for a file that may get automatically created if you start the old A2 Linux dedi server)

I can't see anything wrong with your arma2oaserver file, but it's worth a try to unpack a fresh copy from the a2oa-server-1.55.75619.tar.bz2 archive and then edit it on the server using Vi, emacs, gedit or whichever favourite editor you have. There may be strange characters hiding in the file that got there during editing or when (if) you uploaded it from your Windows machine.

Good luck!

[HitmanFF 6]

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

Might be a copy-paste error from your file to the forum post, but there seems to be a } missing there (ending ${OTHERPARAMS ).

Following Killswitches suggestion to use a fresh arma2oaserver would be best probably.

[Spike1986 10]

i checked all, theres no way... :(

its allright, i changed the name of the cfg and checked all files, installed new.. no way :eek:

[Spike1986 10]

ok, i removed the server...