Login is currently disabled. Administrators should consult the Kibana logs for more details.[still unsatisfactory]


(Yong Rhee) #1

After installing X-pack for both ElasticSearch and Kibana, I have encountered this problem as several users experienced before. I still can not resolve this issue after looking at document and other treads in the website.

Here is my log in an attached file
My config.yml is modified with user: "elastic" and password: "XXXX"


(Stacey Gammon) #2

What version are you on?

Can you navigate to localhost:9200 and log in directly to elasticsearch there? (or whatever custom URL if your elasticsearch is not hosted using the default domain/port).

That error happens usually when Kibana can't communicate with Elastic. Can you send over the logs from right after you boot up Kibana? Can you send over the logs from your Elasticsearch instance as well?

Is everything else in your kibana.yml using the default parameters? Anything customized in your elasticsearch.yml?


(Yong Rhee) #4

problem still remained

both are 6.3.0 and I have also auto-generated credentials using elasticsearch_password.bat and reflected on kibana.yml correctly {elastic:'PASSWORD'} so Kibana can connect to elasticsearch. problem is logstash is not working properly as I posted.

My machine is Windows and I installed using .msi so I don't directly can see elasticsearch.yml on my machine.
Elastic log

[2018-06-26T11:39:20,863][INFO ][o.e.n.Node               ] [DESKTOP-C93E9FL] initializing ...
[2018-06-26T11:39:20,952][INFO ][o.e.e.NodeEnvironment    ] [DESKTOP-C93E9FL] using [1] data paths, mounts [[Windows (C:)]], net usable_space [150.1gb], net total_space [237.2gb], types [NTFS]
[2018-06-26T11:39:20,953][INFO ][o.e.e.NodeEnvironment    ] [DESKTOP-C93E9FL] heap size [1.9gb], compressed ordinary object pointers [true]
[2018-06-26T11:39:21,441][INFO ][o.e.n.Node               ] [DESKTOP-C93E9FL] node name [DESKTOP-C93E9FL], node ID [BpA0Gp1JRs6U3wbkepaLzQ]
[2018-06-26T11:39:21,441][INFO ][o.e.n.Node               ] [DESKTOP-C93E9FL] version[6.3.0], pid[30664], build[unknown/unknown/424e937/2018-06-11T23:38:03.357887Z], OS[Windows 10/10.0/amd64], JVM[Oracle Corporation/Java HotSpot(TM) 64-Bit Server VM/1.8.0_171/25.171-b11]
[2018-06-26T11:39:21,441][INFO ][o.e.n.Node               ] [DESKTOP-C93E9FL] JVM arguments [-XX:+UseConcMarkSweepGC, -XX:CMSInitiatingOccupancyFraction=75, -XX:+UseCMSInitiatingOccupancyOnly, -XX:+AlwaysPreTouch, -Xss1m, -Djava.awt.headless=true, -Dfile.encoding=UTF-8, -Djna.nosys=true, -XX:-OmitStackTraceInFastThrow, -Dio.netty.noUnsafe=true, -Dio.netty.noKeySetOptimization=true, -Dio.netty.recycler.maxCapacityPerThread=0, -Dlog4j.shutdownHookEnabled=false, -Dlog4j2.disable.jmx=true, -Djava.io.tmpdir=C:\Users\joshu\AppData\Local\Temp\elasticsearch, -XX:+HeapDumpOnOutOfMemoryError, -XX:HeapDumpPath=data, -XX:ErrorFile=logs/hs_err_pid%p.log, -XX:+PrintGCDetails, -XX:+PrintGCDateStamps, -XX:+PrintTenuringDistribution, -XX:+PrintGCApplicationStoppedTime, -Xloggc:logs/gc.log, -XX:+UseGCLogFileRotation, -XX:NumberOfGCLogFiles=32, -XX:GCLogFileSize=64m, -Xmx2048m, -Xms2048m, -Delasticsearch, -Des.path.home=C:\Program Files\Elastic\Elasticsearch\6.3.0, -Des.path.conf=C:\ProgramData\Elastic\Elasticsearch\config]
Java HotSpot(TM) 64-Bit Server VM warning: Cannot open file logs/gc.log due to No such file or directory

[2018-06-26T11:39:28,419][INFO ][o.e.p.PluginsService     ] [DESKTOP-C93E9FL] loaded module [aggs-matrix-stats]

