A2OA Linux Server beta 1.59.79548

[Vixente 10]

EDIT: Sorry to bother you again with this... but i could not find any reference to any 'MPMissions' (uppercase) folder anywhere. Neither in server.cfg nor in server profile.

This is what my server dumps just when i connect to it:

21:06:23 Player [VK] Vicente connecting.

21:06:25 Player [VK] Vicente connected (id=1848774).

File mcc\Dialogs\mcc_PopupMenu.hpp, line 365: '/PUM3_PopupMenuDialog/UnitShipSpawn.onButtonClick': Missing ';' prior '}'

File mcc\Dialogs\mcc_extrasmenu.hpp, line 305: '/ExtrasDialog/LHD_pos1.action': Missing ';' prior '}'

File mcc\Dialogs\mcc_PopupMenu.hpp, line 365: '/PUM3_PopupMenuDialog/UnitShipSpawn.onButtonClick': Missing ';' prior '}'

File mcc\Dialogs\mcc_extrasmenu.hpp, line 305: '/ExtrasDialog/LHD_pos1.action': Missing ';' prior '}'

Cannot open file 'MPMissions\{BDR}Domination{BDR}2,8-Rw.Takistan.pbo'

Critical: Destroying running thread!

Critical: Destroying running thread!

./arranca: línea 4: 4818 Violación de segmento ./server -cpuCount=2 -exthreads=1 -config=server.cfg -nomap -port=2302

('arranca' is my little script that launches the server binary)

This is the content of my player.arma2oaprofile inside 'player' folder:

singleVoice=0;

soundEnableEAX=1;

soundEnableHW=0;

volumeCD=5;

volumeFX=5;

volumeSpeech=5;

And this is the content of my server.cfg:

//

// server.cfg

//

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

// GLOBAL SETTINGS

port=2317;

hostname="[ES]Vikingos-[VK]Vicente LINUX-DEBIAN-VMWARE-TEST SERVER"; // The name of the server that shall be displayed in the public server list

password=""; // Password for joining, eg connecting to the server

passwordAdmin="*censored*"; // Password to become server admin. When you're in Arma MP and connected to the server, type '#login PASSWORD'

reportingIP="arma2pc.master.gamespy.com"; // This is the default setting. If you change this, your server might not turn up in the public list. Leave empty for private servers

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[]={

"", "", "",

"Bienvenido al servidor ARMA2 de www.clanvikingos.es ",

"La utilizacion de nuestro Teamspeak es OBLIGATORIA para jugar en este servidor",

"Prohibido utilizar cualquier vehiculo si no estas en nuestro Team Speak o seras expulsado",

"This is a spanish server so you must know the Spanish language to join our TS",

"Proveedor de servidor de juegos www.NewLightSystems.com"

};

motdInterval=30; // Time interval (in seconds) between each message

// JOINING RULES

checkfiles[]={ // Checks if these files are equal to the servers files. If one or more is not, player will be kicked from server

"HWTL\dta\data3d.pbo",

"dta\data3d.pbo"

};

maxPlayers=10; // 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=0; // Verifies the players files by checking them with the .bisign signatures. Works properly from 1.08 on

equalModRequired=0; // If set to 1, player has to use exactly the same -mod= startup parameter as the server.

// 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=7; // Quality from 1 to 10

persistent=1; // If 1, missions still run on even after the last player disconnected.

// SCRIPTING ISSUES

onUserConnected=""; // self-explaining

onUserDisconnected="";

doubleIdDetected="";

regularCheck="";

// some ArmA specific stuff - 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

BattlEye=1; //Server to use BattlEye system

// MISSIONS CYCLE (see below)

class Missions {

};

Permissions are set chmod 755 on all files and folders.

Any clues? :j:

Edited May 10, 2011 by Vixente

[daikan 1]

This is a little hard to debug without seeing the actual filesystem contents...

Maybe you could try doing a

grep -R MPMissions .

or

grep -R "{BDR}Domination{BDR}2,8-Rw.Takistan" .

