# Unrecognized service

**URL:** <https://discuss.elastic.co/t/unrecognized-service/126231>\
**Category:** Logstash\
**Created:** [March 30, 2018, 1:16pm UTC](https://discuss.elastic.co/t/unrecognized-service/126231 "2018-03-30T13:16:46Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![vinodr](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vinodr/32/28759_2.png) [@vinodr](https://discuss.elastic.co/u/vinodr)\
**Post date:** [March 30, 2018, 3:53pm UTC](https://discuss.elastic.co/t/unrecognized-service/126231/2 "2018-03-30T15:53:58Z")

</div>

> [@Service logstash configtest gone](https://discuss.elastic.co/t/service-logstash-configtest-gone/64488):
>
> In pre 5.0 instances of logstash, after making changes to a config file it was possible to run: service logstash configtest After updating to version 5, this no longer works and returns back: The service command supports only basic LSB actions (start, stop, restart, try-restart, reload, force-reload, status). For other actions, please try to use systemctl. This is on CentOS 7 running logstash 5.0 Does anyone know the new syntax? I searched through the version 5 documentation for "configtest…

---

_[View the full topic](https://discuss.elastic.co/t/unrecognized-service/126231)._
