# Fleet server error: "Eat bulk checkin error; Keep on truckin'"

**URL:** <https://discuss.elastic.co/t/fleet-server-error-eat-bulk-checkin-error-keep-on-truckin/377477>\
**Category:** Elastic Agent\
**Created:** [April 24, 2025, 7:57am UTC](https://discuss.elastic.co/t/fleet-server-error-eat-bulk-checkin-error-keep-on-truckin/377477 "2025-04-24T07:57:01Z")\
**Posts on this page:** 2\
**Page:** 1

<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:** [April 24, 2025, 7:57am UTC](https://discuss.elastic.co/t/fleet-server-error-eat-bulk-checkin-error-keep-on-truckin/377477/1 "2025-04-24T07:57:01Z")

</div>

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 object, but found a concrete value","ecs.version":"1.6.0","service.name":"fleet-server","service.type":"fleet-server","ecs.version":"1.6.0"}`  
and  
`"message":"Eat bulk checkin error; Keep on truckin'"`  
and  
`"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"`

I don't really know where this error comes from. Around March 20, I upgraded the elastic stack version from 8.17.1 to 8.17.3. I also upgraded some agents in the area that day.  
For two agents, the upgrade failed and they stayed on 8.17.1. Since then, in the fleet, for the agent that failed to upgrade, there is a message "Agent upgrade is stuck in failed state. Agent upgrade failed. Consider restarting the upgrade."

However, I also checked the message regarding the local\_metadata mapping, which is in the .fleet-agents-7 index  
for practically all local\_metadata some mapping is specified, while for **"local\_metadata.elastic.agent.complete"** there is an **"unknown field"**. When I looked in the data views in management, this field is not there.

And now I wonder if this is a matter of agent upgrade or mapping? This index is without a template and without an ingest pipeline, so as a user I also cannot update the mapping for this field. I get this message:  
`"action [indices:admin/mapping/put] is unauthorized for user [xxxxxxx.x] with effective roles [admin,editor,monitoring_user,superuser] on restricted indices [.fleet-agents-7], this action is granted by the index privileges [manage,all]"`

---

<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:06pm UTC](https://discuss.elastic.co/t/fleet-server-error-eat-bulk-checkin-error-keep-on-truckin/377477/2 "2025-06-06T21:06:00Z")

</div>

Thanks, the `local_metadata.elastic.agent.complete` attribute being missing is a bug, 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)