ArmA Reforger Instance stuck in Starting state, but has actually started.

[Azza276]

Operating System

Windows Server 2016

AMP Version and Build Date

2.6.0.6

AMP Release Stream

Mainline

I confirm that

• I have searched for an existing bug report for this issue.
• I am using the latest available version of AMP.
• my operating system is up-to-date.

Intended Action

Start and control an Arma Reforger AMP instance on Windows Server 2016

Expected Behaviour

Arma Reforger instance starts, and transitions to a Running state as shown in AMP.

Actual Behaviour

Arma Reforger Instance is started.
The Arma Reforger instance shows "Starting State"
The Arma Reforger game starts and shows RCON Admin Connection
The Arma Reforger instance continues to show "Starting" state.
Unable to Abort or Kill game server through Reforger Instance control. Requires stopping and restarting the entire Reforger instance.
After a day or two, the instance fails -Reporting that 2 attempts to start were made, but game didn't start.

Reproduction

Using Windows Server 2016 - Install latest AMP (with Web Admin)
Install an Arma Reforger Instance.
Start the Arma Reforger Instance.
Note that Arma Reforger instance console shows that game log, and that RCON Admin #0 connects.
Arma Reforger Instance remains in "Starting" State.

[Azza276]

A lot of log reports and discovery has already been conducted as seen in this Discord Post.
https://discord.com/channels/266012086423912458/1319511484224770128
Note: this seems to not affect Windows Server 2022. Unsure about Windows Server 2019.
This appears to be an issue with the RCON client from AMP, as logs show it disconnects shortly after it connects.
Greelan suggested it may be related to the RCON REGEX filters, which is similar to Github issue 1212
#1212

[Greelan]

It appears that the console output in your case is being buffered, preventing AMP from reading the line that it tells it the server is started (the one that includes "Game successfully created."). This is despite the template including a setting which is meant to address this buffering.

I could change it to detect start on RCON connecting but that won't address your console buffering issue.

[Azza276]

Thanks Greelan,
Is this something I can trial locally (modifying a config)?
Does the console buffering explain the "Dropped client: #0" where the AMP RCON client is dropped?
Cheers

[Greelan]

If RCON is disconnecting as well, that could be an unrelated issue.

If you want to test, stop the instance, edit GenericModule.kvp for the instance, and change the following setting to this value:

App.ApplicationReadyMode=RCONConnected

[Azza276]

Yep, That works, the instance now goes to running state, and I can control (stop) the server within the instance.

[Azza276]

Though, as expected if the RCON client is dropped, there are no Metrics and Status being shown. This is a minor inconvinience, but much better than staying in Starting state.

[Greelan]

RCON doesn't have anything to do with metrics

[Azza276]

Ok, Copy.
Well metrics aren't showing then. Both CPU and RAM are sitting at 0 on a running server.