If I run kibana I can see this error
log [11:15:40.772] [info][status][plugin:kibana] Status changed from uninitialized to green - Ready
log [11:15:40.804] [info][status][plugin:elasticsearch] Status changed from uninitialized to yellow - Waiting for Elasticsearch
log [11:15:40.821] [info][status][plugin:kbn_vislib_vis_types] Status changed from uninitialized to green - Ready
log [11:15:40.826] [info][status][plugin:markdown_vis] Status changed from uninitialized to green - Ready
log [11:15:40.831] [info][status][plugin:metric_vis] Status changed from uninitialized to green - Ready
log [11:15:40.837] [info][status][plugin:spyModes] Status changed from uninitialized to green - Ready
log [11:15:40.842] [info][status][plugin:statusPage] Status changed from uninitialized to green - Ready
log [11:15:40.847] [info][status][plugin:table_vis] Status changed from uninitialized to green - Ready
log [11:15:40.866] [info][listening] Server running at http://0.0.0.0:5601
log [11:15:40.881] [error][status][plugin:elasticsearch] Status changed from yellow to red - Authentication Exception
Environment 2.1.1
shield 2.1
kibana 4.3.0
After some google search I found out this
Elasticsearch works with standard HTTP basic authentication headers to identify the requester. Since Elasticsearch is stateless, this header must be sent with every request:
Authorization: Basic
The is computed as base64(USERNAME:PASSWORD)
My question is from which path or file i needs to set this authorization: Basic
Related
I have two servers: Kibana is installed on one of them and Elasticsearch is installed on another one.
The Kibana's version is 4.5.4
The Elastic version is 2.3.1
Here is what I get when I start kibana
log [07:25:26.859] [info][status][plugin:kibana] Status changed from uninitialized to green - Ready
log [07:25:26.890] [info][status][plugin:elasticsearch] Status changed from uninitialized to yellow - Waiting for Elasticsearch
log [07:25:26.905] [info][status][plugin:kbn_vislib_vis_types] Status changed from uninitialized to green - Ready
log [07:25:26.913] [info][status][plugin:markdown_vis] Status changed from uninitialized to green - Ready
log [07:25:26.919] [info][status][plugin:metric_vis] Status changed from uninitialized to green - Ready
log [07:25:26.923] [info][status][plugin:spyModes] Status changed from uninitialized to green - Ready
log [07:25:26.940] [info][status][plugin:statusPage] Status changed from uninitialized to green - Ready
log [07:25:26.945] [info][status][plugin:table_vis] Status changed from uninitialized to green - Ready
log [07:25:26.950] [error][status][plugin:elasticsearch] Status changed from yellow to red - Elasticsearch is still initializing the kibana index.
log [07:25:26.952] [info][listening] Server running at http://0.0.0.0:5601
According to this answer I delete an index file in elasticsearch.
Then I restart kibana and elastic, and here is what I get in the log, when I try to start kibana.
log [07:29:57.455] [info][status][plugin:kibana] Status changed from uninitialized to green - Ready
log [07:29:57.488] [info][status][plugin:elasticsearch] Status changed from uninitialized to yellow - Waiting for Elasticsearch
log [07:29:57.502] [error][elasticsearch] Request error, retrying -- connect ECONNREFUSED 10.205.102.36:9200
log [07:29:57.508] [warning][elasticsearch] Unable to revive connection: http://10.205.102.36:9200/
log [07:29:57.509] [warning][elasticsearch] No living connections
log [07:29:57.511] [error][status][plugin:elasticsearch] Status changed from yellow to red - Unable to connect to Elasticsearch at http://10.205.102.36:9200.
log [07:29:57.512] [info][status][plugin:kbn_vislib_vis_types] Status changed from uninitialized to green - Ready
log [07:29:57.516] [info][status][plugin:markdown_vis] Status changed from uninitialized to green - Ready
log [07:29:57.519] [info][status][plugin:metric_vis] Status changed from uninitialized to green - Ready
log [07:29:57.529] [info][status][plugin:spyModes] Status changed from uninitialized to green - Ready
log [07:29:57.533] [info][status][plugin:statusPage] Status changed from uninitialized to green - Ready
log [07:29:57.536] [info][status][plugin:table_vis] Status changed from uninitialized to green - Ready
log [07:29:57.542] [info][listening] Server running at http://0.0.0.0:5601
log [07:30:05.102] [info][status][plugin:elasticsearch] Status changed from red to yellow - No existing Kibana index found
log [07:30:35.288] [error][status][plugin:elasticsearch] Status changed from yellow to red - Waiting for Kibana index ".kibana" to come online failed.
log [07:30:37.803] [error][status][plugin:elasticsearch] Status changed from red to red - Elasticsearch is still initializing the kibana index.
So when I delete an index, it creates it again and shows the same error. How can I resolve this problem?
I am using AWS Elasticsearch service with 5.1 version.
I have separate installation of kibana 5.1.1 with x-pack.
My Kibana is not coming up, giving Authorization Exception
As per forum https://forums.aws.amazon.com/thread.jspa?threadID=248200, Amazon ES does not support x-pack plugin.
Now How do i create users in kibana
Below are the Logs on Kibana Terminal:
> log [07:54:06.223] [error][status][plugin:xpack_main#5.1.1] Status
> changed from yellow to red – Authorization Exception log
> [07:54:06.224] [error][status][plugin:graph#5.1.1] Status changed from
> yellow to red – Authorization Exception log [07:54:06.224]
> [error][status][plugin:reporting#5.1.1] Status changed from yellow to
> red – Authorization Exception log [07:54:06.225]
> [error][status][plugin:elasticsearch#5.1.1] Status changed from yellow
> to red – Authorization Exception log [07:54:06.230]
> [error][status][plugin:security#5.1.1] Status changed from
> uninitialized to red – Authorization Exception log [07:54:06.231]
> [warning][security] Generating a random key for
> xpack.security.encryptionKey. To prevent sessions from being
> invalidated on restart, please set xpack.security.encryptionKey in
> kibana.yml log [07:54:06.234] [warning][security] Session cookies will
> be transmitted over insecure connections. This is not recommended. log
> [07:54:06.279] [error][status][plugin:profiler#5.1.1] Status changed
> from uninitialized to red – Authorization Exception
I downloaded elasticsearch and open in console. ES worked good and had status green. Next I downloaded Kibana and open - now I have still yellow status, also if I stopped Kibana.
I have info:
[o.e.c.r.a.AllocationService] [4e84hhA] Cluster health status changed
from [RED] to [YELLOW] (reason: [shards started [[.kibana][0]] ...]).
How can I fix it and where I can find more information for this error?
That's probably because the .kibana index has one replica shard and you have a single ES node running.
Run this and you'll get a GREEN status again:
PUT /.kibana/_settings
{
"index" : {
"number_of_replicas" : 0
}
}
Kibana is unable to initialize when starting, it shows the misleading exception "Shard Failures" without any details:
But when digging in the Browser console, the following logs have been written:
"INFO: 2016-11-25T13:41:59Z
Adding connection to https://monitoring.corp.com/elk-kibana/elasticsearch
" kibana.bundle.js:63741:6
config initcommons.bundle.js:62929
complete in 459.08ms commons.bundle.js:62925:12
loading default index patterncommons.bundle.js:62929
Index Patterns: index pattern set to logstash-* commons.bundle.js:8926:17
complete in 125.70ms commons.bundle.js:62925:12
Error: indexPattern.fields is undefined
isSortable#https://monitoring.corp.com/elk-kibana/bundles/kibana.bundle.js?v=9732:85441:8
getSort#https://monitoring.corp.com/elk-kibana/bundles/kibana.bundle.js?v=9732:85448:47
__WEBPACK_AMD_DEFINE_RESULT__</getSort.array#https://monitoring.corp.com/elk-kibana/bundles/kibana.bundle.js?v=9732:85463:15
getStateDefaults#https://monitoring.corp.com/elk-kibana/bundles/kibana.bundle.js?v=9732:85015:16
__WEBPACK_AMD_DEFINE_RESULT__</<#https://monitoring.corp.com/elk-kibana/bundles/kibana.bundle.js?v=9732:85009:47
invoke#https://monitoring.corp.com/elk-kibana/bundles/commons.bundle.js?v=9732:31569:15
$ControllerProvider/this.$get</</instantiate<#https://monitoring.corp.com/elk-kibana/bundles/commons.bundle.js?v=9732:36227:25
nodeLinkFn#https://monitoring.corp.com/elk-kibana/bundles/commons.bundle.js?v=9732:35339:37
compositeLinkFn#https://monitoring.corp.com/elk-kibana/bundles/commons.bundle.js?v=9732:34771:14
publicLinkFn#https://monitoring.corp.com/elk-kibana/bundles/commons.bundle.js?v=9732:34646:31
ngViewFillContentFactory/<.link#https://monitoring.corp.com/elk-kibana/bundles/commons.bundle.js?v=9732:57515:8
invokeLinkFn#https://monitoring.corp.com/elk-kibana/bundles/commons.bundle.js?v=9732:35880:10
nodeLinkFn#https://monitoring.corp.com/elk-kibana/bundles/commons.bundle.js?v=9732:35380:12
compositeLinkFn#https://monitoring.corp.com/elk-kibana/bundles/commons.bundle.js?v=9732:34771:14
publicLinkFn#https://monitoring.corp.com/elk-kibana/bundles/commons.bundle.js?v=9732:34646:31
createBoundTranscludeFn/boundTranscludeFn#https://monitoring.corp.com/elk-kibana/bundles/commons.bundle.js?v=9732:34790:17
controllersBoundTransclude#https://monitoring.corp.com/elk-kibana/bundles/commons.bundle.js?v=9732:35407:19
update#https://monitoring.corp.com/elk-kibana/bundles/commons.bundle.js?v=9732:57465:26
$RootScopeProvider/this.$get</Scope.prototype.$broadcast#https://monitoring.corp.com/elk-kibana/bundles/commons.bundle.js?v=9732:43402:16
commitRoute/<#https://monitoring.corp.com/elk-kibana/bundles/commons.bundle.js?v=9732:57149:16
processQueue#https://monitoring.corp.com/elk-kibana/bundles/commons.bundle.js?v=9732:41836:29
scheduleProcessQueue/<#https://monitoring.corp.com/elk-kibana/bundles/commons.bundle.js?v=9732:41852:28
$RootScopeProvider/this.$get</Scope.prototype.$eval#https://monitoring.corp.com/elk-kibana/bundles/commons.bundle.js?v=9732:43080:17
$RootScopeProvider/this.$get</Scope.prototype.$digest#https://monitoring.corp.com/elk-kibana/bundles/commons.bundle.js?v=9732:42891:16
$RootScopeProvider/this.$get</Scope.prototype.$apply#https://monitoring.corp.com/elk-kibana/bundles/commons.bundle.js?v=9732:43188:14
done#https://monitoring.corp.com/elk-kibana/bundles/commons.bundle.js?v=9732:37637:37
completeRequest#https://monitoring.corp.com/elk-kibana/bundles/commons.bundle.js?v=9732:37835:8
requestLoaded#https://monitoring.corp.com/elk-kibana/bundles/commons.bundle.js?v=9732:37776:10
<div class="application ng-scope" ng-class="'tab-' + chrome.getActiveTabId('-none-') + ' ' + chrome.getApplicationClasses()" ng-view="" ng-controller="chrome.$$rootControllerConstruct as kibana"> commons.bundle.js:39568:19
Error: Request to Elasticsearch failed: "Bad Request"
KbnError#https://monitoring.corp.com/elk-kibana/bundles/commons.bundle.js?v=9732:62016:21
RequestFailure#https://monitoring.corp.com/elk-kibana/bundles/commons.bundle.js?v=9732:62049:6
__WEBPACK_AMD_DEFINE_RESULT__</</</<#https://monitoring.corp.com/elk-kibana/bundles/kibana.bundle.js?v=9732:88628:16
processQueue#https://monitoring.corp.com/elk-kibana/bundles/commons.bundle.js?v=9732:41836:29
scheduleProcessQueue/<#https://monitoring.corp.com/elk-kibana/bundles/commons.bundle.js?v=9732:41852:28
$RootScopeProvider/this.$get</Scope.prototype.$eval#https://monitoring.corp.com/elk-kibana/bundles/commons.bundle.js?v=9732:43080:17
$RootScopeProvider/this.$get</Scope.prototype.$digest#https://monitoring.corp.com/elk-kibana/bundles/commons.bundle.js?v=9732:42891:16
$RootScopeProvider/this.$get</Scope.prototype.$apply#https://monitoring.corp.com/elk-kibana/bundles/commons.bundle.js?v=9732:43188:14
done#https://monitoring.corp.com/elk-kibana/bundles/commons.bundle.js?v=9732:37637:37
completeRequest#https://monitoring.corp.com/elk-kibana/bundles/commons.bundle.js?v=9732:37835:8
requestLoaded#https://monitoring.corp.com/elk-kibana/bundles/commons.bundle.js?v=9732:37776:10
commons.bundle.js:39568:19
I'm aware of the https://github.com/elastic/kibana/issues/6460 issue, but we don't have any signs of an entity which is too large.
I also recreated the indexpattern already, without luck (deleting and creating).
However when going into the "Settings" > "Index pattern" where the fields are shown, and going back to discover, kibana seems to work again (until next browser refresh). Any ideas how to fix kibana?
Kibana version: 4.4.2
Elasticsearch version: 2.2.0
Increasing the server.maxPayloadBytes property in the kibana.yml file to an appropiate size solved the issue.
I have my kibana running normal but I can't open the link from browser.
Please find the Kibana logs below,
log [14:09:05.036] [info][status][plugin:kibana] Status changed from uninitialized to green - Ready
log [14:09:05.065] [info][status][plugin:elasticsearch] Status changed from uninitialized to yellow - Waiting for Elasticsearch
log [14:09:05.100] [info][status][plugin:shield] Status changed from uninitialized to green - Ready
log [14:09:05.103] [info][status][plugin:kbn_vislib_vis_types] Status changed from uninitialized to green - Ready
log [14:09:05.111] [info][status][plugin:markdown_vis] Status changed from uninitialized to green - Ready
log [14:09:05.116] [info][status][plugin:metric_vis] Status changed from uninitialized to green - Ready
log [14:09:05.118] [info][status][plugin:spyModes] Status changed from uninitialized to green - Ready
log [14:09:05.128] [info][status][plugin:statusPage] Status changed from uninitialized to green - Ready
log [14:09:05.132] [info][status][plugin:table_vis] Status changed from uninitialized to green - Ready
log [14:09:05.136] [info][status][plugin:elasticsearch] Status changed from yellow to green - Kibana index ready
log [14:09:05.140] [info][listening] Server running at https://0.0.0.0:5600
I tried the elasticsearch by
curl localhost:9200
It shows,
{
"name" : "Scream",
"cluster_name" : "elasticsearch",
"version" : {
"number" : "2.3.3",
"build_hash" : "218bdf10790eef486ff2c41a3df5cfa32dadcfde",
"build_timestamp" : "2016-05-17T15:40:04Z",
"build_snapshot" : false,
"lucene_version" : "5.5.0"
},
"tagline" : "You Know, for Search"
}
but for kibana:
curl localhost:5600
curl: (52) Empty reply from server
Please find my kibana config,
port: 5600
# The host to bind the server to.
host: "0.0.0.0"
# The Elasticsearch instance to use for all your queries.
elasticsearch_url: "http://localhost:9200"
Problem is quite old but in case someone ends up here - make sure to use "https".
The fineprint does say that "ignore the self-signed certificate error" :)
I was stack in same issue.
I think the problem is occurred when you do port forwarding.
You have to set 0.0.0.0:5601 as a source port.
I ran the latest GitHub 5.5.0 install and when I tried to bring up the localhost, IE just said Kibana LOADING...
However, I installed Chrome and Kibana popped right up. So the solution is to use a different browser.