# Logstash does not start main pipeline and produces no output on Ubuntu 16.04

**URL:** <https://discuss.elastic.co/t/logstash-does-not-start-main-pipeline-and-produces-no-output-on-ubuntu-16-04/79650>\
**Category:** Logstash\
**Created:** [March 22, 2017, 9:12pm UTC](https://discuss.elastic.co/t/logstash-does-not-start-main-pipeline-and-produces-no-output-on-ubuntu-16-04/79650 "2017-03-22T21:12:02Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![esbenp](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/esbenp/32/16116_2.png) [@esbenp](https://discuss.elastic.co/u/esbenp)\
**Post date:** [March 22, 2017, 9:12pm UTC](https://discuss.elastic.co/t/logstash-does-not-start-main-pipeline-and-produces-no-output-on-ubuntu-16-04/79650/1 "2017-03-22T21:12:02Z")

</div>

I have installed Logstash and Elasticsearch on an Ubuntu 16.04 machine with 4 gb ram using `apt-get install logstash`.

When I boot the service with `systemctl start logstash` it does start the process (I can see it using `ps aux | grep logstash`) but no index is created in Elasticsearch. I thought I would try to debug it by just running the process in the terminal but when I do it creates no output.

This is the command I run:

```auto
sudo -u logstash /usr/share/logstash/bin/logstash \
 --path.settings /etc/logstash \
 -f /etc/logstash/conf.d/std.conf \
 --config.test_and_exit \
 --log.level debug

```

Nothing ever happens - it produces no output. It does not tell me that the main pipeline has started or gives me an error or anything.

I have checked `/var/log/logstash` put the folder is empty. I have checked `syslog` but there are only a few entries from when it was running as a service (only entries like `Mar 22 20:11:21 elasticsearch-logstash systemd[1]: Started logstash.`)

I installed logstash as root and I have tried `chown -R logstash:adm` both `/usr/share/logstash/`, `var/log/logstash` and `/etc/logstash` but nothing works.

I only have a single configuration file `/etc/logstash/conf.d/main.conf` and I have tried several pipeline configurations but same result:

**main.conf (version 1)**

```auto
input { 
  stdin {

  } 
} 
output {
  stdout {
    
  } 
}

```

**main.conf (version 2)**

```auto
input {
  stdin {
  }
}
output {
 file {
   path => "/var/log/logstash/yo.log"
 }
}

```

**main.conf (version 3)**

```auto
input { 
  stdin {

  } 
} 
output {
  stdout { codec => rubydebug }
}

```

None of these configurations change the outcome in anyway. I have no idea why it is silently failing on me.

It should be noted that I have also tried installing by downloading the tar file and running Logstash from the downloaded directory with same result.

Any ideas?

---

<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 23, 2017, 2:42am UTC](https://discuss.elastic.co/t/logstash-does-not-start-main-pipeline-and-produces-no-output-on-ubuntu-16-04/79650/2 "2017-03-23T02:42:13Z")

</div>

Its likely waiting for input into stdin, have you tried passing something in?

---

<div class="post-metadata">

**Author:** ![dfinn](https://avatars.discourse-cdn.com/v4/letter/d/8c91f0/32.png) [@dfinn](https://discuss.elastic.co/u/dfinn)\
**Post date:** [March 23, 2017, 4:14am UTC](https://discuss.elastic.co/t/logstash-does-not-start-main-pipeline-and-produces-no-output-on-ubuntu-16-04/79650/3 "2017-03-23T04:14:27Z")

</div>

It also doesn't look like you've told it to output to Elasticsearch. I don't think it does this by default but maybe I'm wrong.

Here's my output section:

```
output {
  elasticsearch {
    hosts => "localhost:9200"
  }
  stdout { codec => rubydebug }
}
```

---

<div class="post-metadata">

**Author:** ![esbenp](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/esbenp/32/16116_2.png) [@esbenp](https://discuss.elastic.co/u/esbenp)\
**Post date:** [March 23, 2017, 5:41am UTC](https://discuss.elastic.co/t/logstash-does-not-start-main-pipeline-and-produces-no-output-on-ubuntu-16-04/79650/4 "2017-03-23T05:41:42Z")

</div>

Turns out it was the lack of entropy problem.

The issue: [https://github.com/elastic/logstash/issues/5491](https://github.com/elastic/logstash/issues/5491)  
The solution: [https://www.digitalocean.com/community/tutorials/how-to-setup-additional-entropy-for-cloud-servers-using-haveged](https://www.digitalocean.com/community/tutorials/how-to-setup-additional-entropy-for-cloud-servers-using-haveged)

---

<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:** [April 20, 2017, 5:42am UTC](https://discuss.elastic.co/t/logstash-does-not-start-main-pipeline-and-produces-no-output-on-ubuntu-16-04/79650/5 "2017-04-20T05:42:03Z")

</div>

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