Kibana 7.0 startup error - getConnections has been called

[eduardovieira (Eduardo)]

Hello everyone!

I feel like I have a simple problem, but I am unable to fix it.

Whenever I try to start kibana, I get a timeout error. It seems like it is trying to connect to my elasticsearch instance but getting no response.

When I try to curl the elasticsearch destination from the kibana IP I get the standard answer.

Does anyone know how to fix it?

log [16:30:13.608] [debug][plugins] Initializing plugin timelion@kibana
log [16:30:13.785] [info][status][plugin:timelion@undefined] Status changed from uninitialized to green - Ready
log [16:30:13.786] [debug][plugins] Initializing plugin vega@kibana
log [16:30:13.808] [debug][plugin] Checking Elasticsearch version
log [16:30:13.815] [server][uuid][uuid] Resuming persistent Kibana instance UUID: 41fcb572-b653-4794-a845-1606f841acf8
log [16:30:13.820] [info][status][plugin:elasticsearch@undefined] Status changed from yellow to green - Ready
log [16:30:16.329] [debug][plugin] Checking Elasticsearch version
log [16:30:17.128] [debug][legacy-proxy] "getConnections" has been called.
log [16:30:18.835] [debug][plugin] Checking Elasticsearch version
log [16:30:21.344] [debug][plugin] Checking Elasticsearch version
log [16:30:22.129] [debug][legacy-proxy] "getConnections" has been called.
log [16:30:23.850] [debug][plugin] Checking Elasticsearch version
log [16:30:26.360] [debug][plugin] Checking Elasticsearch version
log [16:30:27.129] [debug][legacy-proxy] "getConnections" has been called.
log [16:30:28.868] [debug][plugin] Checking Elasticsearch version
log [16:30:31.381] [debug][plugin] Checking Elasticsearch version
log [16:30:32.131] [debug][legacy-proxy] "getConnections" has been called.
log [16:30:33.890] [debug][plugin] Checking Elasticsearch version
log [16:30:36.400] [debug][plugin] Checking Elasticsearch version
log [16:30:37.132] [debug][legacy-proxy] "getConnections" has been called.
log [16:30:38.908] [debug][plugin] Checking Elasticsearch version
log [16:30:41.418] [debug][plugin] Checking Elasticsearch version
log [16:30:42.133] [debug][legacy-proxy] "getConnections" has been called.
log [16:30:43.834] [debug][root] shutting root down
log [16:30:43.836] [fatal][root] { Error: Request Timeout after 30000ms
at /usr/share/kibana/node_modules/elasticsearch/src/lib/transport.js:355:15
at Timeout. (/usr/share/kibana/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)
status: undefined,
displayName: 'RequestTimeout',
message: 'Request Timeout after 30000ms',
body: undefined }
log [16:30:43.841] [debug][server] stopping server
log [16:30:43.842] [debug][legacy-service] stopping legacy service
log [16:30:43.842] [debug][plugins-service] Stopping plugins service
log [16:30:43.843] [debug][server][http] stopping http server
log [16:30:43.845] [debug][legacy-proxy] Event is being forwarded: close

FATAL Error: Request Timeout after 30000ms

[rashmi (kulkarni)]

@eduardovieira

getConnections" has been called.

Actually, we do create the Kibana index on start. If your seeing a Kibana is not ready message, more than likely it's due to Kibana not being able to connect to Elasticsearch. Are you seeing any Kibana logs related to this? Can you also check the proxy settings ? You can try and delete the optimize folder in the kibana folder and restarting Kibana. There have been improvements to not having the optimization process failing in Kibana.

THanks
Rashmi