# Logstash service Centos

**URL:** <https://discuss.elastic.co/t/logstash-service-centos/120903>\
**Category:** Logstash\
**Created:** [February 21, 2018, 5:22pm UTC](https://discuss.elastic.co/t/logstash-service-centos/120903 "2018-02-21T17:22:43Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![QuizzyRascal](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/quizzyrascal/32/27900_2.png) [@QuizzyRascal](https://discuss.elastic.co/u/QuizzyRascal)\
**Post date:** [February 21, 2018, 5:22pm UTC](https://discuss.elastic.co/t/logstash-service-centos/120903/1 "2018-02-21T17:22:44Z")

</div>

Is there anyway to get debug information when starting a logstash service through

sudo systemctl start logstash

My listener isn't starting and so my service runs without the listener- I want to try and get the information needed to sort the issue out.

It runs fine and loads the listener perfectly from the command line.

Any tips anyone?

Thanks  
QR

---

<div class="post-metadata">

**Author:** ![QuizzyRascal](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/quizzyrascal/32/27900_2.png) [@QuizzyRascal](https://discuss.elastic.co/u/QuizzyRascal)\
**Post date:** [February 26, 2018, 5:10pm UTC](https://discuss.elastic.co/t/logstash-service-centos/120903/2 "2018-02-26T17:10:20Z")

</div>

Solved!  
The issue appears to be a combination of things:

1. The build of CentOS 7 I have been given has noexec on /tmp which was an issue that stopped command line execution of logstash.
2. The permissions around /etc/logstash and /etc/logstash.conf.d

These were set to root only, which might be fine for others but for me was a bad do.

I executed the following command:

setfacl -Rm d:u:logstash:rwX,u:logstash:rwX /etc/logstash

Which set rw on the directory and conf.d

Before when I was running Verbose from the command line I was getting a warning that the service could not find logstash.yml but it would start using a default.  
When starting from SystemCtl the service would start but not listen

So after the line above I rebooted and made sure the logstash service was running and did a netstat -ntl

And to my delight discovered that logstash was now listening on port 5000 as hoped and that the listener persisted.

So at the moment this is a solved issue. I hope this helps someone else

---

<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:** [March 26, 2018, 5:10pm UTC](https://discuss.elastic.co/t/logstash-service-centos/120903/3 "2018-03-26T17:10:24Z")

</div>

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