Kibana is running inside the server but Kibana UI is not working


(sasank) #1

Hi,
I installed Kibana version 6.2.2 three months back it is up and running and the UI monitoring is also working fine but suddenly UI is not working now. Kibana is running inside the server but can't browse the URL (Kibana UI not responding) Can you please help me to reslove this issuse.

Please find the logs below

log [02:00:20.223] [info][status][plugin:license_management@6.2.2] Status changed from uninitialized to green - Ready
log [02:00:20.440] [info][status][plugin:timelion@6.2.2] Status changed from uninitialized to green - Ready
log [02:00:20.446] [info][status][plugin:graph@6.2.2] Status changed from uninitialized to yellow - Waiting for Elasticsearch
log [02:00:20.457] [info][status][plugin:monitoring@6.2.2] Status changed from uninitialized to green - Ready
log [02:00:21.553] [info][status][plugin:reporting@6.2.2] Status changed from uninitialized to yellow - Waiting for Elasticsearch
log [02:00:21.602] [info][status][plugin:security@6.2.2] Status changed from uninitialized to yellow - Waiting for Elasticsearch
log [02:00:21.603] [warning][security] Session cookies will be transmitted over insecure connections. This is not recommended.
log [02:00:21.675] [info][status][plugin:grokdebugger@6.2.2] Status changed from uninitialized to green - Ready
log [02:00:21.693] [info][status][plugin:dashboard_mode@6.2.2] Status changed from uninitialized to green - Ready
log [02:00:21.699] [info][status][plugin:logstash@6.2.2] Status changed from uninitialized to yellow - Waiting for Elasticsearch
log [02:00:21.751] [info][status][plugin:apm@6.2.2] Status changed from uninitialized to green - Ready
log [02:00:21.767] [info][status][plugin:console@6.2.2] Status changed from uninitialized to green - Ready
log [02:00:21.776] [info][status][plugin:metrics@6.2.2] Status changed from uninitialized to green - Ready
log [02:00:21.791] [info][listening] Server running at http://xx

