Logstash dying out during startup

(Zama Las) #1

My logstash is dying out during startup

Can see the following in log,....No errors obserbed.

[2017-10-05T14:18:33,230][WARN ][logstash.outputs.elasticsearch] Restored connection to ES instance {:url=>"http://logstash_system:xxxxxx@elasticsearch:9200/"}
[2017-10-05T14:18:33,232][INFO ][logstash.outputs.elasticsearch] New Elasticsearch output {:class=>"LogStash::Outputs::ElasticSearch", :hosts=>["http://elasticsearch:9200"]}
[2017-10-05T14:18:33,233][INFO ][logstash.pipeline ] Starting pipeline {"id"=>".monitoring-logstash", "pipeline.workers"=>1, "pipeline.batch.size"=>2, "pipeline.batch.delay"=>5, "pipeline.max_inflight"=>2}
[2017-10-05T14:18:33,261][INFO ][logstash.licensechecker.licensereader] Elasticsearch pool URLs updated {:changes=>{:removed=>[], :added=>[http://logstash_system:xxxxxx@elasticsearch:9200/]}}
[2017-10-05T14:18:33,262][INFO ][logstash.licensechecker.licensereader] Running health check to see if an Elasticsearch connection is working {:healthcheck_url=>http://logstash_system:xxxxxx@elasticsearch:9200/, :path=>"/"}
[2017-10-05T14:18:33,271][WARN ][logstash.licensechecker.licensereader] Restored connection to ES instance {:url=>"http://logstash_system:xxxxxx@elasticsearch:9200/"}
[2017-10-05T14:18:33,346][INFO ][logstash.pipeline ] Pipeline .monitoring-logstash started
[2017-10-05T14:18:33,401][INFO ][logstash.agent ] Successfully started Logstash API endpoint {:port=>9600}
[2017-10-05T14:18:36,370][WARN ][logstash.agent ] stopping pipeline {:id=>".monitoring-logstash"}

My logstash.conf looks like this

input {
beats {
port => 5044

output {
hosts => ["elasticsearch:9200"]
document_type => "log"
user => elastic
password => changeme
stdout {
codec => rubydebug

(Mark Walkom) #2

How are you starting it?

(Zama Las) #3

I was starting the service using docker . Initially it started successfully with default configuration . I did some changes in config file after which it was not starting up . Identified the config issue and now the service has started successfully. BTW , there was no error message in log file regarding the configuration error .

(system) #4

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.