# Logstash dying out during startup

**URL:** <https://discuss.elastic.co/t/logstash-dying-out-during-startup/102850>\
**Category:** Logstash\
**Created:** [October 5, 2017, 2:25pm UTC](https://discuss.elastic.co/t/logstash-dying-out-during-startup/102850 "2017-10-05T14:25:29Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Zama\_Las](https://avatars.discourse-cdn.com/v4/letter/z/bb73d2/32.png) [@Zama\_Las](https://discuss.elastic.co/u/Zama_Las)\
**Post date:** [October 5, 2017, 2:25pm UTC](https://discuss.elastic.co/t/logstash-dying-out-during-startup/102850/1 "2017-10-05T14:25:29Z")

</div>

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/](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](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/](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/](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/](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  
}  
}

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [October 6, 2017, 1:34am UTC](https://discuss.elastic.co/t/logstash-dying-out-during-startup/102850/2 "2017-10-06T01:34:20Z")

</div>

How are you starting it?

---

<div class="post-metadata">

**Author:** ![Zama\_Las](https://avatars.discourse-cdn.com/v4/letter/z/bb73d2/32.png) [@Zama\_Las](https://discuss.elastic.co/u/Zama_Las)\
**Post date:** [October 6, 2017, 6:05am UTC](https://discuss.elastic.co/t/logstash-dying-out-during-startup/102850/3 "2017-10-06T06:05:28Z")

</div>

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 .

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [November 3, 2017, 6:05am UTC](https://discuss.elastic.co/t/logstash-dying-out-during-startup/102850/4 "2017-11-03T06:05:39Z")

</div>

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