Below is Kibana log

  log   [15:40:45.925] [warning][reporting] Generating a random key for xpack.reporting.encryptionKey. To prevent pending reports from failing on restart, please set xpack.reporting.encryptionKey in kibana.yml
  log   [15:40:45.934] [info][status][plugin:reporting@6.3.0] Status changed from uninitialized to yellow - Waiting for Elasticsearch
  log   [15:40:46.124] [error][status][plugin:xpack_main@6.3.0] Status changed from yellow to red - Request Timeout after 3000ms
  log   [15:40:46.135] [error][status][plugin:searchprofiler@6.3.0] Status changed from yellow to red - Request Timeout after 3000ms
  log   [15:40:46.138] [error][status][plugin:ml@6.3.0] Status changed from yellow to red - Request Timeout after 3000ms
  log   [15:40:46.138] [error][status][plugin:tilemap@6.3.0] Status changed from yellow to red - Request Timeout after 3000ms
  log   [15:40:46.139] [error][status][plugin:watcher@6.3.0] Status changed from yellow to red - Request Timeout after 3000ms
  log   [15:40:46.141] [error][status][plugin:index_management@6.3.0] Status changed from yellow to red - Request Timeout after 3000ms
  log   [15:40:46.142] [error][status][plugin:graph@6.3.0] Status changed from yellow to red - Request Timeout after 3000ms
  log   [15:40:46.143] [error][status][plugin:security@6.3.0] Status changed from yellow to red - Request Timeout after 3000ms
  log   [15:40:46.144] [error][status][plugin:grokdebugger@6.3.0] Status changed from yellow to red - Request Timeout after 3000ms
  log   [15:40:46.146] [error][status][plugin:logstash@6.3.0] Status changed from yellow to red - Request Timeout after 3000ms
  log   [15:40:46.148] [error][status][plugin:reporting@6.3.0] Status changed from yellow to red - Request Timeout after 3000ms
  log   [15:40:46.150] [error][status][plugin:elasticsearch@6.3.0] Status changed from yellow to red - Request Timeout after 3000ms
  log   [15:40:46.154] [info][listening] Server running at http://localhost:5601
  log   [15:40:46.198] [info][license][xpack] Imported license information from Elasticsearch for the [data] cluster: mode: trial | status: active | expiry date: 2018-07-17T09:14:08-04:00
  log   [15:40:46.234] [info][status][plugin:xpack_main@6.3.0] Status changed from red to green - Ready
  log   [15:40:46.235] [info][status][plugin:searchprofiler@6.3.0] Status changed from red to green - Ready
  log   [15:40:46.236] [info][status][plugin:ml@6.3.0] Status changed from red to green - Ready
  log   [15:40:46.237] [info][status][plugin:tilemap@6.3.0] Status changed from red to green - Ready
  log   [15:40:46.238] [info][status][plugin:watcher@6.3.0] Status changed from red to green - Ready
  log   [15:40:46.239] [info][status][plugin:index_management@6.3.0] Status changed from red to green - Ready
  log   [15:40:46.240] [info][status][plugin:graph@6.3.0] Status changed from red to green - Ready
  log   [15:40:46.241] [info][status][plugin:security@6.3.0] Status changed from red to green - Ready
  log   [15:40:46.242] [info][status][plugin:grokdebugger@6.3.0] Status changed from red to green - Ready
  log   [15:40:46.242] [info][status][plugin:logstash@6.3.0] Status changed from red to green - Ready
  log   [15:40:46.243] [info][status][plugin:reporting@6.3.0] Status changed from red to green - Ready
  log   [15:40:46.253] [info][kibana-monitoring][monitoring-ui] Stopping all Kibana monitoring collectors
  log   [15:40:46.269] [info][license][xpack] Imported license information from Elasticsearch for the [monitoring] cluster: mode: trial | status: active | expiry date: 2018-07-17T09:14:08-04:00
  log   [15:40:48.770] [info][kibana-monitoring][monitoring-ui] Starting all Kibana monitoring collectors
  log   [15:40:48.774] [info][status][plugin:elasticsearch@6.3.0] Status changed from red to green - Ready!


Data can not be indexed
(Kevin) #5

I am getting the same on a new install on Windows , Kibana and elasticsearch version 6.3.0.


(system) #6

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