Alan
August 9, 2016, 12:03pm
1
Hi,
I am having problems setting up logstash with elasticsearch
{:timestamp=>“2016-08-09T13:01:38.941000+0100”, :message=>“localhost:9200 failed to respond”, :class=>“Manticore::ClientProtocolException”, :backtrace=>[“/opt/logstash/vendor/bundle/jruby/1.9/gems/manticore-0.5.5-java/lib/manticore/response.rb:37:in `initialize’”, “org/jruby/RubyProc.java:281:in `call’”, “/opt/logstash/vendor/bundle/jruby/1.9/gems/manticore-0.5.5-java/lib/manticore/response.rb:79:in `call’”, “/opt/logstash/vendor/bundle/jruby/1.9/gems/manticore-0.5.5-java/lib/manticore/response.rb:256:in `call_once’”, “/opt/logstash/vendor/bundle/jruby/1.9/gems/manticore-0.5.5-java/lib/manticore/response.rb:153:in `code’”, “/opt/logstash/vendor/bundle/jruby/1.9/gems/elasticsearch-transport-1.0.15/lib/elasticsearch/transport/transport/http/manticore.rb:71:in `perform_request’”, “org/jruby/RubyProc.java:281:in `call’”, “/opt/logstash/vendor/bundle/jruby/1.9/gems/elasticsearch-transport-1.0.15/lib/elasticsearch/transport/transport/base.rb:201:in `perform_request’”, “/opt/logstash/vendor/bundle/jruby/1.9/gems/elasticsearch-transport-1.0.15/lib/elasticsearch/transport/transport/http/manticore.rb:54:in `perform_request’”, “/opt/logstash/vendor/bundle/jruby/1.9/gems/elasticsearch-transport-1.0.15/lib/elasticsearch/transport/transport/sniffer.rb:32:in `hosts’”, “org/jruby/ext/timeout/Timeout.java:147:in `timeout’”, “/opt/logstash/vendor/bundle/jruby/1.9/gems/elasticsearch-transport-1.0.15/lib/elasticsearch/transport/transport/sniffer.rb:31:in `hosts’”, “/opt/logstash/vendor/bundle/jruby/1.9/gems/elasticsearch-transport-1.0.15/lib/elasticsearch/transport/transport/base.rb:76:in `reload_connections!'”, “/opt/logstash/vendor/bundle/jruby/1.9/gems/logstash-output-elasticsearch-2.5.5-java/lib/logstash/outputs/elasticsearch/http_client.rb:72:in `sniff!'”, “/opt/logstash/vendor/bundle/jruby/1.9/gems/logstash-output-elasticsearch-2.5.5-java/lib/logstash/outputs/elasticsearch/http_client.rb:60:in `start_sniffing!'”, “org/jruby/ext/thread/Mutex.java:149:in `synchronize’”, “/opt/logstash/vendor/bundle/jruby/1.9/gems/logstash-output-elasticsearch-2.5.5-java/lib/logstash/outputs/elasticsearch/http_client.rb:60:in `start_sniffing!'”, “org/jruby/RubyKernel.java:1479:in `loop’”, “/opt/logstash/vendor/bundle/jruby/1.9/gems/logstash-output-elasticsearch-2.5.5-java/lib/logstash/outputs/elasticsearch/http_client.rb:59:in `start_sniffing!'”], :level=>:error}
{:timestamp=>“2016-08-09T13:01:43.593000+0100”, :message=>“localhost:9200 failed to respond”, :class=>“Manticore::ClientProtocolException”, :backtrace=>[“/opt/logstash/vendor/bundle/jruby/1.9/gems/manticore-0.5.5-java/lib/manticore/response.rb:37:in initialize'", "org/jruby/RubyProc.java:281:in call’”, "/opt/logstash/vendor/bundle/jruby/1.9/gems/manticore-0.
need help
Having same issue. Seems like it might be tied to init.d script? chroot or ulimit stuff? Can run ./bin/logstash --verbose just fine. Definitely not an issue with connection with ES on localhost:9200, I can curl to it fine and seg faults even when output stanza does not reference ElasticSearch.
···
On Tuesday, August 9, 2016 at 7:03:11 AM UTC-5, Alan wrote:
Hi,
I am having problems setting up logstash with elasticsearch
{:timestamp=>“2016-08-09T13:01:38.941000+0100”, :message=>“localhost:9200 failed to respond”, :class=>“Manticore::ClientProtocolException”, :backtrace=>[“/opt/logstash/vendor/bundle/jruby/1.9/gems/manticore-0.5.5-java/lib/manticore/response.rb:37:in `initialize’”, “org/jruby/RubyProc.java:281:in `call’”, “/opt/logstash/vendor/bundle/jruby/1.9/gems/manticore-0.5.5-java/lib/manticore/response.rb:79:in `call’”, “/opt/logstash/vendor/bundle/jruby/1.9/gems/manticore-0.5.5-java/lib/manticore/response.rb:256:in `call_once’”, “/opt/logstash/vendor/bundle/jruby/1.9/gems/manticore-0.5.5-java/lib/manticore/response.rb:153:in `code’”, “/opt/logstash/vendor/bundle/jruby/1.9/gems/elasticsearch-transport-1.0.15/lib/elasticsearch/transport/transport/http/manticore.rb:71:in `perform_request’”, “org/jruby/RubyProc.java:281:in `call’”, “/opt/logstash/vendor/bundle/jruby/1.9/gems/elasticsearch-transport-1.0.15/lib/elasticsearch/transport/transport/base.rb:201:in `perform_request’”, “/opt/logstash/vendor/bundle/jruby/1.9/gems/elasticsearch-transport-1.0.15/lib/elasticsearch/transport/transport/http/manticore.rb:54:in `perform_request’”, “/opt/logstash/vendor/bundle/jruby/1.9/gems/elasticsearch-transport-1.0.15/lib/elasticsearch/transport/transport/sniffer.rb:32:in `hosts’”, “org/jruby/ext/timeout/Timeout.java:147:in `timeout’”, “/opt/logstash/vendor/bundle/jruby/1.9/gems/elasticsearch-transport-1.0.15/lib/elasticsearch/transport/transport/sniffer.rb:31:in `hosts’”, “/opt/logstash/vendor/bundle/jruby/1.9/gems/elasticsearch-transport-1.0.15/lib/elasticsearch/transport/transport/base.rb:76:in `reload_connections!'”, “/opt/logstash/vendor/bundle/jruby/1.9/gems/logstash-output-elasticsearch-2.5.5-java/lib/logstash/outputs/elasticsearch/http_client.rb:72:in `sniff!'”, “/opt/logstash/vendor/bundle/jruby/1.9/gems/logstash-output-elasticsearch-2.5.5-java/lib/logstash/outputs/elasticsearch/http_client.rb:60:in `start_sniffing!'”, “org/jruby/ext/thread/Mutex.java:149:in `synchronize’”, “/opt/logstash/vendor/bundle/jruby/1.9/gems/logstash-output-elasticsearch-2.5.5-java/lib/logstash/outputs/elasticsearch/http_client.rb:60:in `start_sniffing!'”, “org/jruby/RubyKernel.java:1479:in `loop’”, “/opt/logstash/vendor/bundle/jruby/1.9/gems/logstash-output-elasticsearch-2.5.5-java/lib/logstash/outputs/elasticsearch/http_client.rb:59:in `start_sniffing!'”], :level=>:error}
{:timestamp=>“2016-08-09T13:01:43.593000+0100”, :message=>“localhost:9200 failed to respond”, :class=>“Manticore::ClientProtocolException”, :backtrace=>[“/opt/logstash/vendor/bundle/jruby/1.9/gems/manticore-0.5.5-java/lib/manticore/response.rb:37:in initialize'", "org/jruby/RubyProc.java:281:in call’”, "/opt/logstash/vendor/bundle/jruby/1.9/gems/manticore-0.
need help
anything of interest in the elasticsearch logfile?
···
On Thursday, 18 August 2016 00:32:56 UTC+2, Thomas Godar wrote:
Having same issue. Seems like it might be tied to init.d script? chroot or ulimit stuff? Can run ./bin/logstash --verbose just fine. Definitely not an issue with connection with ES on localhost:9200, I can curl to it fine and seg faults even when output stanza does not reference ElasticSearch.
On Tuesday, August 9, 2016 at 7:03:11 AM UTC-5, Alan wrote:
Hi,
I am having problems setting up logstash with elasticsearch
{:timestamp=>“2016-08-09T13:01:38.941000+0100”, :message=>“localhost:9200 failed to respond”, :class=>“Manticore::ClientProtocolException”, :backtrace=>[“/opt/logstash/vendor/bundle/jruby/1.9/gems/manticore-0.5.5-java/lib/manticore/response.rb:37:in `initialize’”, “org/jruby/RubyProc.java:281:in `call’”, “/opt/logstash/vendor/bundle/jruby/1.9/gems/manticore-0.5.5-java/lib/manticore/response.rb:79:in `call’”, “/opt/logstash/vendor/bundle/jruby/1.9/gems/manticore-0.5.5-java/lib/manticore/response.rb:256:in `call_once’”, “/opt/logstash/vendor/bundle/jruby/1.9/gems/manticore-0.5.5-java/lib/manticore/response.rb:153:in `code’”, “/opt/logstash/vendor/bundle/jruby/1.9/gems/elasticsearch-transport-1.0.15/lib/elasticsearch/transport/transport/http/manticore.rb:71:in `perform_request’”, “org/jruby/RubyProc.java:281:in `call’”, “/opt/logstash/vendor/bundle/jruby/1.9/gems/elasticsearch-transport-1.0.15/lib/elasticsearch/transport/transport/base.rb:201:in `perform_request’”, “/opt/logstash/vendor/bundle/jruby/1.9/gems/elasticsearch-transport-1.0.15/lib/elasticsearch/transport/transport/http/manticore.rb:54:in `perform_request’”, “/opt/logstash/vendor/bundle/jruby/1.9/gems/elasticsearch-transport-1.0.15/lib/elasticsearch/transport/transport/sniffer.rb:32:in `hosts’”, “org/jruby/ext/timeout/Timeout.java:147:in `timeout’”, “/opt/logstash/vendor/bundle/jruby/1.9/gems/elasticsearch-transport-1.0.15/lib/elasticsearch/transport/transport/sniffer.rb:31:in `hosts’”, “/opt/logstash/vendor/bundle/jruby/1.9/gems/elasticsearch-transport-1.0.15/lib/elasticsearch/transport/transport/base.rb:76:in `reload_connections!'”, “/opt/logstash/vendor/bundle/jruby/1.9/gems/logstash-output-elasticsearch-2.5.5-java/lib/logstash/outputs/elasticsearch/http_client.rb:72:in `sniff!'”, “/opt/logstash/vendor/bundle/jruby/1.9/gems/logstash-output-elasticsearch-2.5.5-java/lib/logstash/outputs/elasticsearch/http_client.rb:60:in `start_sniffing!'”, “org/jruby/ext/thread/Mutex.java:149:in `synchronize’”, “/opt/logstash/vendor/bundle/jruby/1.9/gems/logstash-output-elasticsearch-2.5.5-java/lib/logstash/outputs/elasticsearch/http_client.rb:60:in `start_sniffing!'”, “org/jruby/RubyKernel.java:1479:in `loop’”, “/opt/logstash/vendor/bundle/jruby/1.9/gems/logstash-output-elasticsearch-2.5.5-java/lib/logstash/outputs/elasticsearch/http_client.rb:59:in `start_sniffing!'”], :level=>:error}
{:timestamp=>“2016-08-09T13:01:43.593000+0100”, :message=>“localhost:9200 failed to respond”, :class=>“Manticore::ClientProtocolException”, :backtrace=>[“/opt/logstash/vendor/bundle/jruby/1.9/gems/manticore-0.5.5-java/lib/manticore/response.rb:37:in initialize'", "org/jruby/RubyProc.java:281:in call’”, "/opt/logstash/vendor/bundle/jruby/1.9/gems/manticore-0.
need help
Nothing. I tried a few installs on fresh centos 6 instances and finally managed to get it to work as expected. Really no clue as to why. Think the post install scripts perhaps are goofed up? Yum seemed to think things went fine on each install but I ended up with no files in /etc/logstash/conf.d and folder permissions were not set correctly - go figure the time I got things working was when the install seemed to have not completed fully. First attempt was an upgrade to an old logstash setup that brought me here. Can saw that yum install, yum remove, yum install does not get you to where you were after first install. Sorry not very constructive or helpful I know but I’ve had to move on. I’ll open a ticket at Elastic if I ever have anything useful to really contribute for whatever this issue was.
···
On Friday, August 19, 2016 at 5:11:18 AM UTC-5, in...@search-guard.com wrote:
anything of interest in the elasticsearch logfile?
On Thursday, 18 August 2016 00:32:56 UTC+2, Thomas Godar wrote:
Having same issue. Seems like it might be tied to init.d script? chroot or ulimit stuff? Can run ./bin/logstash --verbose just fine. Definitely not an issue with connection with ES on localhost:9200, I can curl to it fine and seg faults even when output stanza does not reference ElasticSearch.
On Tuesday, August 9, 2016 at 7:03:11 AM UTC-5, Alan wrote:
Hi,
I am having problems setting up logstash with elasticsearch
{:timestamp=>“2016-08-09T13:01:38.941000+0100”, :message=>“localhost:9200 failed to respond”, :class=>“Manticore::ClientProtocolException”, :backtrace=>[“/opt/logstash/vendor/bundle/jruby/1.9/gems/manticore-0.5.5-java/lib/manticore/response.rb:37:in `initialize’”, “org/jruby/RubyProc.java:281:in `call’”, “/opt/logstash/vendor/bundle/jruby/1.9/gems/manticore-0.5.5-java/lib/manticore/response.rb:79:in `call’”, “/opt/logstash/vendor/bundle/jruby/1.9/gems/manticore-0.5.5-java/lib/manticore/response.rb:256:in `call_once’”, “/opt/logstash/vendor/bundle/jruby/1.9/gems/manticore-0.5.5-java/lib/manticore/response.rb:153:in `code’”, “/opt/logstash/vendor/bundle/jruby/1.9/gems/elasticsearch-transport-1.0.15/lib/elasticsearch/transport/transport/http/manticore.rb:71:in `perform_request’”, “org/jruby/RubyProc.java:281:in `call’”, “/opt/logstash/vendor/bundle/jruby/1.9/gems/elasticsearch-transport-1.0.15/lib/elasticsearch/transport/transport/base.rb:201:in `perform_request’”, “/opt/logstash/vendor/bundle/jruby/1.9/gems/elasticsearch-transport-1.0.15/lib/elasticsearch/transport/transport/http/manticore.rb:54:in `perform_request’”, “/opt/logstash/vendor/bundle/jruby/1.9/gems/elasticsearch-transport-1.0.15/lib/elasticsearch/transport/transport/sniffer.rb:32:in `hosts’”, “org/jruby/ext/timeout/Timeout.java:147:in `timeout’”, “/opt/logstash/vendor/bundle/jruby/1.9/gems/elasticsearch-transport-1.0.15/lib/elasticsearch/transport/transport/sniffer.rb:31:in `hosts’”, “/opt/logstash/vendor/bundle/jruby/1.9/gems/elasticsearch-transport-1.0.15/lib/elasticsearch/transport/transport/base.rb:76:in `reload_connections!'”, “/opt/logstash/vendor/bundle/jruby/1.9/gems/logstash-output-elasticsearch-2.5.5-java/lib/logstash/outputs/elasticsearch/http_client.rb:72:in `sniff!'”, “/opt/logstash/vendor/bundle/jruby/1.9/gems/logstash-output-elasticsearch-2.5.5-java/lib/logstash/outputs/elasticsearch/http_client.rb:60:in `start_sniffing!'”, “org/jruby/ext/thread/Mutex.java:149:in `synchronize’”, “/opt/logstash/vendor/bundle/jruby/1.9/gems/logstash-output-elasticsearch-2.5.5-java/lib/logstash/outputs/elasticsearch/http_client.rb:60:in `start_sniffing!'”, “org/jruby/RubyKernel.java:1479:in `loop’”, “/opt/logstash/vendor/bundle/jruby/1.9/gems/logstash-output-elasticsearch-2.5.5-java/lib/logstash/outputs/elasticsearch/http_client.rb:59:in `start_sniffing!'”], :level=>:error}
{:timestamp=>“2016-08-09T13:01:43.593000+0100”, :message=>“localhost:9200 failed to respond”, :class=>“Manticore::ClientProtocolException”, :backtrace=>[“/opt/logstash/vendor/bundle/jruby/1.9/gems/manticore-0.5.5-java/lib/manticore/response.rb:37:in initialize'", "org/jruby/RubyProc.java:281:in call’”, "/opt/logstash/vendor/bundle/jruby/1.9/gems/manticore-0.
need help