# ELK 5.3.2 with X-Pack - Error Event in LogStash Log

**URL:** <https://discuss.elastic.co/t/elk-5-3-2-with-x-pack-error-event-in-logstash-log/86565>\
**Category:** Logstash\
**Created:** [May 21, 2017, 10:39am UTC](https://discuss.elastic.co/t/elk-5-3-2-with-x-pack-error-event-in-logstash-log/86565 "2017-05-21T10:39:10Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![GJahchan](https://avatars.discourse-cdn.com/v4/letter/g/48db29/32.png) [@GJahchan](https://discuss.elastic.co/u/GJahchan)\
**Post date:** [May 21, 2017, 10:39am UTC](https://discuss.elastic.co/t/elk-5-3-2-with-x-pack-error-event-in-logstash-log/86565/1 "2017-05-21T10:39:10Z")

</div>

Running ELK 5.3.2 on CentOS 7.3. I am seeing a stream of the following error events (once every ten seconds) which are seemingly due to X-Pack:

[2017-05-21T13:27:11,120][ERROR][logstash.outputs.elasticsearch] Got a bad response code from server, but this code is not considered retryable. Request will be dropped {:code=\>400, :response\_body=\>"{"error":{"root\_cause":[{"type":"illegal\_argument\_exception","reason":"request [/\_xpack/monitoring/\_bulk] contains unrecognized parameters: [interval], [system\_api\_version], [system\_id]"}],"type":"illegal\_argument\_exception","reason":"request [/\_xpack/monitoring/\_bulk] contains unrecognized parameters: [interval], [system\_api\_version], [system\_id]"},"status":400}"}

They do not seem to have a negative impact on LogStash feeding events into ElasticSearch, but I am not comfortable with these errors.

Any idea about how to identify the root cause and resolve?

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [June 18, 2017, 10:39am UTC](https://discuss.elastic.co/t/elk-5-3-2-with-x-pack-error-event-in-logstash-log/86565/2 "2017-06-18T10:39:43Z")

</div>

Closed on June 18, 2017, 10:39am UTC

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.