# Elasticsearch status "elasticsearch dead but pid file exists"

**URL:** <https://discuss.elastic.co/t/elasticsearch-status-elasticsearch-dead-but-pid-file-exists/33600>\
**Category:** Elasticsearch\
**Created:** [November 3, 2015, 7:19am UTC](https://discuss.elastic.co/t/elasticsearch-status-elasticsearch-dead-but-pid-file-exists/33600 "2015-11-03T07:19:22Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![sunilmchaudhari](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sunilmchaudhari/32/9475_2.png) [@sunilmchaudhari](https://discuss.elastic.co/u/sunilmchaudhari)\
**Post date:** [November 3, 2015, 7:19am UTC](https://discuss.elastic.co/t/elasticsearch-status-elasticsearch-dead-but-pid-file-exists/33600/1 "2015-11-03T07:19:22Z")

</div>

Hi,  
I am trying to start master node of elasticsearch.  
It stops suddenly and shows status as "elasticsearch dead but pid file exists"  
I deleted pid file then it says syslock is locked. I deleted the same again it start saying "elasticsearch dead but pid file exists"

log file is blank.  
What might be the reason?

br,  
Sunil

---

<div class="post-metadata">

**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:** [November 3, 2015, 7:22am UTC](https://discuss.elastic.co/t/elasticsearch-status-elasticsearch-dead-but-pid-file-exists/33600/2 "2015-11-03T07:22:16Z")

</div>

What version, what does your config look like?

---

<div class="post-metadata">

**Author:** ![sunilmchaudhari](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sunilmchaudhari/32/9475_2.png) [@sunilmchaudhari](https://discuss.elastic.co/u/sunilmchaudhari)\
**Post date:** [November 3, 2015, 8:43am UTC](https://discuss.elastic.co/t/elasticsearch-status-elasticsearch-dead-but-pid-file-exists/33600/3 "2015-11-03T08:43:42Z")

</div>

version 1.5.2  
elasticsearch.yml

```
    ################################### Cluster ###################################
    
    # Cluster name identifies your cluster for auto-discovery. If you're running
    # multiple clusters on the same network, make sure you're using unique names.
    #
    cluster.name: presit-elasticsearch
    
    
    #################################### Node #####################################
    
    # Node names are generated dynamically on startup, so you're relieved
    # from configuring them manually. You can tie this node to a specific name:
    
    node.name: "presit-data-Node-2"
    
    # Every node can be configured to allow or deny being eligible as the master,
    # and to allow or deny to store the data.
    #
    # Allow this node to be eligible as a master node (enabled by default):
    #
    node.master: true
    #
    # Allow this node to store data (enabled by default):
    #
    node.data: true
    
    # You can exploit these settings to design advanced cluster topologies.
    #
    # 1. You want this node to never become a master node, only to hold data.
    # This will be the "workhorse" of your cluster.
    #
    #node.master: false
    #node.data: true
    #
    # 2. You want this node to only serve as a master: to not store any data and
    # to have free resources. This will be the "coordinator" of your cluster.
    #
    #node.master: true
    #node.data: false
    #
    # 3. You want this node to be neither master nor data node, but
    # to act as a "search load balancer" (fetching data from nodes,
    # aggregating results, etc.)
    #
    #node.master: false
    #node.data: false
    

      
    
    #################################### Index ####################################
    
    
    # Set the number of shards (splits) of an index (5 by default):
    #
    index.number_of_shards: 3
    
    # Set the number of replicas (additional copies) of an index (1 by default):
    #
    index.number_of_replicas: 2
    
    # Note, that for development on a local machine, with small indices, it usually
    # makes sense to "disable" the distributed features:
    #
    #index.number_of_shards: 1
    #index.number_of_replicas: 0

    
    #################################### Paths ####################################
    
 
    path.data: /elasticsearch
    
   #path.data: /path/to/data1,/path/to/data2
    
    # Path to temporary files:
    #
    #path.work: /path/to/work
    
     
    ################################## Security ################################
  
    http.cors.allow-origin: "/.*/"
    http.cors.enabled: true
    bootstrap.mlockall: true
```

---

<div class="post-metadata">

**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:** [November 3, 2015, 10:06am UTC](https://discuss.elastic.co/t/elasticsearch-status-elasticsearch-dead-but-pid-file-exists/33600/4 "2015-11-03T10:06:58Z")

</div>

I'd try to run the ES binary directly and see what it reports.

---

<div class="post-metadata">

**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, 11:40pm UTC](https://discuss.elastic.co/t/elasticsearch-status-elasticsearch-dead-but-pid-file-exists/33600/5 "2017-07-05T23:40:57Z")

</div>