# There is huge delay starting up logstash 5.0.0-alpha5

**URL:** <https://discuss.elastic.co/t/there-is-huge-delay-starting-up-logstash-5-0-0-alpha5/59935>\
**Category:** Logstash\
**Created:** [September 7, 2016, 2:46am UTC](https://discuss.elastic.co/t/there-is-huge-delay-starting-up-logstash-5-0-0-alpha5/59935 "2016-09-07T02:46:45Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![madkoala](https://avatars.discourse-cdn.com/v4/letter/m/977dab/32.png) [@madkoala](https://discuss.elastic.co/u/madkoala)\
**Post date:** [September 7, 2016, 2:46am UTC](https://discuss.elastic.co/t/there-is-huge-delay-starting-up-logstash-5-0-0-alpha5/59935/1 "2016-09-07T02:46:45Z")

</div>

We're using Elastic Stack 5.0.0-alpha5.  
We have very big trouble starting up Logstash.

Logstash won't start up after executing (as a service) over 1+ hours.  
Process is alive, but there's no messages or logs even with debug configuration.

Are there anyone know the reasons and workarounds?

Running environment:

> Ubuntu 16.04 LTS with java version 1.8.0\_101  
> ElasticStack 5.0.0-alpha5

---

<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:** [September 7, 2016, 3:10am UTC](https://discuss.elastic.co/t/there-is-huge-delay-starting-up-logstash-5-0-0-alpha5/59935/2 "2016-09-07T03:10:37Z")

</div>

How are you starting it?

---

<div class="post-metadata">

**Author:** ![madkoala](https://avatars.discourse-cdn.com/v4/letter/m/977dab/32.png) [@madkoala](https://discuss.elastic.co/u/madkoala)\
**Post date:** [September 7, 2016, 4:25am UTC](https://discuss.elastic.co/t/there-is-huge-delay-starting-up-logstash-5-0-0-alpha5/59935/3 "2016-09-07T04:25:18Z")

</div>

Starting with "systemctl start logstash.service"

---

<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:** [September 7, 2016, 7:05am UTC](https://discuss.elastic.co/t/there-is-huge-delay-starting-up-logstash-5-0-0-alpha5/59935/4 "2016-09-07T07:05:24Z")

</div>

So how exactly do you know it takes an hour to start?

---

<div class="post-metadata">

**Author:** ![madkoala](https://avatars.discourse-cdn.com/v4/letter/m/977dab/32.png) [@madkoala](https://discuss.elastic.co/u/madkoala)\
**Post date:** [September 7, 2016, 7:54am UTC](https://discuss.elastic.co/t/there-is-huge-delay-starting-up-logstash-5-0-0-alpha5/59935/5 "2016-09-07T07:54:19Z")

</div>

I'm looking into logstash log file with wrong configuration file.

---

<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:** [September 7, 2016, 9:43am UTC](https://discuss.elastic.co/t/there-is-huge-delay-starting-up-logstash-5-0-0-alpha5/59935/6 "2016-09-07T09:43:42Z")

</div>

What does that mean?

---

<div class="post-metadata">

**Author:** ![madkoala](https://avatars.discourse-cdn.com/v4/letter/m/977dab/32.png) [@madkoala](https://discuss.elastic.co/u/madkoala)\
**Post date:** [September 8, 2016, 3:19am UTC](https://discuss.elastic.co/t/there-is-huge-delay-starting-up-logstash-5-0-0-alpha5/59935/7 "2016-09-08T03:19:40Z")

</div>

That means I used wrong configuration file intentionally to check start up delay time.  
Logstash logs error about wrong configuration file.

Also, I tested with logstash 2.4.0 on the same machine, and it worked fine.  
Thanks.

---

<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, 4:39am UTC](https://discuss.elastic.co/t/there-is-huge-delay-starting-up-logstash-5-0-0-alpha5/59935/8 "2017-07-06T04:39:24Z")

</div>