# Errors installing logstash-mixin-ecs\_compatibility\_support plugin **URL:** \ **Category:** Logstash\ **Created:** [March 10, 2022, 10:32pm UTC](https://discuss.elastic.co/t/errors-installing-logstash-mixin-ecs-compatibility-support-plugin/299374 "2022-03-10T22:32:21Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![mikespharss](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mikespharss/32/102900_2.png) [@mikespharss](https://discuss.elastic.co/u/mikespharss)\ **Post date:** [March 10, 2022, 10:32pm UTC](https://discuss.elastic.co/t/errors-installing-logstash-mixin-ecs-compatibility-support-plugin/299374/1 "2022-03-10T22:32:21Z")
I started having a weird problem where using logstash-plugin to install logstash-output-opensearch was leaving my plugin environment in a broken state. Logstash version: logstash 7.16.1 using bundled JDK version I started seeing this in my test environments when installing logstash plugins ```auto root@dokken:/usr/share/logstash# bin/logstash-plugin install logstash-output-opensearch Using bundled JDK: /usr/share/logstash/jdk OpenJDK 64-Bit Server VM warning: Option UseConcMarkSweepGC was deprecated in version 9.0 and will likely be removed in a future release. Validating logstash-output-opensearch Resolving mixin dependencies Updating mixin dependencies logstash-mixin-ecs_compatibility_support Bundler attempted to update logstash-mixin-ecs_compatibility_support but its version stayed the same Installing logstash-output-opensearch Killed ``` After this error happens, the plugin environment is left in a broken state for any logstash-plugin command, even lists or installing other plugins ```auto ---- Begin output of bin/logstash-plugin install logstash-output-lumberjack ---- STDOUT: Using bundled JDK: /usr/share/logstash/jdk Validating logstash-output-lumberjack Resolving mixin dependencies STDERR: OpenJDK 64-Bit Server VM warning: Option UseConcMarkSweepGC was deprecated in version 9.0 and will likely be removed in a future release. Bundler::ProductionError: You are trying to install in deployment mode after changing your Gemfile. Run `bundle install` elsewhere and add the updated Gemfile.lock to version control. If this is a development machine, remove the /usr/share/logstash/Gemfile freeze by running `bundle config unset frozen`. The dependencies in your gemfile changed You have added to the Gemfile: * logstash-output-opensearch ensure_equivalent_gemfile_and_lockfile at /usr/share/logstash/vendor/bundle/jruby/2.5.0/gems/bundler-2.2.33/lib/bundler/definition.rb:396 setup at /usr/share/logstash/vendor/bundle/jruby/2.5.0/gems/bundler-2.2.33/lib/bundler/runtime.rb:13 setup at /usr/share/logstash/vendor/bundle/jruby/2.5.0/gems/bundler-2.2.33/lib/bundler.rb:150 setup! at /usr/share/logstash/lib/bootstrap/bundler.rb:79 update_logstash_mixin_dependencies at /usr/share/logstash/lib/pluginmanager/install.rb:187 execute at /usr/share/logstash/lib/pluginmanager/install.rb:77 run at /usr/share/logstash/vendor/bundle/jruby/2.5.0/gems/clamp-1.0.1/lib/clamp/command.rb:68 execute at /usr/share/logstash/vendor/bundle/jruby/2.5.0/gems/clamp-1.0.1/lib/clamp/subcommand/execution.rb:11 run at /usr/share/logstash/vendor/bundle/jruby/2.5.0/gems/clamp-1.0.1/lib/clamp/command.rb:68 run at /usr/share/logstash/vendor/bundle/jruby/2.5.0/gems/clamp-1.0.1/lib/clamp/command.rb:133
at /usr/share/logstash/lib/pluginmanager/main.rb:64 ---- End output of bin/logstash-plugin install logstash-output-lumberjack ---- ``` When I tried as a test to just install that dependency plugin manually, I got a failure reporting that it was not a valid logstash plugin ```auto root@dokken:/usr/share/logstash# bin/logstash-plugin install logstash-mixin-ecs_compatibility_support Using bundled JDK: /usr/share/logstash/jdk OpenJDK 64-Bit Server VM warning: Option UseConcMarkSweepGC was deprecated in version 9.0 and will likely be removed in a future release. Validating logstash-mixin-ecs_compatibility_support logstash-mixin-ecs_compatibility_support is not a Logstash plugin ERROR: Installation aborted, verification failed for logstash-mixin-ecs_compatibility_support ``` This appears to be because the logstash-mixin-ecs\_compatibility\_support gemspec doesn't have the metadata defined? Though that doesn't seem new so I'm confused why this recently started happening. Regardless, if I install the logstash-mixin-ecs\_compatibility\_support plugin with the `--no-verify` flag, then that installation succeeds. Then I can install the logstash-output-opensearch plugin and that also succeeds. Likewise installing the logstash-output-opensearch plugin itself with the `--no-verify` flag succeeds. I wasn't sure if this was a real bug or just something weird in our environment that I can't pinpoint, but it seems like two problems: 1. logstash-plugin fails to install the logstash-mixin-ecs\_compatibility\_support dependency, possibly due to missing metadata? 2. logstash-plugin did not gracefully handle the failure of installing a dependency plugin, leaving the plugin environment in a broken state or possibly 1. This is all actually a problem with logstash-output-opensearch (which I understand is not maintained by Elastic), even though it can be remediated by manually installing the dependency with no-verify first. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [March 10, 2022, 10:32pm UTC](https://discuss.elastic.co/t/errors-installing-logstash-mixin-ecs-compatibility-support-plugin/299374/2 "2022-03-10T22:32:21Z")
Opensearch is an AWS run product and differs from the original Elasticsearch and Kibana products that Elastic builds and maintains. You may need to contact them directly for further assistance. (This is an automated response from your friendly Elastic bot. Please report this post if you have any suggestions or concerns :elasticheart: ) ---
**Author:** ![Badger](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/badger/32/25190_2.png) [@Badger](https://discuss.elastic.co/u/Badger)\ **Post date:** [March 10, 2022, 11:05pm UTC](https://discuss.elastic.co/t/errors-installing-logstash-mixin-ecs-compatibility-support-plugin/299374/3 "2022-03-10T23:05:14Z")
This open [issue](https://github.com/elastic/logstash/issues/13505) is related. ---
**Author:** ![mikespharss](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mikespharss/32/102900_2.png) [@mikespharss](https://discuss.elastic.co/u/mikespharss)\ **Post date:** [March 11, 2022, 5:28pm UTC](https://discuss.elastic.co/t/errors-installing-logstash-mixin-ecs-compatibility-support-plugin/299374/4 "2022-03-11T17:28:33Z")
Hmm it does look similar but I'll note that I'm not making any manual edits to a Gemfile, I'm exclusively using the logstash-plugin command. And I don't end up in this state if I install the plugin with `--no-verify` ---
**Author:** ![mikespharss](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mikespharss/32/102900_2.png) [@mikespharss](https://discuss.elastic.co/u/mikespharss)\ **Post date:** [March 17, 2022, 7:28pm UTC](https://discuss.elastic.co/t/errors-installing-logstash-mixin-ecs-compatibility-support-plugin/299374/5 "2022-03-17T19:28:50Z")
Just as a follow-up here, I want to add that have had some testing with another co-worker, and they are not experiencing the failures I am, even though we're running the same Dockerfile and chef recipes, so that does support the premise that there is just something off in my local environment that is leading to some abnormal failures. It's still unclear why this is happening but I don't have enough reproducible data to fairly claim it is an issue with elastic code. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [April 14, 2022, 7:29pm UTC](https://discuss.elastic.co/t/errors-installing-logstash-mixin-ecs-compatibility-support-plugin/299374/6 "2022-04-14T19:29:33Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.