# Elasticsearch status red after installing x-pack

**URL:** <https://discuss.elastic.co/t/elasticsearch-status-red-after-installing-x-pack/128458>\
**Category:** Elasticsearch\
**Created:** [April 18, 2018, 5:12am UTC](https://discuss.elastic.co/t/elasticsearch-status-red-after-installing-x-pack/128458 "2018-04-18T05:12:02Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![rahulnama](https://avatars.discourse-cdn.com/v4/letter/r/8c91f0/32.png) [@rahulnama](https://discuss.elastic.co/u/rahulnama)\
**Post date:** [April 18, 2018, 5:12am UTC](https://discuss.elastic.co/t/elasticsearch-status-red-after-installing-x-pack/128458/1 "2018-04-18T05:12:02Z")

</div>

I'm using elasticsearch to index a 12 mb log file. I've indexed the log file and then installed the trial version of x-pack to give it a try.  
and then my elasticsearch status turned to red. Please have a look at the screenshot

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/4/e/4e94193d9eb5bd5a617a1924aacd5d7ccc600116.png)

Please let me know the reason.  
my kibana.yml file:

```
   server.port: 5601
   server.host: "0.0.0.0"
   elasticsearch.url: "http://localhost:9200"
   elasticsearch.preserveHost: true
   elasticsearch.username: "elastic"
   elasticsearch.password: " *********"

```

elasticsearch.yml file

```
bootstrap.memory_lock: true
cluster.name: elasticsearch
http.port: 9200
node.data: true
node.ingest: true
node.master: true
node.max_local_storage_nodes: 1
node.name: EC2AMAZ-1763048
path.data: C:\ProgramData\Elastic\Elasticsearch\data
path.logs: C:\ProgramData\Elastic\Elasticsearch\logs
transport.tcp.port: 9300

```

jvm.options:  
-XX:+UseConcMarkSweepGC  
-XX:CMSInitiatingOccupancyFraction=75  
-XX:+UseCMSInitiatingOccupancyOnly  
-XX:+AlwaysPreTouch  
-Xss1m  
-Djava.awt.headless=true  
-Dfile.encoding=UTF-8  
-Djna.nosys=true  
-XX:-OmitStackTraceInFastThrow  
-Dio.netty.noUnsafe=true  
-Dio.netty.noKeySetOptimization=true  
-Dio.netty.recycler.maxCapacityPerThread=0  
-Dlog4j.shutdownHookEnabled=false  
-Dlog4j2.disable.jmx=true  
-Djava.io.tmpdir=${ES\_TMPDIR}  
-XX:+HeapDumpOnOutOfMemoryError  
-Xmx4096m  
-Xms4096m

Please help to solve this

Thanks for your time as always 🙂

---

<div class="post-metadata">

**Author:** ![spinscale](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/spinscale/32/25011_2.png) [@spinscale](https://discuss.elastic.co/u/spinscale)\
**Post date:** [April 18, 2018, 6:30am UTC](https://discuss.elastic.co/t/elasticsearch-status-red-after-installing-x-pack/128458/2 "2018-04-18T06:30:58Z")

</div>

wild guess here: Is it possible you ran out of diskspace or you are almost at capacity. When this happens, Elasticsearch puts some indices into read-only mode. You need to allow them to be written first. Note: This is not an x-pack feature, but an Elasticsearch one.

See the flood stage setting at our documentation [https://www.elastic.co/guide/en/elasticsearch/reference/6.2/disk-allocator.html](https://www.elastic.co/guide/en/elasticsearch/reference/6.2/disk-allocator.html)

---

<div class="post-metadata">

**Author:** ![rahulnama](https://avatars.discourse-cdn.com/v4/letter/r/8c91f0/32.png) [@rahulnama](https://discuss.elastic.co/u/rahulnama)\
**Post date:** [April 18, 2018, 6:56am UTC](https://discuss.elastic.co/t/elasticsearch-status-red-after-installing-x-pack/128458/3 "2018-04-18T06:56:20Z")

</div>

Hey,

Thansk for the quick reply @spinscale.

Good guess I would say. I just increased the diskspace as it's almost full.

As you said I'm not able to write to some indices and I'm not sure how to change the mode. Anyway I'm not able to access kibana to execute it through dev tools. so I tried with curl but I'm not able to do it.

response from curl: AuthenticationException[Missing authentication token]

please do help.

Thanks for your time 🙂

---

<div class="post-metadata">

**Author:** ![spinscale](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/spinscale/32/25011_2.png) [@spinscale](https://discuss.elastic.co/u/spinscale)\
**Post date:** [April 18, 2018, 7:00am UTC](https://discuss.elastic.co/t/elasticsearch-status-red-after-installing-x-pack/128458/4 "2018-04-18T07:00:01Z")

</div>

The documentation link has a full blown example how to solve this. The error message you are getting is because you enabled security and thus you have to provide a username and a password (or you just log into kibana and do it from there).

---

<div class="post-metadata">

**Author:** ![rahulnama](https://avatars.discourse-cdn.com/v4/letter/r/8c91f0/32.png) [@rahulnama](https://discuss.elastic.co/u/rahulnama)\
**Post date:** [April 18, 2018, 8:32am UTC](https://discuss.elastic.co/t/elasticsearch-status-red-after-installing-x-pack/128458/5 "2018-04-18T08:32:41Z")

</div>

Thank you much @spinscale. I've gone through the documentation and able to do it. curl didn't work and I have done it with postman.

Thanks for your time 🙂

---

<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:** [May 16, 2018, 8:32am UTC](https://discuss.elastic.co/t/elasticsearch-status-red-after-installing-x-pack/128458/6 "2018-05-16T08:32:52Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.