Improve "port taken" type errors

[markwalkom]

This was raised here, we report a taken port as;

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' }

We should really make this a little nicer.

[prayagupa]

I'm having the same issue,

 /usr/local/kibana-5.3.0-linux-x86_64/bin/kibana
  log   [23:08:08.708] [info][status][plugin:[email protected]] Status changed from uninitialized to green - Ready
  log   [23:08:08.772] [info][status][plugin:[email protected]] Status changed from uninitialized to yellow - Waiting for Elasticsearch
  log   [23:08:08.794] [info][status][plugin:[email protected]] Status changed from uninitialized to green - Ready
  log   [23:08:08.825] [info][status][plugin:[email protected]] Status changed from yellow to green - Kibana index ready
  log   [23:08:08.960] [info][status][plugin:[email protected]] Status changed from uninitialized to green - Ready
  log   [23:08:08.966] [fatal] Error: listen EADDRNOTAVAIL 172.24.14.161:5601
    at Object.exports._errnoException (util.js:1022:11)
    at exports._exceptionWithHostPort (util.js:1045:20)
    at Server._listen2 (net.js:1246:19)
    at listen (net.js:1295:10)
    at net.js:1405:9
    at _combinedTickCallback (internal/process/next_tick.js:77:11)
    at process._tickCallback (internal/process/next_tick.js:98:9)
FATAL { Error: listen EADDRNOTAVAIL 172.24.14.161:5601
    at Object.exports._errnoException (util.js:1022:11)
    at exports._exceptionWithHostPort (util.js:1045:20)
    at Server._listen2 (net.js:1246:19)
    at listen (net.js:1295:10)
    at net.js:1405:9
    at _combinedTickCallback (internal/process/next_tick.js:77:11)
    at process._tickCallback (internal/process/next_tick.js:98:9)
  cause: 
   { Error: listen EADDRNOTAVAIL 172.24.14.161:5601
       at Object.exports._errnoException (util.js:1022:11)
       at exports._exceptionWithHostPort (util.js:1045:20)
       at Server._listen2 (net.js:1246:19)
       at listen (net.js:1295:10)
       at net.js:1405:9
       at _combinedTickCallback (internal/process/next_tick.js:77:11)
       at process._tickCallback (internal/process/next_tick.js:98:9)
     code: 'EADDRNOTAVAIL',
     errno: 'EADDRNOTAVAIL',
     syscall: 'listen',
     address: '172.24.14.161',
     port: 5601 },
  isOperational: true,
  code: 'EADDRNOTAVAIL',
  errno: 'EADDRNOTAVAIL',
  syscall: 'listen',
  address: '172.24.14.161',
  port: 5601 }

It says, ADDR NOT AVAIL but there no one running on 5601,

netstat -a -o | grep 5601

kibana.yml

# Kibana is served by a back end server. This setting specifies the port to use.
#server.port: 5601

# Specifies the address to which the Kibana server will bind. IP addresses and host names are both valid values.
# The default is 'localhost', which usually means remote machines will not be able to connect.
# To allow connections from remote users, set this parameter to a non-loopback address.
server.host: "172.24.14.161"

# Enables you to specify a path to mount Kibana at if you are running behind a proxy. This only affects
# the URLs generated by Kibana, your proxy is expected to remove the basePath value before forwarding requests
# to Kibana. This setting cannot end in a slash.
#server.basePath: ""

# The maximum payload size in bytes for incoming server requests.
#server.maxPayloadBytes: 1048576

# The Kibana server's name.  This is used for display purposes.
#server.name: "your-hostname"

# The URL of the Elasticsearch instance to use for all your queries.
elasticsearch.url: "http://172.24.41.161:9200"

Changing server.host:"127.0.0.1" works which is stupid because I need to access from outside.

[chenchurao]

