# Logstash 6.1.1 : jar-dependencies conflicts
**URL:** https://discuss.elastic.co/t/logstash-6-1-1-jar-dependencies-conflicts/126131
**Category:** Logstash
**Created:** [March 29, 2018, 5:15pm UTC](https://discuss.elastic.co/t/logstash-6-1-1-jar-dependencies-conflicts/126131 "2018-03-29T17:15:20Z")
**Posts on this page:** 10
**Page:** 1
### Author:  [@samia](https://discuss.elastic.co/u/samia)
#### Post date: [March 29, 2018, 5:15pm UTC](https://discuss.elastic.co/t/logstash-6-1-1-jar-dependencies-conflicts/126131/1 "2018-03-29T17:15:21Z")
Hello !
I'm running Logstash 6.1.1
I've updated a logstash plugin : logstash-input-udp.
Since this update I'm having apparently a conflict between different versions of jar-dependencies.
Here's what I find in the logs :
Gem::LoadError: You have already activated jar-dependencies 0.3.12, but your Gemfile requires jar-dependencies 0.3.11. Prepending `bundle exec` to your command may solve this.
I did some actions, but neither succeeded :
1. Removed the logstash-input-udp plugin
2. Re-installed the plugin and updated it
3. Removed the whole /usr/share/logstash tree and the logstash rpm. Then re-installed Logstash 6.1.1
I always have the same error.
But when re-installing Logstash, instead of having these errors in /var/log/messages ; I'm having now this error in the logstash logs directly :
ERROR][logstash.agent] Failed to execute action {:action=\>LogStash::PipelineAction::Create/pipeline\_id:main, :exception=\>"LogStash::ConfigurationError", :message=\>"Something is wrong with your configuration.", :backtrace=\>["/usr/share/logstash/logstash-core/lib/logstash/config/mixin.rb:89:in `config_init'", "/usr/share/logstash/logstash-core/lib/logstash/filters/base.rb:128:in`initialize'", "/usr/share/logstash/logstash-core/lib/logstash/filter\_delegator.rb:23:in `initialize'", "/usr/share/logstash/logstash-core/lib/logstash/plugins/plugin_factory.rb:88:in`plugin'", "/usr/share/logstash/logstash-core/lib/logstash/pipeline.rb:114:in `plugin'", "(eval):92:in`'", "org/jruby/RubyKernel.java:994:in `eval'", "/usr/share/logstash/logstash-core/lib/logstash/pipeline.rb:86:in`initialize'", "/usr/share/logstash/logstash-core/lib/logstash/pipeline.rb:171:in `initialize'", "/usr/share/logstash/logstash-core/lib/logstash/pipeline_action/create.rb:40:in`execute'", "/usr/share/logstash/logstash-core/lib/logstash/agent.rb:335:in `block in converge_state'", "/usr/share/logstash/logstash-core/lib/logstash/agent.rb:141:in`with\_pipelines'", "/usr/share/logstash/logstash-core/lib/logstash/agent.rb:332:in `block in converge_state'", "org/jruby/RubyArray.java:1734:in`each'", "/usr/share/logstash/logstash-core/lib/logstash/agent.rb:319:in `converge_state'", "/usr/share/logstash/logstash-core/lib/logstash/agent.rb:166:in`block in converge\_state\_and\_update'", "/usr/share/logstash/logstash-core/lib/logstash/agent.rb:141:in `with_pipelines'", "/usr/share/logstash/logstash-core/lib/logstash/agent.rb:164:in`converge\_state\_and\_update'", "/usr/share/logstash/logstash-core/lib/logstash/agent.rb:90:in `execute'", "/usr/share/logstash/logstash-core/lib/logstash/runner.rb:343:in`block in execute'", "/usr/share/logstash/vendor/bundle/jruby/2.3.0/gems/stud-0.0.23/lib/stud/task.rb:24:in `block in initialize'"]}
I'm not a java nor a ruby guru and I'm rather stucked at this point.
Thank you in advance for your help.
---
### Author:  [@yaauie](https://discuss.elastic.co/u/yaauie)
#### Post date: [March 29, 2018, 5:26pm UTC](https://discuss.elastic.co/t/logstash-6-1-1-jar-dependencies-conflicts/126131/2 "2018-03-29T17:26:32Z")
Oy. That's not a very helpful error message 😩
1. what is the pipeline configuration (or at least, what inputs, outputs, and filters does it use)?
2. what plugins are currently installed? `bin/logstash-plugin list --verbose`
---
### Author:  [@samia](https://discuss.elastic.co/u/samia)
#### Post date: [April 10, 2018, 12:57pm UTC](https://discuss.elastic.co/t/logstash-6-1-1-jar-dependencies-conflicts/126131/3 "2018-04-10T12:57:14Z")
Hello,
Sorry for the late reply: I was on holiday.
Here are the details you asked for :
- plugins list :
=============
./bin/logstash-plugin list --verbose
logstash-codec-cef (5.0.2)
logstash-codec-collectd (3.0.8)
logstash-codec-dots (3.0.6)
logstash-codec-edn (3.0.6)
logstash-codec-edn\_lines (3.0.6)
logstash-codec-es\_bulk (3.0.6)
logstash-codec-fluent (3.1.5)
logstash-codec-graphite (3.0.5)
logstash-codec-json (3.0.5)
logstash-codec-json\_lines (3.0.5)
logstash-codec-line (3.0.6)
logstash-codec-msgpack (3.0.7)
logstash-codec-multiline (3.0.8)
logstash-codec-netflow (3.9.0)
logstash-codec-plain (3.0.6)
logstash-codec-rubydebug (3.0.5)
logstash-filter-aggregate (2.7.2)
logstash-filter-anonymize (3.0.6)
logstash-filter-cidr (3.1.2)
logstash-filter-clone (3.0.5)
logstash-filter-csv (3.0.7)
logstash-filter-date (3.1.9)
logstash-filter-de\_dot (1.0.3)
logstash-filter-dissect (1.1.2)
logstash-filter-dns (3.0.7)
logstash-filter-drop (3.0.5)
logstash-filter-elasticsearch (3.2.1)
logstash-filter-fingerprint (3.1.2)
logstash-filter-geoip (5.0.2)
logstash-filter-grok (4.0.0)
logstash-filter-jdbc\_streaming (1.0.3)
logstash-filter-json (3.0.5)
logstash-filter-kv (4.0.3)
logstash-filter-metrics (4.0.5)
logstash-filter-mutate (3.2.0)
logstash-filter-ruby (3.1.3)
logstash-filter-sleep (3.0.6)
logstash-filter-split (3.1.6)
logstash-filter-syslog\_pri (3.0.5)
logstash-filter-throttle (4.0.4)
logstash-filter-translate (3.0.4)
logstash-filter-truncate (1.0.4)
logstash-filter-urldecode (3.0.6)
logstash-filter-useragent (3.2.2)
logstash-filter-xml (4.0.5)
logstash-input-beats (5.0.4)
logstash-input-dead\_letter\_queue (1.1.2)
logstash-input-elasticsearch (4.1.1)
logstash-input-exec (3.1.5)
logstash-input-file (4.0.3)
logstash-input-ganglia (3.1.3)
logstash-input-gelf (3.0.7)
logstash-input-generator (3.0.5)
logstash-input-graphite (3.0.4)
logstash-input-heartbeat (3.0.5)
logstash-input-http (3.0.8)
logstash-input-http\_poller (4.0.4)
logstash-input-imap (3.0.5)
logstash-input-jdbc (4.3.2)
logstash-input-kafka (8.0.2)
logstash-input-pipe (3.0.6)
logstash-input-rabbitmq (6.0.2)
logstash-input-redis (3.1.6)
logstash-input-s3 (3.1.8)
logstash-input-snmptrap (3.0.5)
logstash-input-sqs (3.0.6)
logstash-input-stdin (3.2.5)
logstash-input-syslog (3.2.4)
logstash-input-tcp (5.0.2)
logstash-input-twitter (3.0.7)
logstash-input-udp (3.3.0)
logstash-input-unix (3.0.6)
logstash-output-cloudwatch (3.0.7)
logstash-output-csv (3.0.6)
logstash-output-elasticsearch (9.0.2)
logstash-output-email (4.0.6)
logstash-output-file (4.2.1)
logstash-output-graphite (3.1.4)
logstash-output-http (5.1.1)
logstash-output-kafka (7.0.4)
logstash-output-lumberjack (3.1.5)
logstash-output-nagios (3.0.5)
logstash-output-null (3.0.4)
logstash-output-pagerduty (3.0.6)
logstash-output-pipe (3.0.5)
logstash-output-rabbitmq (5.0.3)
logstash-output-redis (4.0.3)
logstash-output-s3 (4.0.13)
logstash-output-sns (4.0.6)
logstash-output-sqs (5.0.2)
logstash-output-stdout (3.1.3)
logstash-output-tcp (5.0.2)
logstash-output-udp (3.0.5)
logstash-output-webhdfs (3.0.5)
logstash-patterns-core (4.1.2)
- Pipeline configuration
====================
1. INPUTS :
2. OUTPUTS : elasticsearch
3. FILTERS :
(\*) As I mentionned it, it's after the logstash-input-udp plugin update, that the mess appeared.
But even if I remove this input from my configuration, logstash does not run.
Thank you in advance for your help !
---
### Author:  [@yaauie](https://discuss.elastic.co/u/yaauie)
#### Post date: [April 10, 2018, 9:46pm UTC](https://discuss.elastic.co/t/logstash-6-1-1-jar-dependencies-conflicts/126131/4 "2018-04-10T21:46:47Z")
did you use the `bin/logstash-plugin update logstash-input-udp` command to update, or some other means? The above is _supposed_ to resolve these kinds of conflicts for us...
---
### Author:  [@samia](https://discuss.elastic.co/u/samia)
#### Post date: [April 12, 2018, 12:44pm UTC](https://discuss.elastic.co/t/logstash-6-1-1-jar-dependencies-conflicts/126131/5 "2018-04-12T12:44:31Z")
Hi Ry,
Here's what I did exactly :
- I first tried to update it through the logstash-plugin update command as you said above.
However I couldn't do it (and I don't remember the error message). But I know I had to update my system (sudo yum update).
- As the problem didn't disappear, even when removing the config file using input-udp, I removed the the plugin by using
./bin/logstash-plugin remove logstash-input-udp
Then I re-installed it :
./bin/logstash-plugin install logstash-input-udp
Still, the problem didn't disappear.
So, I deinstalled all logstash 6.1.1 and re-installed it completely :
- sudo rpm -e logstash-6.1.1-1.noarch
- sudo rpm -ihv logstash-6.1.1.rpm
But it hasn't change the situation.
I don't know what to do. And I'm ready to de-install the whole ELK 6.1.1 stack and install the last stable version of the stack.
Thanks once again.
---
### Author:  [@yaauie](https://discuss.elastic.co/u/yaauie)
#### Post date: [April 12, 2018, 11:21pm UTC](https://discuss.elastic.co/t/logstash-6-1-1-jar-dependencies-conflicts/126131/6 "2018-04-12T23:21:34Z")
- On a fresh install of logstash via `rpm` (without trying the plugin update), are you getting the above issues?
- There are a couple patch releases of Logstash since 6.1.1 that are fully compatible with any 6.1.x version of the rest of the Elastic Stack -- 6.1.4 is the most recent, and it includes a bump of `logstash-input-udp` [from `v3.1.3` to `v3.2.1`](https://github.com/elastic/logstash/compare/v6.1.1...v6.1.4#diff-ff7f984784f6cafec43126e48d8f5f5cL380), so you may not have to do the plugin upgrade on your own.
For good measure, what JVM/JDK are you using?
-
```auto
java -version
```
-
```auto
echo ${JAVA_HOME?}
```
---
### Author:  [@samia](https://discuss.elastic.co/u/samia)
#### Post date: [April 13, 2018, 12:42pm UTC](https://discuss.elastic.co/t/logstash-6-1-1-jar-dependencies-conflicts/126131/7 "2018-04-13T12:42:10Z")
- Yes. I reinstalled Logstash 6.1.1 via rpm and the issues are still there.
- I didn't apply any patches after the reinstall. I will do it on monday.
- I'm using the OpenJDK 1.8 on a RedHat Linux Server 7.4
===\> java -version gives me this :
```
openjdk version "1.8.0_161"
OpenJDK Runtime Environment (build 1.8.0_161-b14)
OpenJDK 64-Bit Server VM (build 25.161-b14, mixed mode)
```
The error message makes me think that on updating the udp plugin I changed something in java itself (?). But as I said it above, I'm not a java person.
Never the less, I'll install the logstash patches, and I'll see what happens.
---
### Author:  [@samia](https://discuss.elastic.co/u/samia)
#### Post date: [April 17, 2018, 1:19pm UTC](https://discuss.elastic.co/t/logstash-6-1-1-jar-dependencies-conflicts/126131/8 "2018-04-17T13:19:13Z")
Hi Ry,
I upgraded logstash from 6.1.1 to 6.1.4 (the last version for 6.1).
It didn't help. I still have the same error log (see below).
As I told you in my last message, the issue seems not to be in the core of logstash but related to the java/Gem/ruby stuff :
before, I re-install logstash the error message was the following :
**_Gem::LoadError: You have already activated jar-dependencies 0.3.12, but your Gemfile requires jar-dependencies 0.3.11. Prepending bundle exec to your command may solve this._**
And I don't know how to go back to jar-dependencies 0.3.11, if this ever makes sense.
When searching for the _jar-dependencies.gemspec_ file, I find this :
**_find . -name jar-dependencies.gemspec -print_**
_ **./vendor/bundle/jruby/2.3.0/gems/jar-dependencies-0.3.12/jar-dependencies.gemspec** _
# Logstash log error :
Failed to execute action {:action=\>LogStash::PipelineAction::Create/pipeline\_id:main, :exception=\>"LogStash::ConfigurationError", :message=\>"Something is wrong with your configuration.", :backtrace=\>["/usr/share/logstash/logstash-core/lib/logstash/config/mixin.rb:89:in `config_init'", "/usr/share/logstash/logstash-core/lib/logstash/filters/base.rb:128:in`initialize'", "/usr/share/logstash/logstash-core/lib/logstash/filter\_delegator.rb:23:in `initialize'", "/usr/share/logstash/logstash-core/lib/logstash/plugins/plugin_factory.rb:88:in`plugin'", "/usr/share/logstash/logstash-core/lib/logstash/pipeline.rb:114:in `plugin'", "(eval):92:in`'", "org/jruby/RubyKernel.java:994:in `eval'", "/usr/share/logstash/logstash-core/lib/logstash/pipeline.rb:86:in`initialize'", "/usr/share/logstash/logstash-core/lib/logstash/pipeline.rb:171:in `initialize'", "/usr/share/logstash/logstash-core/lib/logstash/pipeline_action/create.rb:40:in`execute'", "/usr/share/logstash/logstash-core/lib/logstash/agent.rb:335:in `block in converge_state'", "/usr/share/logstash/logstash-core/lib/logstash/agent.rb:141:in`with\_pipelines'", "/usr/share/logstash/logstash-core/lib/logstash/agent.rb:332:in `block in converge_state'", "org/jruby/RubyArray.java:1734:in`each'", "/usr/share/logstash/logstash-core/lib/logstash/agent.rb:319:in `converge_state'", "/usr/share/logstash/logstash-core/lib/logstash/agent.rb:166:in`block in converge\_state\_and\_update'", "/usr/share/logstash/logstash-core/lib/logstash/agent.rb:141:in `with_pipelines'", "/usr/share/logstash/logstash-core/lib/logstash/agent.rb:164:in`converge\_state\_and\_update'", "/usr/share/logstash/logstash-core/lib/logstash/agent.rb:90:in `execute'", "/usr/share/logstash/logstash-core/lib/logstash/runner.rb:343:in`block in execute'", "/usr/share/logstash/vendor/bundle/jruby/2.3.0/gems/stud-0.0.23/lib/stud/task.rb:24:in `block in initialize'"]}
---
### Author:  [@samia](https://discuss.elastic.co/u/samia)
#### Post date: [April 17, 2018, 3:25pm UTC](https://discuss.elastic.co/t/logstash-6-1-1-jar-dependencies-conflicts/126131/9 "2018-04-17T15:25:04Z")
Finally, it worked !
First, I recognize that I've missed another error message in the logstash logs ☹
I use geo-location and after the first reinstall : my geo database has been removed.
I reinstalled my geo database.
Moreover, I removed the whole subdir :
logstash/vendor/bundle/jruby/2.3.0/gems/jar-dependencies-0.3.12 (which was present even though I re-installed logstash multiple times)
- removed the logstash package (yum remove)
- re-installed logstash-6.1.1 (yum install)
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [May 15, 2018, 3:25pm UTC](https://discuss.elastic.co/t/logstash-6-1-1-jar-dependencies-conflicts/126131/10 "2018-05-15T15:25:17Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.