from within your server install dir and see if it turns up anything interesting.

Edited May 10, 2011 by daikan

[Vixente 10]

Well, that was something. It is clear that some files refer to mpmissions folder as if it were uppercased.

Take a look:

arma2@debsrv:~$ find . | xargs grep -s "MPMissions"

Coincidencia en el fichero binario ./@acex_usnavy/addons/acex_usnavy_missions.pbo

./@acex_usnavy/changelog.txt:* 3rd party MPMissions, credits to the authors. [sickboy]

Coincidencia en el fichero binario ./expansion/beta/expansion/dta/bin.pbo

Coincidencia en el fichero binario ./expansion/beta/expansion/addons/ui.pbo

Coincidencia en el fichero binario ./expansion/beta/expansion/addons/hotfix_oa_154.pbo

Coincidencia en el fichero binario ./expansion/beta/expansion/addons/mp_armory.pbo

Coincidencia en el fichero binario ./expansion/beta/arma2oa.exe

Coincidencia en el fichero binario ./expansion/beta/arma2oaserver.exe

Coincidencia en el fichero binario ./expansion/dta/bin.pbo

Coincidencia en el fichero binario ./expansion/addons/ui.pbo

Coincidencia en el fichero binario ./expansion/addons/missions_e.pbo

Coincidencia en el fichero binario ./expansion/addons/mp_armory.pbo

Coincidencia en el fichero binario ./expansion/addons/warfare2.pbo

Coincidencia en el fichero binario ./server

Coincidencia en el fichero binario ./mpmissions/co_mcc_sandbox_v15.lingor.pbo

Coincidencia en el fichero binario ./mpmissions/co_mcc_sandbox_v15.takistan.pbo

./mpmissions/readme.txt:MPMissions

Coincidencia en el fichero binario ./mpmissions/co_mcc_sandbox_v15.zargabad.pbo

Coincidencia en el fichero binario ./@acex/addons/acex_missions.pbo

Coincidencia en el fichero binario ./@acex/addons/acex_missions_bc_oa.pbo

./@acex/changelog.txt:* 3rd party MPMissions, credits to the authors. [sickboy]

Coincidencia en el fichero binario ./common/missions_baf.pbo

Coincidencia en el fichero binario ./@ace/addons/ace_missions.pbo

./@ace/changelog.txt:* Moved Combined Ops MPMissions to CO subfolder. [sickboy]

./@ace/changelog.txt:* ACE A2 (Combined Ops) MPMissions again. [sickboy]

Coincidencia en el fichero binario ./dta/bin.pbo

Coincidencia en el fichero binario ./addons/missions.pbo

Coincidencia en el fichero binario ./addons/warfare2.pbo

./uninstall.log:D:e:\ArmA 2\MPMissions

./uninstall.log:F:e:\ArmA 2\MPMissions\readme.txt

arma2@debsrv:~$

"Coincidencia" means "Match".

Ignoring the .txt .exe and other files it is obvious that the .pbo files have references to uppercased mpmissions. Even the server binary! :butbut: Is there any tricky linux command to replace those strings automatically?

[daikan 1]

Hmm doesn't look too bad to me.

Curiously, what are the contents of your mpmissions folder? Did you make sure all the mission file names are converted to lower case after you added them?

[Vixente 10]

Did you make sure all the mission file names are converted to lower case after you added them?

That too? I thought it was not necessary, that you just had to rename the folders at the main game folder... /facepalm

[daikan 1]

That too? I thought it was not necessary, that you just had to rename the folders at the main game folder... /facepalm

Bingo :)

[Vixente 10]

It seems to be working after the "tolower" process.

Thank you so much daikan. ;)

[Plam 10]

Hi,

Since 1.59 (1.57 was fine) I've got this error :

$ ./server --config=/srv/arma/arma2oa.cfg
Item str_disp_server_control listed twice
Data file too short 'pmc\addons\characters_pmc.pbo'. Expected -1767439245 B, got 155561338 B
Critical:Destroying running thread!
[79104.185554] server[6077]: segfault at 0 ip (null) sp 00000000f77371dc error 14 in server[8048000+1025000]
Segmentation Fault

