Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Install issues logstash-input-jms-3.0.1 on logstash 5.2.2 #20

Open
JohanHolman opened this issue Mar 23, 2017 · 5 comments
Open

Install issues logstash-input-jms-3.0.1 on logstash 5.2.2 #20

JohanHolman opened this issue Mar 23, 2017 · 5 comments

Comments

@JohanHolman
Copy link

JohanHolman commented Mar 23, 2017

I've got the latest logstash version installed (tar extract) on Red Hat Enterprise Linux Server release 6.7

# cd logstash
# bin/logstash --version
logstash 5.2.2
# vendor/jruby/bin/jruby --version
jruby 1.7.25 (1.9.3p551) 2016-04-13 867cb81 on Java HotSpot(TM) 64-Bit Server VM 1.8.0_66-b17 +jit [linux-amd64]

Sematic logger < 4.0.0 was needed so, I installed it like this (not sure this is the right way)

# cp /tmp/semantic_logger-3.4.1.gem  .
# env GEM_HOME=vendor/bundle/jruby/1.9 vendor/jruby/bin/jruby vendor/jruby/bin/gem install semantic_logger -V
Successfully installed semantic_logger-3.4.1

Check if sematic logger is installed

# env GEM_HOME=vendor/bundle/jruby/1.9 vendor/jruby/bin/jruby -S gem list --local|grep semantic
semantic_logger (3.4.1)

Try to install the plugin 3.0.1

# ./bin/logstash-plugin install file:///tmp/logstash-input-jms-3.0.1-java.gem.zip
Installing file: /tmp/logstash-input-jms-3.0.1-java.gem.zip
ERROR: An error occured when installing the: file:///tmp/logstash-input-jms-3.0.1-java.gem.zip, to have more information about the error add a DEBUG=1 before running the command., message: Bundler could not find compatible versions for gem "semantic_logger":
  In Gemfile:
    logstash-input-jms (= 3.0.1) java depends on
      semantic_logger (< 4.0.0) java
Could not find gem 'semantic_logger (< 4.0.0) java', which is required by gem 'logstash-input-jms (= 3.0.1) java', in any of the sources.

jruby-jms >= 1.2.0 was needed for plugin 3.0.0. I installed it like this (not sure this is the right way)

# env GEM_HOME=vendor/bundle/jruby/1.9 vendor/jruby/bin/jruby vendor/jruby/bin/gem install jruby-jms -V
Successfully installed jruby-jms-1.2.0-java

Check if jruby-jms is installed

# env GEM_HOME=vendor/bundle/jruby/1.9 vendor/jruby/bin/jruby -S gem list --local|grep "jms"
jruby-jms (1.2.0 java)

Try to install the plugin 3.0.0

# ./bin/logstash-plugin install file:///home/onl19206/logstash-input-jms-3.0.0-java.gem.zip`
Installing file: /home/onl19206/logstash-input-jms-3.0.0-java.gem.zip
ERROR: An error occured when installing the: file:///home/onl19206/logstash-input-jms-3.0.0-java.gem.zip, Installing, file:, /home/onl19206/logstash-input-jms-3.0.0-java.gem.zip, to have more information about the error add a DEBUG=1 before running the command., message: Bundler could not find compatible versions for gem "jruby-jms":
  In Gemfile:
    logstash-input-jms (= 3.0.0) java depends on
      jruby-jms (>= 1.2.0) java
Could not find gem 'jruby-jms (>= 1.2.0) java', which is required by gem 'logstash-input-jms (= 3.0.0) java', in any of the sources.

So what do I do wrong here?

@JohanHolman JohanHolman changed the title Insall issues logstash-input-jms-3.0.1 on logstash 5.2.2 Install issues logstash-input-jms-3.0.1 on logstash 5.2.2 Mar 23, 2017
@niempy
Copy link

niempy commented Mar 24, 2017

+1 if this could be solved

@AgentW4C
Copy link
Collaborator

@JohanHolman assuming you don't have direct internet connectivity on your machine, do you?

@JohanHolman
Copy link
Author

I don't have internet connectivity on this system. Is that the problem here?

@acchen97
Copy link

@JohanHolman please see below for instructions on offline plugin management.

https://www.elastic.co/guide/en/logstash/current/offline-plugins.html

@JohanHolman
Copy link
Author

This does'n make sense. Everything is there. And yes I followed the instructions to install a offline plugin. It does not work. It depends on something what is installed but couldn't be found. So any serious help will be greatly appreciated.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants