dsolsona
commented
9 years ago Hi,
Is there any update on this?
Open suyograo opened 9 years ago
dsolsona
commented
9 years ago Hi,
Is there any update on this?
dsolsona
commented
9 years ago Adding more information based on feedback I got from https://github.com/elastic/logstash/issues/3559
I can easily reproduce this issue with 1.5.2-1 and two easy configuration files.
Start one logstash instance with the following configuration
input {
lumberjack {
codec => json {}
port => "5001"
ssl_certificate => "/opt/logstash/ssl/cert.crt"
ssl_key => "/opt/logstash/ssl/cert.key"
}
}
output { stdout { codec => rubydebug} }Then start another logstash process with this config
input {
generator {
lines => "127.0.0.1 127.0.0.1 - - [10/Aug/2015:07:26:32 -0500] GET /_fpm_status?json HTTP/1.1 200 317 - collectd/5.4.0 0.000"
count => 100
}
}
output {
lumberjack {
codec => json { }
hosts => "127.0.0.1"
port => "5001"
ssl_certificate => "/opt/logstash/ssl/cert.crt"
workers => 2
}
}This consistently throws the error I posted before. The same configuration without the workers => 2 works fine.
dsolsona
commented
9 years ago This is also happening with logstash 1.5.3-1 as well.
dsolsona
commented
9 years ago Any update on this? It's been more three months with no updates whatsoever :(
Kvrepo
commented
5 years ago I would like to bump this issue. I get the same error in the logs. I'm following the instructions written here: https://www.elastic.co/guide/en/logstash/6.7/ls-to-ls.html
#Input pipeline:
/usr/share/logstash/bin/logstash -e 'input{stdin{}}output{ lumberjack { codec => json ssl_certificate => "lumberjack.cert" port => 5001 hosts => "localhost" } }'
#Output pipeline
/usr/share/logstash/bin/logstash -e 'input { beats { codec => json port => 5001 ssl => true ssl_certificate => "lumberjack.cert" ssl_key => "lumberjack.key"} }output{stdout{}}'The first few messages gets through swiftly, then the next few gets halted. Then the error mentioned above appears in the logs and suddenly all halted messages gets to the other side.
from @dsolsona, https://github.com/elastic/logstash/issues/3559
Hi,
I'm seeing this error with the lumberjack output plugin and logstash 1.5.2
My output config is quite simple as you can see
I can't see any error on the other logstash server running the lumberjack input and this only appears to happen with logstash 1.5
There's one thing I've noticed and it's that the error goes away when you run the output with a single worker instead of 10. But I need the extra workers, otherwise the output becomes a bottleneck.