/usr/local/kibana-5.3.0-linux-x86_64/bin/kibana
log [23:08:08.708] [info][status][plugin:[email protected]] Status changed from uninitialized to green - Ready
log [23:08:08.772] [info][status][plugin:[email protected]] Status changed from uninitialized to yellow - Waiting for Elasticsearch
log [23:08:08.794] [info][status][plugin:[email protected]] Status changed from uninitialized to green - Ready
log [23:08:08.825] [info][status][plugin:[email protected]] Status changed from yellow to green - Kibana index ready
log [23:08:08.960] [info][status][plugin:[email protected]] Status changed from uninitialized to green - Ready
log [23:08:08.966] [fatal] Error: listen EADDRNOTAVAIL 172.24.14.161:5601
at Object.exports._errnoException (util.js:1022:11)
at exports._exceptionWithHostPort (util.js:1045:20)
at Server._listen2 (net.js:1246:19)
at listen (net.js:1295:10)
at net.js:1405:9
at _combinedTickCallback (internal/process/next_tick.js:77:11)
at process._tickCallback (internal/process/next_tick.js:98:9)
FATAL { Error: listen EADDRNOTAVAIL 172.24.14.161:5601
at Object.exports._errnoException (util.js:1022:11)
at exports._exceptionWithHostPort (util.js:1045:20)
at Server._listen2 (net.js:1246:19)
at listen (net.js:1295:10)
at net.js:1405:9
at _combinedTickCallback (internal/process/next_tick.js:77:11)
at process._tickCallback (internal/process/next_tick.js:98:9)
cause:
{ Error: listen EADDRNOTAVAIL 172.24.14.161:5601
at Object.exports._errnoException (util.js:1022:11)
at exports._exceptionWithHostPort (util.js:1045:20)
at Server._listen2 (net.js:1246:19)
at listen (net.js:1295:10)
at net.js:1405:9
at _combinedTickCallback (internal/process/next_tick.js:77:11)
at process._tickCallback (internal/process/next_tick.js:98:9)
code: 'EADDRNOTAVAIL',
errno: 'EADDRNOTAVAIL',
syscall: 'listen',
address: '172.24.14.161',
port: 5601 },
isOperational: true,
code: 'EADDRNOTAVAIL',
errno: 'EADDRNOTAVAIL',
syscall: 'listen',
address: '172.24.14.161',
port: 5601 }

i am also find same error can u please guide me any one.

[chenchurao]

log [07:33:29.069] [fatal] Error: listen EADDRNOTAVAIL 52.66.132.152:5602
at Object.exports._errnoException (util.js:1018:11)
at exports._exceptionWithHostPort (util.js:1041:20)
at Server._listen2 (net.js:1249:19)
at listen (net.js:1298:10)
at net.js:1408:9
at _combinedTickCallback (internal/process/next_tick.js:83:11)
at process._tickCallback (internal/process/next_tick.js:104:9)
FATAL { Error: listen EADDRNOTAVAIL 52.66.132.152:5602
at Object.exports._errnoException (util.js:1018:11)
at exports._exceptionWithHostPort (util.js:1041:20)
at Server._listen2 (net.js:1249:19)
at listen (net.js:1298:10)
at net.js:1408:9
at _combinedTickCallback (internal/process/next_tick.js:83:11)
at process._tickCallback (internal/process/next_tick.js:104:9)
cause:
{ Error: listen EADDRNOTAVAIL 52.66.132.152:5602
at Object.exports._errnoException (util.js:1018:11)
at exports._exceptionWithHostPort (util.js:1041:20)
at Server._listen2 (net.js:1249:19)
at listen (net.js:1298:10)
at net.js:1408:9
at _combinedTickCallback (internal/process/next_tick.js:83:11)
at process._tickCallback (internal/process/next_tick.js:104:9)
code: 'EADDRNOTAVAIL',
errno: 'EADDRNOTAVAIL',
syscall: 'listen',
address: '52.66.132.152',
port: 5602 },
isOperational: true,
code: 'EADDRNOTAVAIL',
errno: 'EADDRNOTAVAIL',
syscall: 'listen',
address: '52.66.132.152',
port: 5602 }
I am facing This Issue Can U please guide Me ony one

[prayagupa]

@chenchurao what is your elasticsearch config? Sorry I forgot to update that I made it working by setting full permission to the kibana package, which is weird but it did work.

sudo chmod -R 777 /usr/local/kibana-5.3.0-linux-x86_64

[sdeepanshu02]

@prayagupd It's still not working. Does it have something to do with nginx beacause it was working for me before. But after I installed nginx Kibana stopped working with error message "listen EADDRNOTAVAIL"

[jbudz]

Here's a current example:

Error: listen EADDRINUSE: address already in use 127.0.0.1:5601
    at Server.setupListenHandle [as _listen2] (net.js:1318:16)
    at listenInCluster (net.js:1366:12)
    at GetAddrInfoReqWrap.doListen (net.js:1503:7)
    at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:69:8) {
  code: 'EADDRINUSE',
  errno: -98,
  syscall: 'listen',
  address: '127.0.0.1',
  port: 5601
}

I'm going to close this out - no comments in 3 years. We can reopen if there's still concerns around the messaging.