<p dir="auto">Causes issue if you try to run a cron job as the ES user. Issue on centos 6, package from the repo.</p>
<div class="snippet-clipboard-content notranslate position-relative overflow-auto" data-snippet-clipboard-copy-content="[centos@ip-10-233-237-10 ~]$ sudo su - elasticsearch -s /bin/bash
su: warning: cannot change directory to /home/elasticsearch: No such file or directory

-bash-4.1$ grep elastic /etc/passwd
elasticsearch:x:498:498:elasticsearch user:/home/elasticsearch:/sbin/nologin

-bash-4.1$ ls -l /home/
total 4
drwx------. 3 centos centos 4096 Nov  2 20:23 centos"><pre class="notranslate"><code class="notranslate">[centos@ip-10-233-237-10 ~]$ sudo su - elasticsearch -s /bin/bash
su: warning: cannot change directory to /home/elasticsearch: No such file or directory

-bash-4.1$ grep elastic /etc/passwd
elasticsearch:x:498:498:elasticsearch user:/home/elasticsearch:/sbin/nologin

-bash-4.1$ ls -l /home/
total 4
drwx------. 3 centos centos 4096 Nov  2 20:23 centos
</code></pre></div>
<p dir="auto">We have a entirely Windows-based environment with no options to setup dedicated Linux VMs for Elastic Stack. Elasticsearch comes with a well functioning service wrapper.<br>
Unfortunately, Logstash and Kibana don't...<br>
To be able to install Logstash and Kibana as a service on Windows one has to use some other service wrapper - like for example the Non-Sucking-Service-Manager (<a href="https://nssm.cc/" rel="nofollow">https://nssm.cc/</a>), which in contrary of its name, really sucks! Reason: terminating the service won't always also terminate all Logstash/Kibana related processes. Meaning if you restart a service, instead of killing all processes from the old one and instantiating new ones, you have duplicated processes running.<br>
This is not how I imagine running Logstash and Kibana for a big project setup...<br>
Both should come with as-easy-installable services as Elasticsearch.</p>