Hey all,
Trying to get Kibana 5 (latest) to work with my SG-enabled ES cluster.
I gave the kibana user maximum permissions in the roles/mappings configuration, and in fact Kibana is able to create its own index (.kibana) in ES, so it’s almost working.
Kibana’s logs do show “Status changed from uninitialized to green - Ready”, so I’m hopeful…
However, when I try to access kibana’s “/app/kibana” path I get a HTTP 500 error. Kibana’s logs don’t show any further error info beyond
{
“type”: “error”,
“@timestamp”: “2016-12-07T15:20:11Z”,
“tags”: ,
“pid”: 7,
“level”: “error”,
“message”: “Authentication Exception”,
“error”: {
“message”: “Authentication Exception”,
“name”: “Error”,
“stack”: “Error: Authentication Exception\n at respond (/usr/share/kibana/node_modules/elasticsearch/src/lib/transport.js:289:15)\n at checkRespForFailure (/usr/share/kibana/node_modules/elasticsearch/src/lib/transport.js:248:7)\n at HttpConnector. (/usr/share/kibana/node_modules/elasticsearch/src/lib/connectors/http.js:164:7)\n at IncomingMessage.wrapper (/usr/share/kibana/node_modules/elasticsearch/node_modules/lodash/lodash.js:4994:19)\n at emitNone (events.js:91:20)\n at IncomingMessage.emit (events.js:185:7)\n at endReadableNT (_stream_readable.js:974:12)\n at _combinedTickCallback (internal/process/next_tick.js:74:11)\n at process._tickDomainCallback (internal/process/next_tick.js:122:9)”
},
“url”: {
“protocol”: null,
“slashes”: null,
“auth”: null,
“host”: null,
“port”: null,
“hostname”: null,
“hash”: null,
“search”: “”,
“query”: {},
“pathname”: “/app/kibana”,
“path”: “/app/kibana”,
“href”: “/app/kibana”
}
}
The es username and password are set correctly (it’s succeeding in creating its own index, after all).
Certificates seem to be configured correctly (otherwise the above would not have worked).
What else could it be?
Any ideas how to debug this?
Much appreciated,
Assaf Lavie