# Logstash stops elasticsearch **URL:** \ **Category:** Elasticsearch\ **Created:** [January 12, 2023, 11:20am UTC](https://discuss.elastic.co/t/logstash-stops-elasticsearch/323017 "2023-01-12T11:20:41Z")\ **Posts on this page:** 1\ **Showing post:** 18
**Author:** ![stephenb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stephenb/32/40856_2.png) [@stephenb](https://discuss.elastic.co/u/stephenb)\ **Post date:** [January 17, 2023, 7:29am UTC](https://discuss.elastic.co/t/logstash-stops-elasticsearch/323017/18 "2023-01-17T07:29:36Z")
> [@bas\_kos](#): > > Yes, everything is on one server. Do you think the server is not enough memory? Perhaps..if you start other processes and then try to start elasticsesrch , on your 8GB host elasticsearch will try to claim 4GB if it is not available it will fail. Perhaps take a look at this thread very similar > [@Elastic can not start because of memory issue](https://discuss.elastic.co/t/elastic-can-not-start-because-of-memory-issue/282711/13): > > Understood I am just relating best practices and why you are having issues. Elasticsearch can run like this, BUT Elasticsearch will not run / will not run well if it can not claim the RAM it needs. So if 1gb of RAM works then fine. Also you can always start elasticsearch first let it claim its RAM then let the other processes "fight" of the remaining RAM. So in this case you need to manually set the elasticsearch RAM as you just did... 1GB is pretty small... it may or may not work well depend… --- _[View the full topic](https://discuss.elastic.co/t/logstash-stops-elasticsearch/323017)._