Problems with apache and marvel plugin

monitoring

(David F.) #1

Hi,

i've problems with marvel and reverse proxy.

My apache conf for this terms:

ProxyPass /app/marvel http://:5601/app/marvel
ProxyPassReverse /app/marvel http://
:5601/app/marvel

ProxyPass http://:5601/api/marvel
ProxyPassReverse http://
:5601/api/marvel

I see the cluster info correct:

But the nodes or other options give me errors:

I try with the rewrite options but i did not lucky, any ideas?

Thx for the support


(David F.) #2

i've the same problem on other machine without reverse proxy, error 500 when i try to connect to the cluster info.


(Mark Walkom) #3

What versions?


(David F.) #4

All are in version 2.0, logstash 2.0, elasticsearch 2.0 and kibana 4.2, you recommend upgrade all products for 2.1 versión??

thx warkolm


(David F.) #5

any idea???


(Tanguy) #6

Can you please check if there are errors in the Kibana output?


(David F.) #7

Yes all correct

log [04:45:58.318] [info][status][plugin:kibana] Status changed from uninitialized to green - Ready
log [04:45:58.389] [info][status][plugin:elasticsearch] Status changed from uninitialized to yellow - Waiting for Elasticsearch
log [04:45:58.417] [info][status][plugin:marvel] Status changed from uninitialized to yellow - Waiting for Elasticsearch
log [04:45:58.445] [info][status][plugin:kbn_vislib_vis_types] Status changed from uninitialized to green - Ready
log [04:45:58.464] [info][status][plugin:markdown_vis] Status changed from uninitialized to green - Ready
log [04:45:58.491] [info][status][plugin:metric_vis] Status changed from uninitialized to green - Ready
log [04:45:58.508] [info][status][plugin:spyModes] Status changed from uninitialized to green - Ready
log [04:45:58.518] [info][status][plugin:statusPage] Status changed from uninitialized to green - Ready
log [04:45:58.528] [info][status][plugin:table_vis] Status changed from uninitialized to green - Ready
log [04:45:58.536] [info][status][plugin:elasticsearch] Status changed from yellow to green - Kibana index ready
log [04:45:58.611] [info][listening] Server running at http://0.0.0.0:5601
log [04:45:58.615] [info][status][plugin:marvel] Status changed from yellow to green - Marvel index ready

i'll to configure the debug mode.


(David F.) #8

Yeah with the debug i see the following:

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)

I saw your other post about this 35491


500 Error when attempting to drill into Marvel cluster
(Tanguy) #9

Can you check the logs on Elasticsearch side?

If you see something like this:

[2015-12-02 00:11:34,633][INFO ][rest.suppressed          ] /.marvel-es-*/_field_stats Params: {level=indices, ignore_unavailable=true, index=.marvel-es-*}
java.lang.NullPointerException
	at org.elasticsearch.action.fieldstats.TransportFieldStatsTransportAction.newResponse(TransportFieldStatsTransportAction.java:122)

I think you hit this issue: https://github.com/elastic/elasticsearch/pull/14868

It should be fixed in the next bugfix release.


"null_pointer_exception" encountered in latest ES/Marvel
#10

Hi there,

Is there a workaround for this issue?


#11

I just installed elasticsearch 2.1.0 and kibana 4.3.0 and that fixed my problem.


(Steve Kearns) #12

Thanks for the update Gary - glad to see you got it working.


(system) #13