Kibana canvas

Elastic Stack Kibana
1

I'm getting below error.
[BABEL] Note: The code generator has deoptimised the styling of "/usr/share/kibana/node_modules/x-pack/plugins/canvas/canvas_plugin/types/all.js" as it exceeds the max of "500KB".
Unhandled rejection Error: No Living connections
at sendReqWithConnection (/usr/share/kibana/node_modules/elasticsearch/src/lib/transport.js:226:15)
at next (/usr/share/kibana/node_modules/elasticsearch/src/lib/connection_pool.js:214:7)
at _combinedTickCallback (internal/process/next_tick.js:132:7)
at process._tickCallback (internal/process/next_tick.js:181:9)
Unhandled rejection Error: No Living connections
at sendReqWithConnection (/usr/share/kibana/node_modules/elasticsearch/src/lib/transport.js:226:15)
at next (/usr/share/kibana/node_modules/elasticsearch/src/lib/connection_pool.js:214:7)
at _combinedTickCallback (internal/process/next_tick.js:132:7)
at process._tickCallback (internal/process/next_tick.js:181:9)
[BABEL] Note: The code generator has deoptimised the styling of "/usr/share/kibana/node_modules/x-pack/plugins/canvas/canvas_plugin/functions/common/all.js" as it exceeds the max of "500KB".
[BABEL] Note: The code generator has deoptimised the styling of "/usr/share/kibana/node_modules/x-pack/plugins/canvas/canvas_plugin/functions/common/all.js" as it exceeds the max of "500KB".
Unhandled rejection Error: No Living connections
at sendReqWithConnection (/usr/share/kibana/node_modules/elasticsearch/src/lib/transport.js:226:15)
at next (/usr/share/kibana/node_modules/elasticsearch/src/lib/connection_pool.js:214:7)
at _combinedTickCallback (internal/process/next_tick.js:132:7)
at process._tickDomainCallback (internal/process/next_tick.js:219:9)
Unhandled rejection Error: No Living connections
at sendReqWithConnection (/usr/share/kibana/node_modules/elasticsearch/src/lib/transport.js:226:15)
at next (/usr/share/kibana/node_modules/elasticsearch/src/lib/connection_pool.js:214:7)
at _combinedTickCallback (internal/process/next_tick.js:132:7)
at process._tickDomainCallback (internal/process/next_tick.js:219:9)
Unhandled rejection Error: No Living connections
at sendReqWithConnection (/usr/share/kibana/node_modules/elasticsearch/src/lib/transport.js:226:15)
at next (/usr/share/kibana/node_modules/elasticsearch/src/lib/connection_pool.js:214:7)
at _combinedTickCallback (internal/process/next_tick.js:132:7)
at process._tickDomainCallback (internal/process/next_tick.js:219:9)
Unhandled rejection Error: No Living connections
at sendReqWithConnection (/usr/share/kibana/node_modules/elasticsearch/src/lib/transport.js:226:15)
at next (/usr/share/kibana/node_modules/elasticsearch/src/lib/connection_pool.js:214:7)
at _combinedTickCallback (internal/process/next_tick.js:132:7)
at process._tickDomainCallback (internal/process/next_tick.js:219:9)
Unhandled rejection Error: No Living connections
at sendReqWithConnection (/usr/share/kibana/node_modules/elasticsearch/src/lib/transport.js:226:15)
at next (/usr/share/kibana/node_modules/elasticsearch/src/lib/connection_pool.js:214:7)
at _combinedTickCallback (internal/process/next_tick.js:132:7)
at process._tickDomainCallback (internal/process/next_tick.js:219:9)
Unhandled rejection Error: No Living connections

2

@here I am getting above error. Please help me how to fix above . logstash,kibana and elasticsearch are running. But when I'm watch log in /var/log/kibana/kibana.stderr path.
Please help me how to fix......

3

Hey @balamelangi,

The main error here is that Kibana can't connect to Elasticsearch: No Living connections. The fact that Kibana crashes in this case is another smaller issue that is fixed in master already.

Make sure you can connect to Elasticsearch and Kibana is configured properly to access it too.

Best,
Oleg

4

@azasypkin Thanks for your replay. But my elasticsearch is running and I'm able to curl also, but from kibana side I'm unable to curl as well. The CURL message shows kibana is not ready.

Thanks,
Bala Melangi

5

@balamelangi, please turn on Kibana verbose logging --verbose and share it if possible or just try to find anything suspicious there by yourself. I'm pretty sure that there is some mistake in elasticsearch.* settings in kibana.yml.

Best,
Oleg

6

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