# "null\_pointer\_exception" encountered in latest ES/Marvel

**URL:** <https://discuss.elastic.co/t/null-pointer-exception-encountered-in-latest-es-marvel/35491>\
**Category:** Kibana\
**Tags:** elastic-stack-monitoring\
**Created:** [November 24, 2015, 9:53pm UTC](https://discuss.elastic.co/t/null-pointer-exception-encountered-in-latest-es-marvel/35491 "2015-11-24T21:53:43Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![tguan](https://avatars.discourse-cdn.com/v4/letter/t/958977/32.png) [@tguan](https://discuss.elastic.co/u/tguan)\
**Post date:** [November 24, 2015, 9:53pm UTC](https://discuss.elastic.co/t/null-pointer-exception-encountered-in-latest-es-marvel/35491/1 "2015-11-24T21:53:43Z")

</div>

I have just installed latest Elasticsearch 2.0.0, Kibana-4.2.1, and then downloaded the latest Marvel plugin. Even put following line in elasticsearch.yml ( is this needed?)  
echo 'marvel.agent.enabled: false' \>\> ./config/elasticsearch.yml

However, I kept on seeing following exception in Kibana when clicking anything in Marvel UI. I did not see anything like this when I used the package from training class. BTW: this is freshly built cluster.

Thanks in advance  
Tao

error [13:39:19.962] [null\_pointer\_exception] null :: {"path":"/.marvel-es-\*/\_field\_stats","query":{"level":"indices","ignore\_unavailable":true},"body":"{"fields":["timestamp"],"index\_constraints":{"timestamp":{"max\_value":{"gte":"2015-11-24T20:39:12.312Z"},"min\_value":{"lte":"2015-11-24T21:39:12.312Z"}}}}","statusCode":500,"response":"{"error":{"root\_cause":[{"type":"null\_pointer\_exception","reason":null}],"type":"null\_pointer\_exception","reason":null},"status":500}"}  
at respond (/home/nutanix/kibana-4.2.1-linux-x64/node\_modules/elasticsearch/src/lib/transport.js:238:15)  
at checkRespForFailure (/home/nutanix/kibana-4.2.1-linux-x64/node\_modules/elasticsearch/src/lib/transport.js:201:7)  
at HttpConnector. (/home/nutanix/kibana-4.2.1-linux-x64/node\_modules/elasticsearch/src/lib/connectors/http.js:155:7)  
at IncomingMessage.wrapper (/home/nutanix/kibana-4.2.1-linux-x64/node\_modules/lodash/index.js:3095:19)  
at IncomingMessage.emit (events.js:129:20)  
at \_stream\_readable.js:908:16  
at process.\_tickDomainCallback (node.js:381:11)

---

<div class="post-metadata">

**Author:** ![tanguy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tanguy/32/6030_2.png) [@tanguy](https://discuss.elastic.co/u/tanguy)\
**Post date:** [November 25, 2015, 8:44am UTC](https://discuss.elastic.co/t/null-pointer-exception-encountered-in-latest-es-marvel/35491/2 "2015-11-25T08:44:11Z")

</div>

Hi,

> [@tguan](#):
>
> Even put following line in elasticsearch.yml ( is this needed?)echo 'marvel.agent.enabled: false' \>\> ./config/elasticsearch.yml

`marvel.agent.enabled` is a setting from Marvel 1.x and is not supported in Marvel 2. The equivalent is `marvel.enabled: true|false`. This setting is needed if you want to disable Marvel which is not your case.

We just released a bunch of new versions that fix some bugs (ES 2.1.0, Kibana 4.3.0 and Marvel 2.1.0)... Can you try with these?

-- Tanguy

---

<div class="post-metadata">

**Author:** ![dfr0](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dfr0/32/6433_2.png) [@dfr0](https://discuss.elastic.co/u/dfr0)\
**Post date:** [December 3, 2015, 4:52am UTC](https://discuss.elastic.co/t/null-pointer-exception-encountered-in-latest-es-marvel/35491/3 "2015-12-03T04:52:08Z")

</div>

I 've the same problem tanguy

error [04:49:47.250] [null\_pointer\_exception] null :: {"path":"/.marvel-es-\*/\_field\_stats","query":{"level":"indices","ignore\_unavailable":true},"body":"{"fields":["timestamp"],"index\_constraints":{"timestamp":{"max\_value":{"gte":"2015-12-03T03:49:47.068Z"},"min\_value":{"lte":"2015-12-03T04:49:47.068Z"}}}}","statusCode":500,"response":"{"error":{"root\_cause":[{"type":"null\_pointer\_exception","reason":null}],"type":"null\_pointer\_exception","reason":null},"status":500}"}  
at respond (/data/www/kibana/node\_modules/elasticsearch/src/lib/transport.js:238:15)  
at checkRespForFailure (/data/www/kibana/node\_modules/elasticsearch/src/lib/transport.js:201:7)  
at HttpConnector. (/data/www/kibana/node\_modules/elasticsearch/src/lib/connectors/http.js:155:7)  
at IncomingMessage.wrapper (/data/www/kibana/node\_modules/lodash/index.js:3095:19)  
at IncomingMessage.emit (events.js:129:20)  
at \_stream\_readable.js:908:16  
at process.\_tickDomainCallback (node.js:381:11)

---

<div class="post-metadata">

**Author:** ![dfr0](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dfr0/32/6433_2.png) [@dfr0](https://discuss.elastic.co/u/dfr0)\
**Post date:** [December 3, 2015, 4:59am UTC](https://discuss.elastic.co/t/null-pointer-exception-encountered-in-latest-es-marvel/35491/4 "2015-12-03T04:59:27Z")

</div>

i probe that and does'n t works

---

<div class="post-metadata">

**Author:** ![tanguy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tanguy/32/6030_2.png) [@tanguy](https://discuss.elastic.co/u/tanguy)\
**Post date:** [December 3, 2015, 8:42am UTC](https://discuss.elastic.co/t/null-pointer-exception-encountered-in-latest-es-marvel/35491/5 "2015-12-03T08:42:25Z")

</div>

Concerning the null pointer exception see my comment here [Problems with apache and marvel plugin](https://discuss.elastic.co/t/problems-with-apache-and-marvel-plugin/35623/9?u=tanguy)

---

<div class="post-metadata">

**Author:** ![tguan](https://avatars.discourse-cdn.com/v4/letter/t/958977/32.png) [@tguan](https://discuss.elastic.co/u/tguan)\
**Post date:** [December 4, 2015, 12:57am UTC](https://discuss.elastic.co/t/null-pointer-exception-encountered-in-latest-es-marvel/35491/6 "2015-12-04T00:57:25Z")

</div>

Hi tanguy

I have installed the last software on a new cluster, but I am getting new issues:

1. Without Marvel, I saw this message:  
log [16:53:47.173] [error][status][plugin:elasticsearch] Status changed from yellow to red - Elasticsearch is still initializing the kibana index... Trying again in 2.5 second.

deleting all the indices does not help.

1. After install Marvel, I am getting these messages.  
log [16:50:55.862] [error][status][plugin:elasticsearch] Status changed from yellow to red - Waiting for Kibana index ".kibana" to come online failed.  
log [16:50:58.381] [error][status][plugin:elasticsearch] Status changed from red to red - Elasticsearch is still initializing the kibana index... Trying again in 2.5 second.  
error [16:51:02.531] [search\_phase\_execution\_exception] all shards failed :: {"path":"/.marvel-es-data/cluster\_info/\_search","query":{},"body":"{"size":10000}","statusCode":503,"response":"{"error":{"root\_cause":[],"type":"search\_phase\_execution\_exception","reason":"all shards failed","phase":"query\_fetch","grouped":true,"failed\_shards":[]},"status":503}"}  
at respond (/home/nutanix/es/kibana-4.3.0-linux-x64/node\_modules/elasticsearch/src/lib/transport.js:238:15)  
at checkRespForFailure (/home/nutanix/es/kibana-4.3.0-linux-x64/node\_modules/elasticsearch/src/lib/transport.js:201:7)  
at HttpConnector. (/home/nutanix/es/kibana-4.3.0-linux-x64/node\_modules/elasticsearch/src/lib/connectors/http.js:155:7)  
at IncomingMessage.wrapper (/home/nutanix/es/kibana-4.3.0-linux-x64/node\_modules/lodash/index.js:3095:19)  
at IncomingMessage.emit (events.js:129:20)  
at \_stream\_readable.js:908:16  
at process.\_tickDomainCallback (node.js:381:11)

2. 

[nutanix@ES-POC-VM-6 es]$ curl [http://10.4.78.15:9200/\_cat/indices?v](http://10.4.78.15:9200/_cat/indices?v)  
health status index pri rep docs.count docs.deleted store.size pri.store.size  
red open .marvel-es-2015.12.04 1 1  
red open .marvel-es-data 1 1  
red open nutanix-17459-2015.12.04 5 1  
red open .kibana 1 1  
red open nutanix-17459-2015.12.03 5 1  
[nutanix@ES-POC-VM-6 es]$ curl [http://10.4.78.15:9200/nutanix\*/\_count?pretty](http://10.4.78.15:9200/nutanix*/_count?pretty)  
{  
"error" : {  
"root\_cause" : [],  
"type" : "search\_phase\_execution\_exception",  
"reason" : "all shards failed",  
"phase" : "query",  
"grouped" : true,  
"failed\_shards" : []  
},  
"status" : 503  
}

[ES-POC-VM-6 es]$ java -version  
java version "1.8.0\_65"  
Java(TM) SE Runtime Environment (build 1.8.0\_65-b17)  
Java HotSpot(TM) 64-Bit Server VM (build 25.65-b01, mixed mode)

Thanks  
Tao

---

<div class="post-metadata">

**Author:** ![tanguy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tanguy/32/6030_2.png) [@tanguy](https://discuss.elastic.co/u/tanguy)\
**Post date:** [December 4, 2015, 8:39am UTC](https://discuss.elastic.co/t/null-pointer-exception-encountered-in-latest-es-marvel/35491/7 "2015-12-04T08:39:27Z")

</div>

@tguan : your indices all have a red status, meaning that they cannot be queried. You should investigate why they are in that state.

/\_cat/shards?v will give you more information.

You can also try to use the cluster reroute API with the explain parameter to assign marvel indices: it will tell you why the shard can't be assigned

---

<div class="post-metadata">

**Author:** ![tguan](https://avatars.discourse-cdn.com/v4/letter/t/958977/32.png) [@tguan](https://discuss.elastic.co/u/tguan)\
**Post date:** [December 4, 2015, 7:53pm UTC](https://discuss.elastic.co/t/null-pointer-exception-encountered-in-latest-es-marvel/35491/8 "2015-12-04T19:53:19Z")

</div>

Thanks tanguy! I am amazed by how responsive you and Elasticsearch team are!

I downgraded the software and hit the same issue. Eventually, I figured out that it was due to my dumb mistake in my script, which sets "node.data" to False on a supposedly data node. ☹

Will try out the latest package.

Regards  
Tao

---

<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 6, 2017, 1:46pm UTC](https://discuss.elastic.co/t/null-pointer-exception-encountered-in-latest-es-marvel/35491/9 "2017-07-06T13:46:15Z")

</div>