We are running logstash version 5.5.0 on a RHEL 6.10 fully patched host.
Oddly when I deploy the ELK stack all the other applications get init scripts put in /etc/init.d however logstash seems to put it's script in /usr/share/logstash/bin.
This has made automation via puppet difficult.
The online Elasticsearch documentation found hereseems to suggest that for a RHEL 6.10 system using /sbin/init to start/stop the process you would use /etc/init.d/logstash stop/start/status etc (service logstash command).
However this is where it gets weird, on my system logstash is responding to initctl commands which as far as I know are not used by RHEL 6.10.
When I tried to automate the deployment of logstash via puppet I get a message that upstart is not a provider on this host!! And yet the upstart commands work on the cmd-line.
I have built my own init script to set the boot level for the service as well as control it via /sbin/init which in turn has enabled me to automate the process via puppet.
However why is the installation of logstash not auto generating an init script as it does for the other elements of the ELK stack?
Is this a bug?