500 Error when attempting to drill into Marvel cluster

monitoring

(Dan) #1

I'm running an Elasticsearch 2.0 cluster primarily used for Logstash with the latest versions of Marvel and Kibana. All Kibana functionality seems to work as expected. When accessing Marvel, the page loads with the cluster details and state but when I attempt to click on and drill into that cluster I get a 500 error.

That error in the browser is just:

{"statusCode":500,"error":"Internal Server Error","message":"An internal server error occurred"}

It seems to be attempting to access:

Request URL:http://my.kibana.cluster/api/marvel/v1/clusters/Tk-RrFm7TnOocicaq-qjAQ

On the ES servers I was getting the following error:

[2015-12-01 00:28:16,290][INFO ][rest.suppressed ] /.marvel-es-/_field_stats Params: {index=.marvel-es-, level=indices, ignore_unavailable=true}
java.lang.NullPointerException
at org.elasticsearch.action.fieldstats.TransportFieldStatsTransportAction.newResponse(TransportFieldStatsTransportAction.java:122)
at org.elasticsearch.action.fieldstats.TransportFieldStatsTransportAction.newResponse(TransportFieldStatsTransportAction.java:54)
at org.elasticsearch.action.support.broadcast.TransportBroadcastAction$AsyncBroadcastAction.finishHim(TransportBroadcastAction.java:229)
at org.elasticsearch.action.support.broadcast.TransportBroadcastAction$AsyncBroadcastAction.onOperation(TransportBroadcastAction.java:194)
at org.elasticsearch.action.support.broadcast.TransportBroadcastAction$AsyncBroadcastAction$1.handleResponse(TransportBroadcastAction.java:174)
at org.elasticsearch.action.support.broadcast.TransportBroadcastAction$AsyncBroadcastAction$1.handleResponse(TransportBroadcastAction.java:161)
at org.elasticsearch.transport.netty.MessageChannelHandler.handleResponse(MessageChannelHandler.java:185)
at org.elasticsearch.transport.netty.MessageChannelHandler.messageReceived(MessageChannelHandler.java:138)
at org.jboss.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:70)
at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:564)
at org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendUpstream(DefaultChannelPipeline.java:791)
at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:296)
at org.jboss.netty.handler.codec.frame.FrameDecoder.unfoldAndFireMessageReceived(FrameDecoder.java:462)
at org.jboss.netty.handler.codec.frame.FrameDecoder.callDecode(FrameDecoder.java:443)
at org.jboss.netty.handler.codec.frame.FrameDecoder.messageReceived(FrameDecoder.java:303)
at org.jboss.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:70)
at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:564)
at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:559)
at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:268)
at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:255)
at org.jboss.netty.channel.socket.nio.NioWorker.read(NioWorker.java:88)
at org.jboss.netty.channel.socket.nio.AbstractNioWorker.process(AbstractNioWorker.java:108)
at org.jboss.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:337)
at org.jboss.netty.channel.socket.nio.AbstractNioWorker.run(AbstractNioWorker.java:89)
at org.jboss.netty.channel.socket.nio.NioWorker.run(NioWorker.java:178)
at org.jboss.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108)
at org.jboss.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:42)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)

Any help would be appreciated.


(Tanguy) #3

Hi,

Which versions exactly?


(Dan) #4

Marvel 2.1.0
Kibana 4.2.0


(Mark Walkom) #5

You need to use KB 4.3 with ES 2.1, see https://www.elastic.co/support/matrix


(Tanguy) #6

You may have the same issue as described here Problems with apache and marvel plugin


(Dan) #7

I'm not using ES 2.1. I'm using ES 2.0


(Dan) #8

Thanks. Looks like that's it. It seems like there was some success upgrading ES, Kibana and Marvel. I will try that. Thanks.


(David F.) #9

Me too, i'm using the 2.0 version.


(David F.) #10

i resolved this issue.


(Tanguy) #11

Happy to hear that:) By upgrading?


(David F.) #12

I had a problem with the new app routes

I resolved time ago with the following apache configuration:

Timeout 3200
ProxyTimeout 3200

ProxyRequests Off
ProxyPreserveHost On

Redirect /***** /app/kibana

Redirect /***** /elasticsearch

ProxyPass /status http://*:5601/status
ProxyPassReverse /status http://
:5601/status

ProxyPass /api/status http://:5601/api/status
ProxyPassReverse /api/status http://
:5601/api/status

ProxyPass /app/kibana http://******:5601/app/kibana
ProxyPassReverse /app/kibana http://******:5601/app/kibana

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

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

ProxyPass /bundles http://:5601/bundles
ProxyPassReverse /bundles http://
:5601/bundles

ProxyPass /elasticsearch http://:9200
ProxyPassReverse /elasticsearch http://
:9200

Proxy options

<Proxy http://******:5601/>
Order Deny,Allow
Deny from all
Allow from ****
AuthType Basic
AuthName *****
AuthUserFile ****
Require valid-user

<Proxy http://*******:9200/>
Order Deny,Allow
Deny from all
Allow from *******
AuthType Basic
AuthName ********
AuthUserFile *******
Require valid-user


(system) #13