[.kju 3240]

No PMC and BAF folder on the DS..

[Plam 10]

Ok, so it's "better" but after few seconds :

23:37:47 Hôte dédié créé. (translation : Dedicated host created)
Error context �c���c��M6�M6
File , line 0: '.': '�' encountered instead of '='
Critical:Destroying running thread!
[130173.540041] server[15454]: segfault at c ip 0000000008f7fa2d sp 00000000f73f6370 error 4 in server[8048000+1025000]

[marceldev89 89]

If the server is 64bit, did you install the 32bit libs on the server? (Debian: ia32-libs)

Are all files converted to lowercase?

[=wfl= sgt bilko 10]

I think this:

./server --config=/srv/arma/arma2oa.cfg

Should be this:

./server -server -config=/srv/arma/server.cfg

The file arma2oa.cfg is the one with e.g. "MinBandwidth" settings.

The file you point out with -config is the one with passwords and stuff (named server.cfg in code above).

Edited May 17, 2011 by =WFL= Sgt Bilko

[marceldev89 89]

I think this:

./server --config=/srv/arma/arma2oa.cfg

Should be this:

The file arma2oa.cfg is the one with e.g. "MinBandwidth" settings.

The file you point out with -config is the one with passwords and stuff (named server.cfg in code above).

True, and you don't even have to specify "arma2oa.cfg" anyway since it's loaded automatically (if you leave the filename as it is).

[Plam 10]

Thanks for your help guys !

Now, it works with :

$ ./server -server -config=server.cfg 
Item str_disp_server_control listed twice
8:26:23 Hôte dédié créé.
8:26:24 Identité d'hôte créée.
ArmA 2 OA Console version 1.59 : port 2302 - Sockets

Sorry for my mistakes ;)

[byteslam 10]

...there was a promise to solve a problem...

I just want to come back to the main topic of this thread....the Linux Server and its faulty implementation and that we are still waiting since weeks for a solution....

:mad:

[icebreakr 3105]

^^ +1 ... we can't finish a mission longer than 1 hour, 1 CTD per hour.

[Spayker 10]

Calm down guys... BIS just care on your linux servers. It's better to do ka-28 or mi-52 for nextgeneration laged games.

If you want to solve your problem then you have one solution - win ded server...

[icebreakr 3105]

Will you talk to our server provider and tell them to switch from UNIX to windows ? ;) screw it, I guess we'll move the server to someones home...

[Spayker 10]

Have same problems with provider like you...:D

[Dwarden 1124]

unless windows crashes are fixed the new build for linux has no sense ...

so be happy it crash after 1 hour ... the last betas are crashing way faster and more often :mad:

when it's worked out and fixed you will get nix server too

[byteslam 10]

why not providing an update which makes a binary roll back to the previous stable version until the new release is well tested and really stable??

[icebreakr 3105]

And we suffered another squadnight with 4 or 5 CTDs, we weren't able to finish more than 1 mission in whole evening. We even switched to Vanilla (no mods, not even sound) with no better result.

[byteslam 10]

....two month later and no solution in sight, I can not believe that BI has not enougth man power to solve such an minor problem within a time frame of 2 month.

Anyway, a clear statement would be polite. If now all resources are blocked for ARMA3, we can decide to shutdown our server until ARMA3 has been released, hopefully with a better Linux suport.

[nyles 11]

A new linux server version would be very much appreciated indeed. Those problems are really annoying and have result in a huge noticable drop of players on our server.

[.kju 3240]

Dwarden gave you a clear statement, no?

First 1.60 stable, only then they can build a new, hopefully stable, linux build.

On top tomorrow starts e3 with CC, ToH and e3. Guess what had their focus for the last weeks.

That said there were zero crash dumps and such supplied in the CIT.

And you wonder why they are unable to address it?