# Logstash not a service on Amazon AMI :(

**URL:** <https://discuss.elastic.co/t/logstash-not-a-service-on-amazon-ami/64483>\
**Category:** Logstash\
**Created:** [October 31, 2016, 7:03pm UTC](https://discuss.elastic.co/t/logstash-not-a-service-on-amazon-ami/64483 "2016-10-31T19:03:22Z")\
**Posts on this page:** 1\
**Showing post:** 14

<div class="post-metadata">

**Author:** ![pjmorr](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/pjmorr/32/12996_2.png) [@pjmorr](https://discuss.elastic.co/u/pjmorr)\
**Post date:** [November 8, 2016, 11:55pm UTC](https://discuss.elastic.co/t/logstash-not-a-service-on-amazon-ami/64483/14 "2016-11-08T23:55:43Z")

</div>

All I am pointing out is that based on the documentation I see, and the output of the installation process, the expected behavior of Logstash is different than any of the other ELK stack services.

**Amazon Linux AMI release 2016.09**

> sudo yum list installed | grep elastic  
> elasticsearch.noarch 5.0.0-1 @elasticsearch-5.x  
> filebeat.x86\_64 5.0.0-1 @elastic-5.x  
> kibana.x86\_64 5.0.0-1 @elastic-5.x  
> logstash.noarch 1:5.0.0-1 @elastic-5.x  
> metricbeat.x86\_64 5.0.0-1 @elastic-5.x  
> packetbeat.x86\_64 5.0.0-1 @elastic-5.x

Not sure if the 1:5.0.0-1 is significant vs. all the other components, but it is all from repo installs...  
With these all at the same version I receive the following results on same system:

**Elasticsearch**

> $ sudo service elasticsearch status  
> _elasticsearch (pid 18607) is running..._  
> $ sudo initctl status elasticsearch  
> _initctl: Unknown job: elasticsearch_

**Kibana**

> $sudo service kibana status  
> _kibana is running_  
> $ sudo initctl status kibana  
> _initctl: Unknown job: kibana_

**Packetbeat**

> $ sudo service packetbeat status  
> _packetbeat-god (pid 3699) is running..._  
> $ sudo initctl status packetbeat  
> _initctl: Unknown job: packetbeat_

**Metricbeat**

> $ sudo service metricbeat status  
> _metricbeat-god (pid 24120) is running..._  
> $ sudo initctl status metricbeat  
> _initctl: Unknown job: metricbeat_

**Filebeat**

> $ service filebeat status  
> _filebeat-god (pid 3571) is running..._  
> $ sudo initctl status filebeat  
> _initctl: Unknown job: filebeat_

**Logstash**

> $ service logstash status  
> _logstash: unrecognized service_  
> $ sudo initctl status logstash  
> _logstash stop/waiting_

I am aware of the various ways to start a linux process, I am just pointing out that logstash is the _only_ component which does not conform to the others. I am fine with whatever process, just saying that the phrase _"one of these things does not belong, one of these things is not like the other..."_ comes to mind.

Managing server farms is difficult when a known good process, which has worked in previous versions, and works in all companion processes, does not follow the same guidelines.

My two cents. Sorry for the quasi rant.

---

_[View the full topic](https://discuss.elastic.co/t/logstash-not-a-service-on-amazon-ami/64483)._