Showing Kibana server is not ready yet

HI ,

My elasticsearch is running fine in port 9200 but my kibana port 5601 is showing Kibana server is not ready yet and im so clueless where it went wrong please help me solve it.

output of port number 9200

name "gEhnJDv"
cluster_name "elasticsearch"
cluster_uuid "MQrTdpUpSYGaCejIVoaZ9w"
version
number "6.6.0"
build_flavor "default"
build_type "deb"
build_hash "a9861f4"
build_date "2019-01-24T11:27:09.439740Z"
build_snapshot false
lucene_version "7.6.0"
minimum_wire_compatibility_version "5.6.0"
minimum_index_compatibility_version "5.0.0"
tagline "You Know, for Search"

kibana.yml

server.port: 5601
#server.host: "localhost"
#server.basePath: ""
#server.rewriteBasePath: false
#server.maxPayloadBytes: 1048576
#server.name: "your-hostname"
elasticsearch.hosts: ["http://localhost:9200"]
#elasticsearch.preserveHost: true
#kibana.index: ".kibana
#kibana.defaultAppId: "home"
#elasticsearch.username: "user"
#elasticsearch.password: "pass"
#server.ssl.enabled: false
#server.ssl.certificate: /path/to/your/server.crt
#server.ssl.key: /path/to/your/server.key
#elasticsearch.ssl.certificate: /path/to/your/client.crt
#elasticsearch.ssl.key: /path/to/your/client.key
#elasticsearch.ssl.certificateAuthorities: [ "/path/to/your/CA.pem" ]
#elasticsearch.ssl.verificationMode: full
#elasticsearch.pingTimeout: 1500
#elasticsearch.requestTimeout: 30000
#elasticsearch.requestHeadersWhitelist: [ authorization ]
#elasticsearch.customHeaders: {}
#elasticsearch.shardTimeout: 30000
#elasticsearch.startupTimeout: 5000
#elasticsearch.logQueries: false
#pid.file: /var/run/kibana.pid
#logging.dest: stdout
#logging.silent: false
#logging.quiet: false
#logging.verbose: false
#ops.interval: 5000
#i18n.locale: "en"

logs of kibana
/var/lib/kibana/kibana.stderr

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 process._tickCallback (internal/process/next_tick.js:61:11)
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 process._tickCallback (internal/process/next_tick.js:61:11)
Error: EACCES: permission denied, open '/usr/share/kibana/optimize/.babelcache.json'
at Object.openSync (fs.js:436:3)
at Object.writeFileSync (fs.js:1187:35)
at save (/usr/share/kibana/node_modules/babel-register/lib/cache.js:48:16)
at process._tickCallback (internal/process/next_tick.js:61:11)
at Function.Module.runMain (internal/modules/cjs/loader.js:744:11)
at startup (internal/bootstrap/node.js:285:19)
at bootstrapNodeJSCore (internal/bootstrap/node.js:739:3)
fs.js:115
throw err;
^
)

logs inside
/var/lib/kibana/kibana.stdout

{"type":"log","@timestamp":"2019-02-12T10:10:57+00:00","tags":["status","plugin:kibana","info"],"pid":9740,"name":"plugin:kibana","state":"green","message":"Status changed from uninitialized to green - Ready","prevState":"uninitialized","prevMsg":"uninitialized"}
{"type":"log","@timestamp":"2019-02-12T10:10:57+00:00","tags":["status","plugin:elasticsearch","info"],"pid":9740,"name":"plugin:elasticsearch","state":"yellow","message":"Status changed from uninitialized to yellow - Waiting for Elasticsearch","prevState":"uninitialized","prevMsg":"uninitialized"}
{"type":"log","@timestamp":"2019-02-12T10:10:57+00:00","tags":["status","plugin:kbn_vislib_vis_types","info"],"pid":9740,"name":"plugin:kbn_vislib_vis_types","state":"green","message":"Status changed from uninitialized to green - Ready","prevState":"uninitialized","prevMsg":"uninitialized"}
{"type":"log","@timestamp":"2019-02-12T10:10:57+00:00","tags":

how are you trying to run kibana ?

I run kibana using command
sudo service kibana start
and please can i know how these are related whats the connection between error i got and how i run kibana

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