Hello,
I have created a cluster ELK for my company on centos 7 using last version ELK 7 (1 logstash, 1 elasticsearch master, 1 elasticsearch indexer, and 1 kibana).
The purpose is to make ELK cluster up and to start XPACK trial period before purchasing.
The problem is when starting kibana, i get this error in journal
Elasticsearch cluster did not respond with license information.","prevState":"yellow","prevMsg":"Waiting for Elasticsearch"}
result of: curl -uelastic -XGET "http://localhost:9200/_xpack?pretty"
{
"build" : {
"hash" : "b7e28a7",
"date" : "2019-04-05T22:57:18.033826Z"
},
"license" : null,
"features" : {
"ccr" : {
"description" : "Cross Cluster Replication",
"available" : true,
"enabled" : true
},
"graph" : {
"description" : "Graph Data Exploration for the Elastic Stack",
"available" : true,
"enabled" : true
},
"ilm" : {
"description" : "Index lifecycle management for the Elastic Stack",
"available" : true,
"enabled" : true
},
"logstash" : {
"description" : "Logstash management component for X-Pack",
"available" : true,
"enabled" : true
},
"ml" : {
"description" : "Machine Learning for the Elastic Stack",
"available" : true,
"enabled" : true,
"native_code_info" : {
"version" : "7.0.0",
"build_hash" : "cdaa022645f38d"
}
},
"monitoring" : {
"description" : "Monitoring for the Elastic Stack",
"available" : true,
"enabled" : true
},
"rollup" : {
"description" : "Time series pre-aggregation and rollup",
"available" : true,
"enabled" : true
},
"security" : {
"description" : "Security for the Elastic Stack",
"available" : true,
"enabled" : false
},
"sql" : {
"description" : "SQL access to Elasticsearch",
"available" : true,
"enabled" : true
},
"watcher" : {
"description" : "Alerting, Notification and Automation for the Elastic Stack",
"available" : true,
"enabled" : true
}
},
"tagline" : "You know, for X"
}
and result of: curl -uelastic -XGET 'http://localhost:9200/_cluster/health?pretty'
{
"error" : {
"root_cause" : [
{
"type" : "master_not_discovered_exception",
"reason" : null
}
],
"type" : "master_not_discovered_exception",
"reason" : null
},
"status" : 503
}
can you please help?
Thanks.