-
Notifications
You must be signed in to change notification settings - Fork 63
"uninitialized constant JBUNDLER_CLASSPATH" error while running logstash #35
Comments
What os are you running this on? How was logstash built, ie using the make
|
I built logstash by running "make tarball" and my OS is CentOS 6. |
Okay this may be a bug introduced with the latest jruby kafka.
|
is there any workaround? or are you going to fix this anytime soon? Appreciate your help! |
I worked around this (note: not a ruby/jruby/kafka expert by any means) by commenting out the if clause at the top of: e.g.: |
I got some problem. |
Revert to 0.1.0, as @zhaoxuan suggested, while building for now. I'll try to fix soon. |
Hey guys I pushed a version 0.1.2 that I think fixes the problem. Could you give it a shot? |
Thanks Joe. Its working now!! I am closing this issue now. |
Hi,
I am newbie to most of the stuff like logstash, kafka. I have a kafka server running and have my logs pushed in to kafka but when I try to bin/logstash agent -f logstash.conf --debug I get the following error:
The error reported is:
uninitialized constant JBUNDLER_CLASSPATH
org/jruby/RubyModule.java:2690:in
const_missing' /root/logstash-kafka/build/tarball/logstash-1.4.2/vendor/bundle/jruby/1.9/gems/jruby-kafka-0.1.1-java/lib/jruby-kafka.rb:8:in
(root)'org/jruby/RubyKernel.java:1085:in
require' file:/root/logstash-kafka/build/tarball/logstash-1.4.2/vendor/jar/jruby-complete-1.7.11.jar!/META-INF/jruby.home/lib/ruby/shared/rubygems/core_ext/kernel_require.rb:135:in
require'file:/root/logstash-kafka/build/tarball/logstash-1.4.2/vendor/jar/jruby-complete-1.7.11.jar!/META-INF/jruby.home/lib/ruby/shared/rubygems/core_ext/kernel_require.rb:133:in
require' file:/root/logstash-kafka/build/tarball/logstash-1.4.2/vendor/jar/jruby-complete-1.7.11.jar!/META-INF/jruby.home/lib/ruby/shared/rubygems/core_ext/kernel_require.rb:124:in
require'/root/logstash-kafka/build/tarball/logstash-1.4.2/vendor/bundle/jruby/1.9/gems/polyglot-0.3.4/lib/polyglot.rb:65:in
require' /root/logstash-kafka/build/tarball/logstash-1.4.2/lib/logstash/inputs/kafka.rb:1:in
(root)'/root/logstash-kafka/build/tarball/logstash-1.4.2/lib/logstash/inputs/kafka.rb:31:in
register' org/jruby/RubyArray.java:1613:in
each'/root/logstash-kafka/build/tarball/logstash-1.4.2/lib/logstash/pipeline.rb:135:in
start_inputs' /root/logstash-kafka/build/tarball/logstash-1.4.2/lib/logstash/pipeline.rb:134:in
start_inputs'/root/logstash-kafka/build/tarball/logstash-1.4.2/lib/logstash/pipeline.rb:72:in
run' /root/logstash-kafka/build/tarball/logstash-1.4.2/lib/logstash/runner.rb:168:in
run'org/jruby/RubyProc.java:271:in
call' /root/logstash-kafka/build/tarball/logstash-1.4.2/lib/logstash/agent.rb:139:in
execute'I have kept the setup to a bare minimum with just one kafka broker. Here is my config file:
input {
kafka {
zk_connect => "localhost:2181"
group_id => "logs"
topic_id => "logstash"
reset_beginning => false
consumer_threads => 1
consumer_restart_on_error => true
consumer_restart_sleep_ms => 100
decorate_events => true
}
}
output {
kafka {
broker_list => "localhost:9092"
topic_id => "logstash"
compression_codec => "snappy"
request_required_acks => 1
codec => plain {
format => "%{message}"
}
}
}
The text was updated successfully, but these errors were encountered: