Kibana/Kibi no errors but cant acess remotely


#1

Hey,

i just upgraded to ElasticSearch 5.0 and then i did a new instalation of kibana 5 (before i was using kibi). Everything runs with no problem. I see that the old data from previous elasticsearch installation is there but i cant open kibana webpage. :confused:

Kibana logs:

# ./kibana
  log   [11:07:10.373] [info][status][plugin:kibana@5.0.1] Status changed from uninitialized to green - Ready
  log   [11:07:10.471] [info][status][plugin:elasticsearch@5.0.1] Status changed from uninitialized to yellow - Waiting for Elasticsearch
  log   [11:07:10.529] [info][status][plugin:console@5.0.1] Status changed from uninitialized to green - Ready
  log   [11:07:10.555] [info][status][plugin:elasticsearch@5.0.1] Status changed from yellow to green - Kibana index ready
  log   [11:07:10.816] [info][status][plugin:timelion@5.0.1] Status changed from uninitialized to green - Ready
  log   [11:07:10.823] [info][listening] Server running at http://localhost:5601
  log   [11:07:10.825] [info][status][ui settings] Status changed from uninitialized to green - Ready

ElasticSearch logs:

[2016-11-22T11:03:04,335][INFO ][o.e.p.PluginsService     ] [SdQTW7R] loaded module [aggs-matrix-stats]
[2016-11-22T11:03:04,335][INFO ][o.e.p.PluginsService     ] [SdQTW7R] loaded module [ingest-common]
[2016-11-22T11:03:04,335][INFO ][o.e.p.PluginsService     ] [SdQTW7R] loaded module [lang-expression]
[2016-11-22T11:03:04,335][INFO ][o.e.p.PluginsService     ] [SdQTW7R] loaded module [lang-groovy]
[2016-11-22T11:03:04,335][INFO ][o.e.p.PluginsService     ] [SdQTW7R] loaded module [lang-mustache]
[2016-11-22T11:03:04,335][INFO ][o.e.p.PluginsService     ] [SdQTW7R] loaded module [lang-painless]
[2016-11-22T11:03:04,335][INFO ][o.e.p.PluginsService     ] [SdQTW7R] loaded module [percolator]
[2016-11-22T11:03:04,335][INFO ][o.e.p.PluginsService     ] [SdQTW7R] loaded module [reindex]
[2016-11-22T11:03:04,336][INFO ][o.e.p.PluginsService     ] [SdQTW7R] loaded module [transport-netty3]
[2016-11-22T11:03:04,336][INFO ][o.e.p.PluginsService     ] [SdQTW7R] loaded module [transport-netty4]
[2016-11-22T11:03:04,336][INFO ][o.e.p.PluginsService     ] [SdQTW7R] no plugins loaded
[2016-11-22T11:03:08,058][INFO ][o.e.n.Node               ] [SdQTW7R] initialized
[2016-11-22T11:03:08,058][INFO ][o.e.n.Node               ] [SdQTW7R] starting ...
[2016-11-22T11:03:08,301][INFO ][o.e.t.TransportService   ] [SdQTW7R] publish_address {127.0.0.1:9300}, bound_addresses {127.0.0.1:9300}
[2016-11-22T11:03:11,490][INFO ][o.e.c.s.ClusterService   ] [SdQTW7R] new_master {SdQTW7R}{SdQTW7RBQhSNyTlWIB6Z5A}{RmNCb-v7ThS2xRfwwVf78A}{127.0.0.1}{127.0.0.1:9300}, reason: zen-disco-elected-as-master ([0] nodes joined)
[2016-11-22T11:03:11,518][INFO ][o.e.h.HttpServer         ] [SdQTW7R] publish_address {127.0.0.1:9200}, bound_addresses {127.0.0.1:9200}
[2016-11-22T11:03:11,519][INFO ][o.e.n.Node               ] [SdQTW7R] started
[2016-11-22T11:03:11,997][INFO ][o.e.c.s.ClusterSettings  ] [SdQTW7R] updating [cluster.routing.allocation.enable] from [ALL] to [all]
[2016-11-22T11:03:12,089][INFO ][o.e.g.GatewayService     ] [SdQTW7R] recovered [5] indices into cluster_state
[2016-11-22T11:03:14,131][INFO ][o.e.c.r.a.AllocationService] [SdQTW7R] Cluster health status changed from [RED] to [YELLOW] (reason: [shards started [[.kibi][0]] ...]).
[2016-11-22T11:03:31,075][INFO ][o.e.m.j.JvmGcMonitorService] [SdQTW7R] [gc][23] overhead, spent [273ms] collecting in the last [1s]

ElasticSearch indices:

# curl 'localhost:9200/_cat/indices?v'
health status index    uuid                   pri rep docs.count docs.deleted store.size pri.store.size
yellow open   lsp-gc   Vak362nrQyCPduYJxpBq8w   5   1       6648            0        4mb            4mb
yellow open   tracy    arv6HedjQjaV3Flht3Ab7w   5   1    3597949            0      3.6gb          3.6gb
yellow open   .kibi    LrKdp9QTRCipnNE0Eu3lEQ   1   1         11            1     29.1kb         29.1kb
yellow open   .kibana  _XCFQfeoQSesRM-a-zR6rg   1   1          1            0      3.1kb          3.1kb
yellow open   lsp-heap T_GKNdYCTGyQtYKRUmziIQ   5   1    7146016            0      2.4gb          2.4gb

i try to open localhost:5601 but it cant connect to the webpage. Anyone knows whats wrong?


#3

so now i am able to access servers remotely like grafana for example. But still i cant acess servers like kibana or kibi.

i deleted everything and reinstalled 2.4 versions from scratch and still no good.

If i cant acess kibana nor kibi remotely, even though they are running with no errors, and the problem is not accessing servers remotely, what can be causing this problem?


(Jon Budzenski) #4

Kibana 5.0 binds to localhost by default now. Are you trying to access this externally? In your kibana.yml you may have to change server.host.


#5

I have a machine running ElasticSearch and Kibana. And i am trying to access kibana from another machine. Kibana is poiting to localhost:9200, everything is by default

Obviously i am not putting "localhost:5601" in my browser as i am in a different computer of kibana server


(Jon Budzenski) #6

Ah okay, you'll need to change your kibana.yml. In 4.x server.host was set to bind to all ipv4 addresses on your machine (0.0.0.0), and in 5.x kibana is set to be accessible from only from the machine running it by default. You'll need to bind to it to an address accessible by you. 0.0.0.0 should work but it's probably not what you want if your server is open to the internet.


#7

well it should work like you say. I am in a company so only the computers connected to the company network will be able to access this, which is perfectly ok.


(system) #8

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