# How to start elasticsearch? **URL:** \ **Category:** Elasticsearch\ **Created:** [October 25, 2016, 3:47pm UTC](https://discuss.elastic.co/t/how-to-start-elasticsearch/63900 "2016-10-25T15:47:33Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![friscos](https://avatars.discourse-cdn.com/v4/letter/f/9e8a1a/32.png) [@friscos](https://discuss.elastic.co/u/friscos)\ **Post date:** [October 25, 2016, 3:47pm UTC](https://discuss.elastic.co/t/how-to-start-elasticsearch/63900/1 "2016-10-25T15:47:33Z")
Hi, My elasticsearch service is being stopped upon exit from the terminal. How do i stop happening that? `./elasticsearch [2016-10-25 11:44:40,600][INFO][node] [Harry Leland] version[2.4.1], pid[8729], build[c67dc32/2016-09-27T18:57:55Z] [2016-10-25 11:44:40,601][INFO][node] [Harry Leland] initializing ... [2016-10-25 11:44:41,656][INFO][plugins] [Harry Leland] modules [reindex, lang-expression, lang-groovy], plugins [], sites [] [2016-10-25 11:44:41,692][INFO][env] [Harry Leland] using [1] data paths, mounts [[/apps (/dev/xvdb1)]], net usable_space [88.5gb], net total_space [93.7gb], spins? [no], types [ext4] [2016-10-25 11:44:41,692][INFO][env] [Harry Leland] heap size [1007.3mb], compressed ordinary object pointers [true] [2016-10-25 11:44:41,693][WARN][env] [Harry Leland] max file descriptors [4096] for elasticsearch process likely too low, consider increasing to at least [65536] [2016-10-25 11:44:44,820][INFO][node] [Harry Leland] initialized [2016-10-25 11:44:44,820][INFO][node] [Harry Leland] starting ... [2016-10-25 11:44:45,027][INFO][transport] [Harry Leland] publish_address {127.0.0.1:9300}, bound_addresses {127.0.0.1:9300} [2016-10-25 11:44:45,036][INFO][discovery] [Harry Leland] elasticsearch/FXUp97iTQdqxEkgfVtZ2fw [2016-10-25 11:44:48,152][INFO][cluster.service] [Harry Leland] new_master {Harry Leland}{FXUp97iTQdqxEkgfVtZ2fw}{127.0.0.1}{127.0.0.1:9300}, reason: zen-disco-join(elected_as_master, [0] joins received) [2016-10-25 11:44:48,221][INFO][http] [Harry Leland] publish_address {127.0.0.1:9200}, bound_addresses {127.0.0.1:9200} [2016-10-25 11:44:48,221][INFO][node] [Harry Leland] started [2016-10-25 11:44:48,242][INFO][gateway] [Harry Leland] recovered [0] indices into cluster_state ^C[2016-10-25 11:45:10,469][INFO][node] [Harry Leland] stopping ... [2016-10-25 11:45:10,484][INFO][node] [Harry Leland] stopped [2016-10-25 11:45:10,484][INFO][node] [Harry Leland] closing ... [2016-10-25 11:45:10,491][INFO][node] [Harry Leland] closed` ---
**Author:** ![mainec](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mainec/32/5557_2.png) [@mainec](https://discuss.elastic.co/u/mainec)\ **Post date:** [October 25, 2016, 5:08pm UTC](https://discuss.elastic.co/t/how-to-start-elasticsearch/63900/2 "2016-10-25T17:08:11Z")
Can you describe your use case a bit more? As a general advise I'd suggest following our installation guide here [https://www.elastic.co/guide/en/elasticsearch/reference/5.x/install-elasticsearch.html](https://www.elastic.co/guide/en/elasticsearch/reference/5.x/install-elasticsearch.html) Hope that helps, Isabel ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [October 26, 2016, 9:16am UTC](https://discuss.elastic.co/t/how-to-start-elasticsearch/63900/3 "2016-10-26T09:16:42Z")
> [@friscos](#): > > ^C That's why, you are running the process in the foreground and then calling interrupt. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 5, 2017, 10:09pm UTC](https://discuss.elastic.co/t/how-to-start-elasticsearch/63900/4 "2017-07-05T22:09:40Z")