Find your Arma Reforger server logs and how to read them

Every time the Arma Reforger server starts, it writes a new folder named logs_ plus the date and time inside the logs folder of its profile. On our servers each folder holds console.log, error.log and script.log. The game keeps only the newest ten folders.

In the ArthOS panel

There are three ways to read them, from quickest to most complete.

1. Console. Open the Console tab to watch the current start as it is written. This is the live console.log.
2. Crashes. Open the Crashes tab. Each start of the server is listed, newest first, with how it ended: running now, ran and stopped, failed to start, crashed, froze while stopping, or ended early. Pick a start to see its game version, how long it ran and how many errors it had. Errors are grouped, so a message written a hundred times is one row with a count, sorted by who wrote it: mods, the engine, or the game itself.
3. Files. Open the Files tab, then the profile folder, then logs. Open a logs_ folder and choose a file to read it in the editor. Use this when you need warnings, which the Crashes page leaves out of its tail, or the whole file.

12

123

By hand

The logs sit under the folder you pass to the -profile startup parameter. With -profile ./profile, look in ./profile/logs/. Bohemia’s server hosting page says the console logs are found in the profile folder.

Startup parameters from Bohemia that change what you get:

• -keepNumOfLogs 20 keeps 20 log folders instead of the default 10.
• -logAppend stops the logs being emptied at start, so history is kept.
• -logLevel warning records warnings and above. The levels are normal, warning, error and fatal, and each includes the ones after it.
• -logTime datetime puts the date in every line instead of only the time.
• -logsDir "name" puts the logs in <profile>/logs/name.

Avoid -logFS on a live server. Bohemia describes it as very demanding and meant for debugging only.

What to look for

• A line with (E) is an error, (W) a warning. Search for (E) first.
• Unable to initialize the game means the server never got as far as letting players in. Look at the lines just before it.
• Application crashed! means the game crashed. A Crash GUID line below it is the ID the game sent to Bohemia.
• Application hangs (force crash) means the server froze and was stopped by the freeze check. It is not the same as a crash while players were on.
• Thousands of lines about a thermal profile are not your fault. See the thermal profile log spam guide.

If it does not work

• No logs folder: the server has never started, or you passed a different -profile or -logsDir. Start it once, then look again.
• An old log is gone: the game keeps only the newest ten starts, and they cannot be got back. On your own host, raise -keepNumOfLogs. On a Loafhosts server there is no setting for it, so download a log from Files as soon as you need to keep it.
• The log is very large: a large log usually means one message repeating. Go to the end of the file and look for the line that repeats.
• The log ends before the server finished starting: the Crashes tab lists that start as ended early. Read the last lines for the reason.
• -keepNumOfLogs or -logLevel is not in the panel: these are startup parameters for a server you run yourself. A Loafhosts server starts with a fixed set, and the Startup tab shows the ones you can change.

For what to do with a crash, read how to read Arma Reforger server crashes. More about the game on our Arma Reforger page.

Sources: Bohemia wiki: Startup Parameters, Bohemia wiki: Server Hosting, Bohemia wiki: Crash Report, reforger.armaplatform.com: Update september 3 2026

Arma Reforger serversAll Arma Reforger guides