-
Notifications
You must be signed in to change notification settings - Fork 22
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
NoMethodError thrown in logstash/pipeline.rb using couchdb_changes on Alpha 5 #36
Comments
I'm still seeing this issue when I install using docker. Here's the debug output there:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This problem seems to be stemming from /logstash-input-couchdb_changes-3.0.2/lib/logstash/inputs/couchdb_changes.rb:144
input { couchdb_changes { db => "nt-jpad" } } output { file { path => "/home/jared/testing.txt" } }
{ "_id": "user-", "_rev": "1-d6788b98a9066b0ac439994807ed310a", "type": "user", "username": null, "created": 1467227196, "domains": { "chrome": { "created": 1467227196 } } }
For Ubuntu 16.04
{:timestamp=>"2016-08-18T17:25:07.107000-0600",
:message=>"A plugin had an unrecoverable error. Will restart this plugin.
Plugin: <LogStash::Inputs::CouchDBChanges db=>"nt-jpad",
enable_metric=>true,
codec=><LogStash::Codecs::Plain enable_metric=>true,
charset=>"UTF-8">,
host=>"localhost",
port=>5984,
secure=>false,
password=>,
heartbeat=>1000,
keep_revision=>false,
ignore_attachments=>true,
always_reconnect=>true,
reconnect_delay=>10>
Error: undefined method [] for 2016-08-18T23:25:07.096Z %{host} %{message}:LogStash::Event
Exception: NoMethodError
Stack: /usr/share/logstash/vendor/bundle/jruby/1.9/gems/logstash-input-couchdb_changes-3.0.2/lib/logstash/inputs/couchdb_changes.rb:167:in
run' org/jruby/RubyArray.java:1613:in
each'/usr/share/logstash/vendor/bundle/jruby/1.9/gems/logstash-input-couchdb_changes-3.0.2/lib/logstash/inputs/couchdb_changes.rb:154:in
run' /usr/share/logstash/vendor/jruby/lib/ruby/1.9/net/protocol.rb:395:in
call_block'/usr/share/logstash/vendor/jruby/lib/ruby/1.9/net/protocol.rb:386:in
<<' /usr/share/logstash/vendor/jruby/lib/ruby/1.9/net/protocol.rb:94:in
read'/usr/share/logstash/vendor/jruby/lib/ruby/1.9/net/http.rb:2785:in
read_chunked' /usr/share/logstash/vendor/jruby/lib/ruby/1.9/net/http.rb:2759:in
read_body_0'/usr/share/logstash/vendor/jruby/lib/ruby/1.9/net/http.rb:2719:in
read_body' /usr/share/logstash/vendor/bundle/jruby/1.9/gems/logstash-input-couchdb_changes-3.0.2/lib/logstash/inputs/couchdb_changes.rb:153:in
run'/usr/share/logstash/vendor/jruby/lib/ruby/1.9/net/http.rb:1331:in
transport_request' /usr/share/logstash/vendor/jruby/lib/ruby/1.9/net/http.rb:2680:in
reading_body'/usr/share/logstash/vendor/jruby/lib/ruby/1.9/net/http.rb:1330:in
transport_request' org/jruby/RubyKernel.java:1242:in
catch'/usr/share/logstash/vendor/jruby/lib/ruby/1.9/net/http.rb:1325:in
transport_request' /usr/share/logstash/vendor/jruby/lib/ruby/1.9/net/http.rb:1302:in
request'/usr/share/logstash/vendor/bundle/jruby/1.9/gems/logstash-input-couchdb_changes-3.0.2/lib/logstash/inputs/couchdb_changes.rb:148:in
run' /usr/share/logstash/vendor/jruby/lib/ruby/1.9/net/http.rb:746:in
start'/usr/share/logstash/vendor/jruby/lib/ruby/1.9/net/http.rb:557:in 'start'
/usr/share/logstash/vendor/bundle/jruby/1.9/gems/logstash-input-couchdb_changes-3.0.2/lib/logstash/inputs/couchdb_changes.rb:144:in run'
/usr/share/logstash/logstash-core/lib/logstash/pipeline.rb:323:in
inputworker' /usr/share/logstash/logstash-core/lib/logstash/pipeline.rb:317:in
start_input'",:level=>:error,
:file=>"logstash/pipeline.rb",
:line=>"334",
:method=>"inputworker"}`
The text was updated successfully, but these errors were encountered: