X-pack 5.1.1 error in kibana


(LuciferHBP) #1

Hi,

I have elasticsearch 5.1.1 & kibana 5.1.1, I installed x-pack 5.1.1 in both, but after restarting kibana i am getting following message in kibana:

[06:52:32.441] [info][status][ui settings] Status changed from uninitialized to green - Ready
[06:53:01.768] [warning][license][xpack] License information could not be obtained from Elasticsearch. [illegal_argument_exception
] No endpoint or operation is available at [_xpack] :: {"path":"/_xpack","statusCode":400,"response":"{"error":{"root_cause":[{"type
":"illegal_argument_exception","reason":"No endpoint or operation is available at [_xpack]"}],"type":"illegal_argument_exception
","reason":"No endpoint or operation is available at [_xpack]"},"status":400}"}
Unhandled rejection [illegal_argument_exception] No endpoint or operation is available at [_xpack] :: {"path":"/_xpack","statusCode":400,"
response":"{"error":{"root_cause":[{"type":"illegal_argument_exception","reason":"No endpoint or operation is available at [_xp
ack]"}],"type":"illegal_argument_exception","reason":"No endpoint or operation is available at [_xpack]"},"status":400}"}
at respond (D:\Elastic stack\kibana-5.1.1-windows-x86\node_modules\elasticsearch\src\lib\transport.js:289:15)
at checkRespForFailure (D:\Elastic stack\kibana-5.1.1-windows-x86\node_modules\elasticsearch\src\lib\transport.j
s:248:7)
at HttpConnector. (D:\Elastic stack\kibana-5.1.1-windows-x86\node_modules\elasticsearch\src\lib\conne
ctors\http.js:164:7)
at IncomingMessage.wrapper (D:\Elastic stack\kibana-5.1.1-windows-x86\node_modules\elasticsearch\node_modules\lo
dash\lodash.js:4994:19)
at emitNone (events.js:91:20)
at IncomingMessage.emit (events.js:185:7)
at endReadableNT (_stream_readable.js:974:12)
at _combinedTickCallback (internal/process/next_tick.js:74:11)
at process._tickDomainCallback (internal/process/next_tick.js:122:9)

And in browser i am unable to access localhost:5601

Any help please!!!! ,
Thanks,


(Mark Walkom) #2

Can you access localhost:9200?


(Alexander Reelsen) #3

This looks as if the x-pack plugin on the elasticsearch side was not installed successfully, can you rerun bin/elasticsearch-plugin install x-pack - make sure you finish the installation by manually agreeing on the ask for security permissions.


(LuciferHBP) #4

Thanks for the reply,
Yes localhost:9200 is accessible & output is:
{
"name" : "JMnD7eU",
"cluster_name" : "App-Cluster",
"cluster_uuid" : "pmE-CY9l6NuVK0TCpvIMKg",
"version" : {
"number" : "5.1.1",
"build_hash" : "4455e21",
"build_date" : "2016-12-06T12:36:15.409Z",
"build_snapshot" : false,
"lucene_version" : "6.3.0"
},
"tagline" : "You Know, for Search"
}


How to connect Kibana to Remote elasticsearch
(LuciferHBP) #5

Yes , i installed xpack in elasticsearch 5.1.1 by manually agreeing security persmission & finally it showed that successfully installed x-pack!!!!!


(Alexander Reelsen) #6

Hey,

great to see it working. An easy to check for installed plugins would be one of

curl 'localhost:9200/_nodes/plugins?filter_path=**.plugins.name&pretty'
curl 'localhost:9200/_cat/plugins'

If you dont want to agree manually on the permissions, there is also a batch mode available when installing the plugin using -b

--Alex


(LuciferHBP) #7

Thanks again, its working i have to created user in elasticsearch & same added in kibana config & its working :slight_smile:


#8

Hello,

same issue here.
What do you mean by create user for elasticsearch and kibana?
I've installed ELK with the yum install command.


(LuciferHBP) #9

After installing xpack ,shields gets in place so in Elasticsearch we must create a user with admin role and same credentials we must add in kibana.yml.
It worked for me, hope it 'll work!!!!


(system) #10

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