Jump to content

viper.cless

Member
  • Content Count

    66
  • Joined

  • Last visited

  • Medals

Posts posted by viper.cless


  1. 4.) I configured my Router to forward Ports (UDP, UDP & TCP) 2302, 2303 and 2305 to my Server.

    Try to forward UDP 2304 also. At least the arma linux server is listening on 2304 UDP and not on 2303 UDP, so why would the windows version.

    9.) Internet Searching in the Gamespy Server list, works. BUT The Ping is either "?" or 2500

    Make sure ICPM echo request are answered and not dropped by your firewall.


  2. Yeah something in the forums adding a space ... I am verifying mod by mod right now.

    OTHERPARAMS=-mod=@cba\;@ace\;@acex\;@acex_usnavy\;@acex_ru\;@fallujah

    (making them lowercase in the params line as well)

    Make sure all filesname are lowercase too. *nix is case sensitive.

    Use tolower in your arma server folder to convert file and foldernames recursively.

    I chown'd the entire dir to root and run the server as root. will that not work?

    It will work, but i suggest you don't run the server using root privileges.


  3. We released a new package with the latest version of jayarma2lib. The lib supports the non-steam 1.55 patch that has been released and supports the 1.55 Steam version that should be released soon.

    There seems to be a signature issue with the 1.55 COMPAT patch.

    I got kicked for wrong signatures of acre related files like acre_main.pbo, acre_api.pbo, ...

    Can anybody confirm this? Or is my acre installation broken?

    In the servers log file I found several messages like

    "Spieler Viper: Falsche Signatur für Datei @acre\addons\acre_api.pbo"

    which means "player Viper: wrong signature for file @acre\addons\acre_api.pbo"


  4. When I edit the arma2server and add "OTHERPARAMS=-mod=@mymod" to the Configuration Parameters the mod never loads.

    Adding the variable to the Configuration Params section isn't sufficient.

    You just defined a script variable named OTHERPARAMS, but the variables value is never passed to the server executable.

    You need to edit the line

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

    in the arma2server script too by appending ${OTHERPARAMS}


  5. roby@Jagger:~/arma2$ ./arma2server start

    bash: ./arma2server: /bin/bash^M: bad interpreter: No such file or directory

    You did create/edit the file on windows, right?

    Unix text files have only the line feed as their newline character whereas Windows text files have carriage return and line feed pairs as their newline characters.

    ^M is the carriage return character and is parsed as part of the interpreter name.

    I suggest you install the package tofrodos

    aptitude install tofrodos

    and run the command

    dos2unix arma2server.sh

    from your arma2 folder in order to fix the file.


  6. But I also ran across a site that said you have to install the essential library's also?

    IIRC you wont need them unless you want to build debian packages.

    apt-get install gcc already installed all required packages.

    The ./arma2server start/stop way of doing things seems to work smoother as far as stooping the server. Although when using ./arma2server start, I now have this:

    nohup: redirecting stderr to stdout.

    Don't worry about this message Its just because the corresponding command call in the script doesn't specify the redicrect explicitly.

    And out of curiosity, if I run the older way of starting just for testing, I get:

    Server: Object x:xx not found (message 121)

    Server: Object x:xx not found (message 121)

    Server: Object x:xx not found (message 121)

    I'm guessing this is because there are objects missing that are needed for testing?

    I don't know what is causing these messages.

    I think under the server= line is where many people seem to be putting their mod folders.

    ArmA_Dir is set to (.) which I think is just the root folder, this is where I have the files extracted.

    Take a look at this post

    http://forums.bistudio.com/showpost.php?p=1565052&postcount=5

    ArmA_Dir is set to (.) which I think is just the root folder, this is where I have the files extracted.

    No, . is not the root folder. . is an alias for the current directory, so is .. for the parent directory.

    Thats why you use ./server command for example. which means 'execute the server binary found in the current directory' or cd .. to go to the parent directory. The root of you filesystem is /

    You can print the current directory with the command pwd

    ('print working directory')

    Maybe its a good idea to replace the ARMA_DIR value with the absolute path of your installation folder.

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

    <-- Can this Pid line be left as is?

    Yes. And I just realized that no pid file is created on my system, strange :)

    As far as hard-linking the script into "/etc/rc.d/init.d/arma2server" file, I might be reading too much into that, I don't understand this just yet, I'll try to explore that more. I'm thinking this chkconfig tool is not something required, but can later make life more easy? for now I was just going to start and stop the server when I needed to play.

    In /etc/rc.d/init.d you find configuration files used by the init process.

    Init is the parent of all processes and spawned when booting up your linux.

    By linking the script into /etc/rc.d/init.d and using chkconfig you would be able to configure the start of your armaserver on system boot.

    AFAIK the default on debian systems is to use update-rc.d instead of chkconfig, thats why chkconfig isn't installed on your system.


  7. Ok, I tried everything again from scratch. tar -xjf server-x.xx.tar.bz2 didn't work, it says files not found. I'm guessing because the file is called tar arma2server-x.xx.tar.bz2.

    So I added the arma2server part to the command, along with the version. It said there were errors extracting, yet when I did an ls -l, all the files were there.

    You are right, you need to pass the proper filename to the tar command.(see man tar)

    Nevertheless do you have the error message?

    ./install: line 7: gcc: command not found

    As mentioned in the readme you have to install the GNU C Compiler (gcc)

    Run the command apt-get install gcc as user root.

    The install script requires a compiler to compile the tolower.c file (written in the c programming language) into an binary file called tolower.

    You or the install script can then use the command ./tolower to convert the file and folder names to lower case.

    Edit, I also noticed that when I stop the sever with Ctrl + C, I it stops it, but it says Critical: Destroying running thread. This happens under both a user and the root account.

    Ctrl + C does signal the process to abort asap.

    Use the command ./server only to test your installation.

    The proper way to start/stop the server is by running the arma2server script.

    ./arma2server start or ./arma2server stop

    Don't forget to edit the configuration parameters at the beginning of the arma2server script file.

    The script will also restart the arma2 server automatically in case of a crash.

    IMHO it's always a good idea not to run a service as user root unless it must have root privileges.

    FYI http://community.bistudio.com/wiki/ArmA:_Dedicated_Server#Linux

    The game ran smooth, but I'm getting errors on the server screen when I create vehicles. The errors are:

    Server object 3.4 Not found Message 121

    I don't know what this message is about.


  8. Have exactly the same problem. Can't find out servers in the in-game browser.

    Same problem here.

    It seems to be some gamespy masterserver problem as I found those message in the server log :confused:

     109/11/23, 13:01:53 Warning Message: No challenge value was received from the master server.
    109/11/23, 13:01:53 GameSpy QR2 error: 5, No challenge value was received from the master server.
    


  9. Daddybear;1513744']If I start the server with ./arma2server -mod=@bwmod the Server can't load the addons because they are missing.

    But if I start the Server with ./server -mod=@bwmod the Server can load the addons for the missionfile.

    Find the line starting with

     ${SERVER} >>${LOGFILE} 2>&1 -server -config=${CONFIG}

    in the arms2server script and add your mod option -mod=@bwmod at the end.

    Valid parameters for the arma2server script are

    start|stop|restart|status|check

×