Start the kibana failed


(tianzongqi) #1

when i started the kibana, some error print then failed.

the error info is :
> > log [11:08:33.221] [info][status][plugin:kibana] Status changed from uninitialized to green - Ready > log [11:08:33.256] [info][status][plugin:elasticsearch] Status changed from uninitialized to yellow - Waiting for Elasticsearch > log [11:08:33.274] [info][status][plugin:marvel] Status changed from uninitialized to yellow - Waiting for Elasticsearch > log [11:08:33.296] [info][status][plugin:kbn_vislib_vis_types] Status changed from uninitialized to green - Ready > log [11:08:33.301] [info][status][plugin:markdown_vis] Status changed from uninitialized to green - Ready > log [11:08:33.304] [info][status][plugin:metric_vis] Status changed from uninitialized to green - Ready > log [11:08:33.317] [info][status][plugin:spyModes] Status changed from uninitialized to green - Ready > log [11:08:33.482] [info][status][plugin:statusPage] Status changed from uninitialized to green - Ready > log [11:08:33.487] [info][status][plugin:table_vis] Status changed from uninitialized to green - Ready > log [11:08:33.501] [fatal] Error: listen EACCES > at exports._errnoException (util.js:746:11) > at Server._listen2 (net.js:1141:19) > at listen (net.js:1184:10) > at net.js:1282:9 > at dns.js:85:18 > at process._tickDomainCallback (node.js:381:11) > FATAL { [Error: listen EACCES] > cause: { [Error: listen EACCES] code: 'EACCES', errno: 'EACCES', syscall: 'listen' }, > isOperational: true, > code: 'EACCES', > errno: 'EACCES', > syscall: 'listen' }

what's the probleam? how can i handle this? thank you


(tianzongqi) #2

I find the reason.

the server port is used by other application, so caused the above error.

modify the kabana port, then start success


(Mark Walkom) #3

We can definitely make that error more readable!
I've raised https://github.com/elastic/kibana/issues/6064 to get that fixed :slight_smile:


(Allie Yang Yang) #4

Hi How did you fixed it?

I changed multiple port number, it is all showing same errors...


(system) #5