Issue logstashing to Found - Continued discussion


(Christian Strzadala) #1

Continuing the discussion from Issue logstashing to Found:


(James Tang) #2

Applying an approach from Sherlock Holmes, rule out the possibilities. So if anyone can help with the below questions?

  1. Can logstash and ES on Found be able to handle ipv6 transport? ie receiving logs logstashing into Found?
    https://forums.aws.amazon.com/thread.jspa?messageID=536049. No definitive answers based on the fourm. Last update was recent enough.
  2. How can we rule out that it is an network issue locally? Will using curl be sufficient? Any recommendations as to what kind of test can we performed to rule them out? Especially when the host has both IPV4 and 6 addresses.

Additional information:

  • Switching the configuration to ssl=> false is not working. The same exception is happening.

Failed to flush outgoing items {:outgoing_count=>1, :exception=>"Manticore::ClientProtocolException", :backtrace=>["/volume1/apps/logstash/vendor/bundle/jruby/1.9/gems/manticore-0.4.4-java/lib/manticore/response.rb:35:in `initialize'",
.
.
.
.

regards


(system) #3