# Logstash shutdown completed

**URL:** <https://discuss.elastic.co/t/logstash-shutdown-completed/45809>\
**Category:** Logstash\
**Created:** [March 30, 2016, 2:39pm UTC](https://discuss.elastic.co/t/logstash-shutdown-completed/45809 "2016-03-30T14:39:47Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![JoaquinS](https://avatars.discourse-cdn.com/v4/letter/j/f07891/32.png) [@JoaquinS](https://discuss.elastic.co/u/JoaquinS)\
**Post date:** [March 30, 2016, 2:39pm UTC](https://discuss.elastic.co/t/logstash-shutdown-completed/45809/1 "2016-03-30T14:39:47Z")

</div>

Hello,  
What it means that if I'm consuming from an index of ES (that has always incoming data) Logstash says : "Logstash shutdown completed"?.

My input config is this:

input {  
elasticsearch {  
hosts =\> "192.168.70.109:9200"  
index =\> "itau-monitoreo\*"  
size =\> 500  
scroll =\> "5m"  
docinfo =\> "true"  
}  
}

Regards,

---

<div class="post-metadata">

**Author:** ![magnusbaeck](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/magnusbaeck/32/44943_2.png) [@magnusbaeck](https://discuss.elastic.co/u/magnusbaeck)\
**Post date:** [March 30, 2016, 8:09pm UTC](https://discuss.elastic.co/t/logstash-shutdown-completed/45809/2 "2016-03-30T20:09:43Z")

</div>

I don't think that input plugin is ever supposed to be shutting down ES. Do you have any other inputs that could trigger this? What else is in the log prior to the message in question?

---

<div class="post-metadata">

**Author:** ![JoaquinS](https://avatars.discourse-cdn.com/v4/letter/j/f07891/32.png) [@JoaquinS](https://discuss.elastic.co/u/JoaquinS)\
**Post date:** [March 30, 2016, 8:29pm UTC](https://discuss.elastic.co/t/logstash-shutdown-completed/45809/3 "2016-03-30T20:29:49Z")

</div>

I'm running 17 logstash conf files, each one reads from 1 different index. Some of them gets shut down and others don't.  
`Logstash startup completed Logstash shutdown completed`  
I'm using this command to run Logstash:

`sudo -H -u logstash -c '/opt/logstash/bin/logstash -f /etc/logstash/conf.d/es-import-data[1-17].conf'`

---

<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:** [March 30, 2016, 9:36pm UTC](https://discuss.elastic.co/t/logstash-shutdown-completed/45809/4 "2016-03-30T21:36:57Z")

</div>

Take a look at [https://www.elastic.co/guide/en/elasticsearch/reference/2.3/search-request-scroll.html](https://www.elastic.co/guide/en/elasticsearch/reference/2.3/search-request-scroll.html)

But when you use that it doesn't take into account new data, only data that exists in the index at the time you run LS (and it connects to ES).

---

<div class="post-metadata">

**Author:** ![JoaquinS](https://avatars.discourse-cdn.com/v4/letter/j/f07891/32.png) [@JoaquinS](https://discuss.elastic.co/u/JoaquinS)\
**Post date:** [March 30, 2016, 11:16pm UTC](https://discuss.elastic.co/t/logstash-shutdown-completed/45809/5 "2016-03-30T23:16:50Z")

</div>

And, how can I do a streaming index data extractor using LS?

---

<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:** [March 31, 2016, 1:43am UTC](https://discuss.elastic.co/t/logstash-shutdown-completed/45809/6 "2016-03-31T01:43:39Z")

</div>

You can't as we don't yet have a changes type API in ES.

---

<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:** [July 6, 2017, 5:04am UTC](https://discuss.elastic.co/t/logstash-shutdown-completed/45809/7 "2017-07-06T05:04:38Z")

</div>