.xxx.xxx.xx:5601
log [02:00:21.935] [info][status][plugin:elasticsearch@6.2.2] Status changed from yellow to green - Ready
log [02:00:21.961] [info][license][xpack] Imported license information from Elasticsearch for the [data] cluster: mode: gold | status: active | expiry date: 2019-09-30T23:59:59+00:00
log [02:00:21.970] [info][status][plugin:xpack_main@6.2.2] Status changed from yellow to green - Ready
log [02:00:21.970] [info][status][plugin:searchprofiler@6.2.2] Status changed from yellow to green - Ready
log [02:00:21.971] [info][status][plugin:ml@6.2.2] Status changed from yellow to green - Ready
log [02:00:21.971] [info][status][plugin:tilemap@6.2.2] Status changed from yellow to green - Ready
log [02:00:21.973] [info][status][plugin:watcher@6.2.2] Status changed from yellow to green - Ready
log [02:00:21.974] [info][status][plugin:graph@6.2.2] Status changed from yellow to green - Ready
log [02:00:21.975] [info][status][plugin:reporting@6.2.2] Status changed from yellow to green - Ready
log [02:00:21.976] [info][status][plugin:security@6.2.2] Status changed from yellow to green - Ready
log [02:00:21.976] [info][status][plugin:logstash@6.2.2] Status changed from yellow to green - Ready
log [02:00:21.993] [info][kibana-monitoring][monitoring-ui] Starting all Kibana monitoring collectors
log [02:00:27.443] [error][status][plugin:xpack_main@6.2.2] Status changed from green to red - Request Timeout after 3000ms
log [02:00:27.445] [error][status][plugin:searchprofiler@6.2.2] Status changed from green to red - Request Timeout after 3000ms
log [02:00:27.446] [error][status][plugin:ml@6.2.2] Status changed from green to red - Request Timeout after 3000ms
log [02:00:27.447] [error][status][plugin:tilemap@6.2.2] Status changed from green to red - Request Timeout after 3000ms
log [02:00:27.448] [error][status][plugin:watcher@6.2.2] Status changed from green to red - Request Timeout after 3000ms
log [02:00:27.449] [error][status][plugin:graph@6.2.2] Status changed from green to red - Request Timeout after 3000ms
log [02:00:27.449] [error][status][plugin:reporting@6.2.2] Status changed from green to red - Request Timeout after 3000ms
log [02:00:27.450] [error][status][plugin:security@6.2.2] Status changed from green to red - Request Timeout after 3000ms
log [02:00:27.450] [error][status][plugin:logstash@6.2.2] Status changed from green to red - Request Timeout after 3000ms
log [02:00:27.451] [info][kibana-monitoring][monitoring-ui] Stopping all Kibana monitoring collectors
log [02:00:27.452] [error][status][plugin:elasticsearch@6.2.2] Status changed from green to red - Request Timeout after 3000ms
log [02:00:51.979] [warning][license][xpack] License information from the X-Pack plugin could not be obtained from Elasticsearch for the [monitoring] cluster. Error: Request Timeout after 30000ms
log [02:00:51.982] [warning][monitoring-ui] X-Pack Monitoring Cluster Alerts will not be available: Error: Request Timeout after 30000ms
log [02:00:52.007] [info][kibana-monitoring][monitoring-ui] Starting all Kibana monitoring collectors
log [02:00:52.015] [info][status][plugin:elasticsearch@6.2.2] Status changed from red to green - Ready
log [02:00:52.048] [info][status][plugin:xpack_main@6.2.2] Status changed from red to green - Ready
log [02:00:52.049] [info][status][plugin:searchprofiler@6.2.2] Status changed from red to green - Ready
log [02:00:52.050] [info][status][plugin:ml@6.2.2] Status changed from red to green - Ready
log [02:00:52.050] [info][status][plugin:tilemap@6.2.2] Status changed from red to green - Ready
log [02:00:52.051] [info][status][plugin:watcher@6.2.2] Status changed from red to green - Ready
log [02:00:52.051] [info][status][plugin:graph@6.2.2] Status changed from red to green - Ready
log [02:00:52.052] [info][status][plugin:reporting@6.2.2] Status changed from red to green - Ready
log [02:00:52.054] [info][status][plugin:security@6.2.2] Status changed from red to green - Ready
log [02:00:52.054] [info][status][plugin:logstash@6.2.2] Status changed from red to green - Ready
log [02:01:22.002] [info][license][xpack] Imported license information from Elasticsearch for the [monitoring] cluster: mode: gold | status: active | expiry date: 2019-09-30T23:59:59+00:00


(Tim Roes) #2

Hi,

could you please clarify what you mean by the UI is not working. Can you execute a curl -v against the URL of your Kibana, and post the output here?

Cheers,
Tim


(sasank) #3
  • About to connect() to xx.xxx.xxx.xx port 5601 (#0)

  • Trying xx.xxx.xxx.xx...

  • Connected to xx.xxx.xxx.xx (xx.xxx.xxx.xx) port 5601 (#0)

> GET / HTTP/1.1

> User-Agent: curl/7.29.0

> Host: xx.xxx.xxx.xx:5601

> Accept: /

>

< HTTP/1.1 302 Found

< location: /login?next=%2F

< kbn-name: kibana

< kbn-version: 6.2.2

< kbn-xpack-sig: 96a861687dbbfe2edcd0022b4452b299

< cache-control: no-cache

< content-length: 0

< Date: Fri, 18 Jan 2019 22:27:08 GMT

< Connection: keep-alive

<

  • Connection #0 to xx.xxx.xxx.xx left intact

I can not able to browse the URL of Kibana


(sasank) #4

Hi Timroes,
Thanks for your response.. I execute a curl -v against the URL of kibana and posted here. I installed and configure kibana three months back it is working fine but suddenly i am not able to hit kibana URL (UI Web Page)
can you please help me to solve this problem..

Thanks


(Tim Roes) #5

Could you please execute another curl -v -L <url>, to follow the redirect. Also maybe it's worth clearing your browsers cache or trying a different browser to see if you're able to access it.

Also just to make sure: You're executing curl from the very same machine, you are trying to access it via the browser?

Usually when Kibana "suddenly" is not accessible anymore, in most cases I've seen, something changed in your infrastructure (proxies started working differently, reverse proxies had changed behavior, cloud routing changed, etc.)

Cheers,
Tim


(system) closed #6

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