# Fleet-server mapping error in 9.0.2

**URL:** <https://discuss.elastic.co/t/fleet-server-mapping-error-in-9-0-2/378837>\
**Category:** Elastic Security\
**Created:** [June 4, 2025, 6:00am UTC](https://discuss.elastic.co/t/fleet-server-mapping-error-in-9-0-2/378837 "2025-06-04T06:00:22Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![syk](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/syk/32/141533_2.png) [@syk](https://discuss.elastic.co/u/syk)\
**Post date:** [June 4, 2025, 6:00am UTC](https://discuss.elastic.co/t/fleet-server-mapping-error-in-9-0-2/378837/1 "2025-06-04T06:00:22Z")

</div>

Self hosted ELK 9.0.2 records this mapping error from fleet-server running on an elastic-cluster-node once per minute:

```auto
 "error.message": "elastic fail 400: document_parsing_exception: [1:207] object mapping for [local_metadata] tried to parse field [local_metadata] as object, but found a concrete value"

```

[...]

```auto
    "service.type": [
      "fleet-server"
    ],
    "component.id": [
      "fleet-server-default"
    ],
    "host.os.version": [
      "24.04.2 LTS (Noble Numbat)"
    ],
    "host.os.name": [
      "Ubuntu"
    ],
    "log.level": [
      "error"
    ],
    "agent.name": [
      "srv-elastic01"
    ],
    "host.name": [
      "srv-elastic01"
    ],
    "event.agent_id_status": [
      "verified"
    ],
    "host.os.type": [
      "linux"
    ],
    "log.source": [
      "fleet-server-default"
    ],
    "input.type": [
      "filestream"

```

[...]  
and the Dashboard "[Elastic Agent] Concerning Agents" shows this message instead of the error message:

```auto
 "message": "Eat bulk checkin error; Keep on truckin'"

```

Is this a known bug? Can we do anything to fix it ourselves?

---

<div class="post-metadata">

**Author:** ![Mario\_22](https://avatars.discourse-cdn.com/v4/letter/m/4491bb/32.png) [@Mario\_22](https://discuss.elastic.co/u/Mario_22)\
**Post date:** [June 6, 2025, 6:28pm UTC](https://discuss.elastic.co/t/fleet-server-mapping-error-in-9-0-2/378837/2 "2025-06-06T18:28:56Z")

</div>

I wrote the same problem.

> [@Fleet server error: "Eat bulk checkin error; Keep on truckin'"](https://discuss.elastic.co/t/fleet-server-error-eat-bulk-checkin-error-keep-on-truckin/377477):
>
> Hello, Since March 20, an error has appeared in the fleet-server logs {"log.level":"error","@timestamp":"2025-04-23T10:21:12.631Z","message":"Eat bulk checkin error; Keep on truckin'","component":{"binary":"fleet-server","dataset":"elastic\_agent.fleet\_server","id":"fleet-server-default","type":"fleet-server"},"log":{"source":"fleet-server-default"},"error.message":"elastic fail 400: document\_parsing\_exception: [1:207] object mapping for [local\_metadata] tried to parse field [local\_metadata] as…

I think that problem is with upgrading alestic agent and It's stucks in progress. He can't upgrade and he's in frame task which a status is in upgrading (c.a 1 month).

---

<div class="post-metadata">

**Author:** ![MichelLaterman](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/michellaterman/32/110221_2.png) [@MichelLaterman](https://discuss.elastic.co/u/MichelLaterman)\
**Post date:** [June 6, 2025, 9:07pm UTC](https://discuss.elastic.co/t/fleet-server-mapping-error-in-9-0-2/378837/3 "2025-06-06T21:07:24Z")

</div>

This is unfortunatly a bug where we introduced a new metadata attribute `local_metadata.elastic.agent.complete` with the agent but did not add the mapping into elasticsearch, we're working on the fix that should go into our next patch releases: [Add `complete` attribute to .fleet-agents docs by pkoutsovasilis · Pull Request #127651 · elastic/elasticsearch · GitHub](https://github.com/elastic/elasticsearch/pull/127651)