Page MenuHomeFeedback Tracker

RPT Error Server: Object X:XX not found (message type_XXX) Windows Dedicated Server spam
New, NormalPublic

Description

Over the last 6 months we have been spammed by the following message leading to our RPT logs exceeding 10MB and believe it is causing server crashes.

13:49:22 Server: Object 4:34 not found (message Type_114)
13:49:22 Server: Object 4:10 not found (message Type_126)
13:49:22 Server: Object 4:11 not found (message Type_113)
13:49:22 Server: Object 4:12 not found (message Type_120)
13:49:22 Server: Object 4:13 not found (message Type_120)
13:49:22 Server: Object 4:14 not found (message Type_126)
13:49:22 Server: Object 4:15 not found (message Type_113)
13:49:22 Server: Object 4:16 not found (message Type_120)
13:49:22 Server: Object 4:17 not found (message Type_120)
13:49:22 Server: Object 4:18 not found (message Type_126)
13:49:22 Server: Object 4:19 not found (message Type_113)

The crashes begin with desync and eventually lead to a yellow/red chain

Details

Severity
Crash
Resolution
Open
Reproducibility
Always
Operating System
Windows 10 x64
Operating System Version
Microsoft Windows Server 2016 Standard
Category
Dedicated Server
Steps To Reproduce
  1. Start a dedicated windows Server STABLE Branch with the configs attached
  2. Run a mission with a Game master slot (pbo attached)
  3. Place down a unit
  4. View RPT logs
  1. Start a dedicated windows Server PERF Branch (200_147054_09) with the configs attached
  2. Run a mission with a Game master slot (pbo attached)
  3. Place down a unit
  4. View RPT logs

Additional Information

This has been reproduced when using Headless clients with ACEX to rebalance units. We initially thought it was this but after reproducing this error with vanilla Arma we ruled that out.

Event Timeline

JVils created this task.Dec 20 2020, 3:26 PM
JVils added a comment.Feb 7 2021, 8:14 PM

resolved with latest perf/prof update (11) by turning off RPT Spam.

class AdvancedOptions
{
    LogObjectNotFound = false; // (default true, logging enabled)
    SkipDescriptionParsing = false; // (default false, parse description.ext)
    ignoreMissionLoadErrors = false;
};

Yellow chains are basic.cfg related