-
Notifications
You must be signed in to change notification settings - Fork 76
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
Problems loading a plugin with :type=>"output", :name=>"kafka" after a build #175
Comments
@devopsberlin before building the gem, you will need to vendor the jar dependencies; this will ensure that they get packaged within the
|
@yaauie Thanks! |
@yaauie, when running the command
|
@devopsberlin it appears that one of the dependencies isn't on your loadpath; do you have the gem's dependencies installed? From the looks of it, the This project, like most Ruby projects, uses command -v bundle || gem install bundler Once bundle install Once the bundle is installed, the following should vendor the jar dependencies: rake vendor Once the jar dependencies are vendored, the gem can be built: gem build logstash-output-kafka.gemspec |
@devopsberlin since the jar dependencies are loaded using jruby, you'll also need to be using jruby 9.1.x, with |
@yaauie, thank you for your clear and helpful explanation, it works. If you don't mind me asking one more question, I am using
https://www.elastic.co/guide/en/logstash/5.6/plugins-outputs-kafka.html Is there a way to force logstash to exit / kill the process in this case, this way a new logstash container will be relaunch with the new brokers ids and the service will start properly. So right now I have two solutions for this, first is to restart the service which is running the logstash containers each time I change the kafka nodes, or to make some changes in the plugin to kill the process when catching an error message, but I wonder maybe do you have a better soultion ? Thanks again for all your help!
Thanks |
@devopsberlin I’m not sure how to answer your second question, but see that you’ve already filed it as elastic/logstash#8996 — I’ll flag this with the Logstash team tomorrow and try to get an answer/fix prioritised. |
Closing — original issue addressed; secondary issue filed elsewhere |
I am getting below error after build and install my plugin, using
docker.elastic.co/logstash/logstash-oss:6.0.0
.Made my changes and then build:
Remove old plugin and install the new one:
Error:
Please could you kindly suggest how to fix this issue.
Thanks.
The text was updated successfully, but these errors were encountered: