System Information
| Field | Value |
|---|---|
| Operating System | Linux - Ubuntu 24.04 on x86_64 |
| Product | AMP ‘Callisto’ v2.5.1.4 (Mainline) |
| Virtualization | None |
| Application | DayZ (Stable) |
| Module | GenericModule |
| Running in Container | No |
| Current State | Stopped |
Problem Description
Issue
I upgraded AMP and the game instance this morning. After the update, the DayZ Instance sits there with a “Starting DayZ (Stable)” notification that will not clear.
It appears this is because the RCON is no longer starting on server startup as the port never goes green on the status page.
Everything was working prior to the update to 2.5.1.4 - 20240731.1.
I tried deleting the instance and recreating a fresh one - the fresh image exhibits the same issue - a blank vanilla unmodded DayZ server starts up (it’s connectable with the game) however AMP cannot see it’s started as RCON is not working.
After tinkering a bit - I’ve discovered that AMP is wiping the “beserver_x64.cfg” file and not regenerating it’s contents on server startup as per what’s listed in metaconfig.json.
I edited beserver_x64.cfg and saved correct contents directly after clicking start on the server (so the file was wiped), but before the game server started up and this seems to have started up the RCON properly.
However, if I restart the game server AMP wipes the content of the file again and RCON doesn’t start - so it appears to be a problem with AMP not correctly generating the “beserver_x64.cfg” file.
Have also just noticed that the “Connection link” is also not being built correctly:
Reproduction Steps
- Update AMP and all instances to 2.5.1.4 - 20240731.1 (ADS01 and a DayZ server instance)
- Attempted to restart the DayZ server in the instance after the upgrade
- AMP starts the server, but RCON does not start, therefore AMP cannot see that the server has started
- Diagnosed issue: “beserver_x64.cfg” is being generated incorrectly (blank) on server start instead of with the correct content as specified in “metaconfig.json”