Kibana showing error

Elastic Stack Kibana
1

Hi,

I've installed kibana on linux. i've assign 5601 port as external host(log.gurukul.ninja).
but when i run ./bin/kibana command in linux putty terminal i got this error.

  log   [03:03:35.042] [warning][plugins-discovery] Expect plugin "id" in camelCase, but found: beats_management
  log   [03:03:35.053] [warning][plugins-discovery] Expect plugin "id" in camelCase, but found: triggers_actions_ui
  log   [03:03:42.629] [info][plugins-service] Plugin "visTypeXy" is disabled.
  log   [03:03:42.630] [info][plugins-service] Plugin "auditTrail" is disabled.
  log   [03:03:42.871] [warning][config][deprecation] Config key [monitoring.cluster_alerts.email_notifications.email_address] will be required for email notifications to work in 8.0."
  log   [03:03:43.044] [fatal][root] { Error: listen EADDRNOTAVAIL: address not available 175.101.13.126:5601
    at Server.setupListenHandle [as _listen2] (net.js:1263:19)
    at listenInCluster (net.js:1328:12)
    at GetAddrInfoReqWrap.doListen (net.js:1461:7)
    at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:61:10)
  code: 'EADDRNOTAVAIL',
  errno: 'EADDRNOTAVAIL',
  syscall: 'listen',
  address: '175.101.13.126',
  port: 5601 }

Thank you !

2

This means some other process is already occupying port 5601 - make sure no other instance of Kibana (or another tool using this port) is running

3

but i've assigned port 5601 as log.gurukul.ninja(175.101.13.126).
so am i doing wrong or what?

4

but i've assigned port 5601 as log.gurukul.ninja(175.101.13.126).

I'm not sure what you mean by that. Can you elaborate?

5

i installed kibana on linux server.
i decalred or assigned localhost:5601 to 175.101.13.126:5601 which is my Ip address it host is log.gurukul.ninja.so when i open it on browser i want to see kibana dashboard.

6

To be more precise: What steps exactly did you perform to "assign" localhost:5601 to your IP? It seems like you are running a web server or something which is not necessary - Kibana is its own webserver. It seems like your problem is related to your server configuration, not Kibana itself.

7

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