[Resolved][Kibana7.0.1] Error occurs " Request Timeout after 30000ms" when starting kibana

Elastic Stack Logstash
1

Hi Team,

I was running into below error when starting kibana, and ES side has no error and exception.

 log   [06:49:29.171] [info][status][plugin:spaces@7.0.1] Status changed from yellow to green - Ready
 error  [06:49:57.442] [warning][process] UnhandledPromiseRejectionWarning: Error: Request Timeout after 30000ms
    at C:\elkstack\kibana-7.0.1-windows-x86_64\kibana-7.0.1-windows-x86_64\node_modules\elasticsearch\src\lib\transport.js:355:15
    at Timeout.<anonymous> (C:\elkstack\kibana-7.0.1-windows-x86_64\kibana-7.0.1-windows-x86_64\node_modules\elasticsearch\src\lib\transport.js:384:7)
    at ontimeout (timers.js:436:11)
    at tryOnTimeout (timers.js:300:5)
    at listOnTimeout (timers.js:263:5)
    at Timer.processTimers (timers.js:223:10)
    at emitWarning (internal/process/promises.js:81:15)
    at emitPromiseRejectionWarnings (internal/process/promises.js:120:9)
    at process._tickCallback (internal/process/next_tick.js:69:34)
 error  [06:49:57.460] [warning][process] Error: Request Timeout after 30000ms
    at C:\elkstack\kibana-7.0.1-windows-x86_64\kibana-7.0.1-windows-x86_64\node_modules\elasticsearch\src\lib\transport.js:355:15
    at Timeout.<anonymous> (C:\elkstack\kibana-7.0.1-windows-x86_64\kibana-7.0.1-windows-x86_64\node_modules\elasticsearch\src\lib\transport.js:384:7)
    at ontimeout (timers.js:436:11)
    at tryOnTimeout (timers.js:300:5)
    at listOnTimeout (timers.js:263:5)
    at Timer.processTimers (timers.js:223:10)

How to resolve it? Any other information needed, please let me know.

2

What is the output of the ‘_cluster/health’ api in Elasticsearch?

3

@Christian_Dahlqvist, here's the response. I found the same error occurs when deleting the index from Kibana -> Management-> Index Management

{
  "cluster_name" : "elasticsearch",
  "status" : "yellow",
  "timed_out" : false,
  "number_of_nodes" : 1,
  "number_of_data_nodes" : 1,
  "active_primary_shards" : 21,
  "active_shards" : 21,
  "relocating_shards" : 0,
  "initializing_shards" : 0,
  "unassigned_shards" : 13,
  "delayed_unassigned_shards" : 0,
  "number_of_pending_tasks" : 1,
  "number_of_in_flight_fetch" : 0,
  "task_max_waiting_in_queue_millis" : 0,
  "active_shards_percent_as_number" : 61.76470588235294
}

And I found below warrning: does it matter?
`

log [08:44:58.841] [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

`

4

Add elasticsearch.requestTimeout : 90000 to your kibana.yml.
Refer below link to configure kibana

https://www.elastic.co/guide/en/kibana/current/settings.html

When using reporting you have to set xpack.reporting.encryptionKey in kibana.yml if not kibana will generate it randomly.

1 Like
5

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