# How to keep EnterpriseSearch running all the time

**URL:** <https://discuss.elastic.co/t/how-to-keep-enterprisesearch-running-all-the-time/274448>\
**Category:** Elastic Search\
**Created:** [May 31, 2021, 4:01am UTC](https://discuss.elastic.co/t/how-to-keep-enterprisesearch-running-all-the-time/274448 "2021-05-31T04:01:22Z")\
**Posts on this page:** 1\
**Showing post:** 22

<div class="post-metadata">

**Author:** ![reka.gay](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/reka.gay/32/91470_2.png) [@reka.gay](https://discuss.elastic.co/u/reka.gay)\
**Post date:** [July 12, 2021, 6:55am UTC](https://discuss.elastic.co/t/how-to-keep-enterprisesearch-running-all-the-time/274448/22 "2021-07-12T06:55:29Z")

</div>

@oleksiy-elastic I had to configure it to 9200 and moved elastic to 9201 as we only have 9200 open to our AWS VMs and it takes a long time to get that changed.

That issue has resolved itself after a few restarts (or maybe when I changed the user for the `filebeat` log??) and got replaced by

```auto
NoMethodError: undefined method `join' for nil:NilClass

```

Which I have found some posts for already and it turned out that when AppSearch started up, it killed ElasticSearch - and pretty much the whole VM.

I restarted the VM and it's actually up and running now, but I suspect failures will start again when the log rotates as the owner will be root again instead of the `enterprise-search` user.

Any suggestions on how to resolve that?

---

_[View the full topic](https://discuss.elastic.co/t/how-to-keep-enterprisesearch-running-all-the-time/274448)._