Brainless Technologies Ltd.

Hello,

I'm trying to finish my build on an Arma 3 template and I'm having a difficult time getting something to work.

By default the Linux Arma 3 binaries don't output an .RPT file (log file / console dump), but rather output errors to STDOUT and STDERR. You have to add something to the startup command line arguments so the server dumps the output to a log file.

Here's an example of a startup command for my server that I ran from the command line which works and logs the output to a date stamped file: Here's what my startup command looks like in UGCC: When I run it from UGCC using those parameters it starts the server but doesn't generate the log file.

Any reason you can think of as to why it's not dumping the console output to the log file when run from UGCC?

Stdout redirection does not work with the way the panel launches the server. You should use the -logfile argument to specify a log file to log to.

Masher wrote:Stdout redirection does not work with the way the panel launches the server. You should use the -logfile argument to specify a log file to log to.

-logfile is not a valid arma3server command line parameter.

As per Bohemia Interactive:

It is not very well documented, but the Linux server outputs the "RPT log" messages on stdout/stderr. (The BIS Linux game servers have done this since back in the OFP days)

Solution: redirect stdout and stderr to a log file of your choosing. For example:

./arma3server -port=$port -pid=ServerRunning -cfg=basicServer.cpp -config=server.cpp "${mods}" >>log.${pid}.txt 2>&1

So: not a bug, but Linux dedis being "different".