# Logstash breaks when disabling certain X-pack features **URL:** \ **Category:** Logstash\ **Created:** [June 15, 2017, 7:05am UTC](https://discuss.elastic.co/t/logstash-breaks-when-disabling-certain-x-pack-features/89511 "2017-06-15T07:05:36Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![bjorn](https://avatars.discourse-cdn.com/v4/letter/b/74df32/32.png) [@bjorn](https://discuss.elastic.co/u/bjorn)\ **Post date:** [June 15, 2017, 7:05am UTC](https://discuss.elastic.co/t/logstash-breaks-when-disabling-certain-x-pack-features/89511/1 "2017-06-15T07:05:36Z")
When installing x-pack on a fresh Ubuntu 17.04 install, (Logstash 5.4.1, Elasticsearch 5.4.1, Kibana 5.4.1 from Elastic repo), Logstash breaks when disabling monitoring (xpack.monitoring.enabled: false in elasticsearch.yml and kibana.yml). Using unmodified packages from Elastic, Logstash fails with the following error message: > [2017-06-14T21:45:40,102][ERROR][logstash.outputs.elasticsearch] Encountered an unexpected error submitting a bulk request! Will retry. {:error\_message=\>"uninitialized constant LogStash::Outputs::Elasticsearch::Common::RETRYABLE\_CODES", :class=\>"NameError", :backtrace=\>["org/jruby/RubyModule.java:2719:in 'const\_missing'", "/usr/share/logstash/vendor/bundle/jruby/1.9/gems/logstash-output-elasticsearch-7.3.1-java/lib/logstash/outputs/elasticsearch/common.rb:248:in 'safe\_bulk'", "/usr/share/logstash/vendor/bundle/jruby/1.9/gems/logstash-output-elasticsearch-7.3.1-java/lib/logstash/outputs/elasticsearch/common.rb:118:in 'submit'", "/usr/share/logstash/vendor/bundle/jruby/1.9/gems/logstash-output-elasticsearch-7.3.1-java/lib/logstash/outputs/elasticsearch/common.rb:86:in 'retrying\_submit'", "/usr/share/logstash/vendor/bundle/jruby/1.9/gems/logstash-output-elasticsearch-7.3.1-java/lib/logstash/outputs/elasticsearch/common.rb:37:in 'multi\_receive'", "/usr/share/logstash/logstash-core/lib/logstash/output\_delegator\_strategies/shared.rb:13:in 'multi\_receive'", "/usr/share/logstash/logstash-core/lib/logstash/output\_delegator.rb:47:in 'multi\_receive'", "/usr/share/logstash/logstash-core/lib/logstash/pipeline.rb:407:in 'output\_batch'", "org/jruby/RubyHash.java:1342:in 'each'", "/usr/share/logstash/logstash-core/lib/logstash/pipeline.rb:406:in 'output\_batch'", "/usr/share/logstash/logstash-core/lib/logstash/pipeline.rb:352:in 'worker\_loop'", "/usr/share/logstash/logstash-core/lib/logstash/pipeline.rb:317:in `start\_workers'"]} Then I upgraded the logstash-output-elasticsearch plugin: > ``` > # /usr/share/logstash/bin/logstash-plugin update logstash-output-elasticsearch > Updating logstash-output-elasticsearch > Updated logstash-output-elasticsearch 7.3.1 to 7.3.5 > > ``` Logstash still fails, but with a new error message: > [2017-06-14T22:35:59,087][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}"} Enabling monitoring (removing the settings from elasticsearch.yml and kibana.yml) makes the errors go away and Logstash works as expected. Issue is consistent and has been reproduced twice, with Ubuntu 16.10 and 17.04. ---
**Author:** ![Bargs](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bargs/32/5429_2.png) [@Bargs](https://discuss.elastic.co/u/Bargs)\ **Post date:** [June 15, 2017, 9:47pm UTC](https://discuss.elastic.co/t/logstash-breaks-when-disabling-certain-x-pack-features/89511/2 "2017-06-15T21:47:43Z")
Have you tried setting `xpack.monitoring.enabled: false` in your logstash.yml? ---
**Author:** ![bjorn](https://avatars.discourse-cdn.com/v4/letter/b/74df32/32.png) [@bjorn](https://discuss.elastic.co/u/bjorn)\ **Post date:** [June 16, 2017, 7:01am UTC](https://discuss.elastic.co/t/logstash-breaks-when-disabling-certain-x-pack-features/89511/3 "2017-06-16T07:01:21Z")
Thank you, that made the errors go away and Logstash works as expected. The X-pack documentation at [https://www.elastic.co/guide/en/x-pack/current/monitoring-settings.html](https://www.elastic.co/guide/en/x-pack/current/monitoring-settings.html) should be updated to reflect this requirement. Currently it states that `xpack.monitoring.enabled: false` should be added to elasticsearch.yml and kibana.yml only. On a related note, the X-pack settings start page ([https://www.elastic.co/guide/en/x-pack/current/xpack-settings.html](https://www.elastic.co/guide/en/x-pack/current/xpack-settings.html)) also specifies elasticsearch.yml and kibana.yml only. ---
**Author:** ![Bargs](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bargs/32/5429_2.png) [@Bargs](https://discuss.elastic.co/u/Bargs)\ **Post date:** [June 16, 2017, 1:44pm UTC](https://discuss.elastic.co/t/logstash-breaks-when-disabling-certain-x-pack-features/89511/4 "2017-06-16T13:44:43Z")
That's a good point, definitely an oversight. Thanks for the heads up, I've opened an issue get it fixed. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 14, 2017, 1:45pm UTC](https://discuss.elastic.co/t/logstash-breaks-when-disabling-certain-x-pack-features/89511/5 "2017-07-14T13:45:01Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.