Error Elasticsearch 6.2.4 + Kibana set up through Docker. Kibana LOGIN currently disabled?

Vannazux · April 24, 2018, 3:53am

I am trying to set up the last version of ELK 6.2.4 to test 6.x feature, the user security permission.

Basically, I went to Elasticsearch website and followed instructions downloading Elasticsearch through docker. I executed the docker command below with adding some other parameters:

docker run -p 32669:9200 -p 32670:9300 -e "discovery.type=single-node" --network=elastic -e ELASTICSEARCH_USERNAME=elastic -e ELASTIC_PASSWORD=MagicWord --name elasticsearchplat docker.elastic.co/elasticsearch/elasticsearch-platinum:6.2.4

My ElasticSearch seems to fail showing " update_mapping [doc]" problem and Kibana comes up in a screen telling login screen is currently disabled.

Below is the message from Elasticsearch where seems to be the problem. Anyone knows how to fix this?

...
.....
[2018-04-24T03:41:58,281][INFO ][o.e.p.PluginsService     ] [SZiPBkC] loaded plugin [ingest-user-agent]
[2018-04-24T03:41:58,281][INFO ][o.e.p.PluginsService     ] [SZiPBkC] loaded plugin [x-pack-core]
[2018-04-24T03:41:58,282][INFO ][o.e.p.PluginsService     ] [SZiPBkC] loaded plugin [x-pack-deprecation]
[2018-04-24T03:41:58,282][INFO ][o.e.p.PluginsService     ] [SZiPBkC] loaded plugin [x-pack-graph]
[2018-04-24T03:41:58,282][INFO ][o.e.p.PluginsService     ] [SZiPBkC] loaded plugin [x-pack-logstash]
[2018-04-24T03:41:58,282][INFO ][o.e.p.PluginsService     ] [SZiPBkC] loaded plugin [x-pack-ml]
[2018-04-24T03:41:58,283][INFO ][o.e.p.PluginsService     ] [SZiPBkC] loaded plugin [x-pack-monitoring]
[2018-04-24T03:41:58,283][INFO ][o.e.p.PluginsService     ] [SZiPBkC] loaded plugin [x-pack-security]
[2018-04-24T03:41:58,283][INFO ][o.e.p.PluginsService     ] [SZiPBkC] loaded plugin [x-pack-upgrade]
[2018-04-24T03:41:58,283][INFO ][o.e.p.PluginsService     ] [SZiPBkC] loaded plugin [x-pack-watcher]
[2018-04-24T03:42:02,734][INFO ][o.e.x.m.j.p.l.CppLogMessageHandler] [controller/178] [Main.cc@128] controller (64 bit): Version 6.2.4 (Build 524e7fe231abc1) Copyright (c) 2018 Elasticsearch BV
[2018-04-24T03:42:04,794][INFO ][o.e.d.DiscoveryModule    ] [SZiPBkC] using discovery type [single-node]
[2018-04-24T03:42:05,907][INFO ][o.e.n.Node               ] initialized
[2018-04-24T03:42:05,907][INFO ][o.e.n.Node               ] [SZiPBkC] starting ...
[2018-04-24T03:42:06,122][INFO ][o.e.t.TransportService   ] [SZiPBkC] publish_address {172.18.0.2:9300}, bound_addresses {0.0.0.0:9300}
[2018-04-24T03:42:06,251][INFO ][o.e.x.s.t.n.SecurityNetty4HttpServerTransport] [SZiPBkC] publish_address {172.18.0.2:9200}, bound_addresses {0.0.0.0:9200}
[2018-04-24T03:42:06,252][INFO ][o.e.n.Node               ] [SZiPBkC] started
[2018-04-24T03:42:06,417][INFO ][o.e.g.GatewayService     ] [SZiPBkC] recovered [0] indices into cluster_state
[2018-04-24T03:42:07,135][INFO ][o.e.l.LicenseService     ] [SZiPBkC] license [a28ec707-f6c6-4ba6-b3ea-fd78ca4b6dd3] mode [trial] - valid
[2018-04-24T03:42:16,172][INFO ][o.e.c.m.MetaDataCreateIndexService] [SZiPBkC] [.monitoring-es-6-2018.04.24] creating index, cause [auto(bulk api)], templates [.monitoring-es], shards [1]/[0], mappings [doc]
[2018-04-24T03:42:16,503][INFO ][o.e.c.m.MetaDataCreateIndexService] [SZiPBkC] [.watches] creating index, cause [auto(bulk api)], templates [.watches], shards [1]/[0], mappings [doc]
[2018-04-24T03:42:16,669][INFO ][o.e.c.r.a.AllocationService] [SZiPBkC] Cluster health status changed from [YELLOW] to [GREEN] (reason: [shards started [[.monitoring-es-6-2018.04.24][0], [.watches][0]] ...]).
[2018-04-24T03:42:16,704][INFO ][o.e.x.w.WatcherService   ] [SZiPBkC] paused watch execution, reason [new local watcher shard allocation ids], cancelled [0] queued tasks
[2018-04-24T03:42:16,793][INFO ][o.e.c.m.MetaDataMappingService] [SZiPBkC] [.watches/N9JObdQDS3iDCr0ICqaBSg] update_mapping [doc]
[2018-04-24T03:42:16,848][INFO ][o.e.c.m.MetaDataMappingService] [SZiPBkC] [.watches/N9JObdQDS3iDCr0ICqaBSg] update_mapping [doc]
[2018-04-24T03:43:16,910][INFO ][o.e.c.m.MetaDataCreateIndexService] [SZiPBkC] [.triggered_watches] creating index, cause [auto(bulk api)], templates [.triggered_watches], shards [1]/[1], mappings [doc]
[2018-04-24T03:43:17,010][INFO ][o.e.c.m.MetaDataUpdateSettingsService] [SZiPBkC] updating number_of_replicas to [0] for indices [.triggered_watches]
[2018-04-24T03:43:17,041][INFO ][o.e.c.m.MetaDataUpdateSettingsService] [SZiPBkC] [.triggered_watches/8C3OZ5aFQG2FrMizjxwcjA] auto expanded replicas to [0]
[2018-04-24T03:43:17,089][INFO ][o.e.c.r.a.AllocationService] [SZiPBkC] Cluster health status changed from [YELLOW] to [GREEN] (reason: [shards started [[.triggered_watches][0]] ...]).
[2018-04-24T03:43:17,418][INFO ][o.e.c.m.MetaDataCreateIndexService] [SZiPBkC] [.watcher-history-7-2018.04.24] creating index, cause [auto(bulk api)], templates [.watch-history-7], shards [1]/[0], mappings [doc]
[2018-04-24T03:43:17,548][INFO ][o.e.c.r.a.AllocationService] [SZiPBkC] Cluster health status changed from [YELLOW] to [GREEN] (reason: [shards started [[.watcher-history-7-2018.04.24][0]] ...]).
[2018-04-24T03:43:17,640][INFO ][o.e.c.m.MetaDataMappingService] [SZiPBkC] [.watcher-history-7-2018.04.24/zaLjzMT2T3av9cxMwAXUDA] update_mapping [doc]
[2018-04-24T03:43:17,778][INFO ][o.e.c.m.MetaDataMappingService] [SZiPBkC] [.watcher-history-7-2018.04.24/zaLjzMT2T3av9cxMwAXUDA] update_mapping [doc]![Capture|690x378]

Attached also a screen from Kibana, which seems not to be able to reach Elasticsearch or nable login

nandan_bigdata · April 24, 2018, 3:54am

Are you using Docker ?

Vannazux · April 24, 2018, 4:02am

Yes, I am using Docker.

Vannazux · April 25, 2018, 1:39am

No one?

val · April 25, 2018, 5:56am

Below is the message from Elasticsearch where seems to be the problem. Anyone knows how to fix this?

There's no ERROR in your ES logs.

Attached also a screen from Kibana, which seems not to be able to reach Elasticsearch or nable login

How do you launch your Kibana instance? Via docker as well?

Vannazux · April 25, 2018, 2:58pm

Hi Val,

Yes, via docker.

I am the same person who posted the other POST in stackoverflow that you were checking the log.

In this POST here I was trying to use also the feature of the user roles security in Kibana. I used also Docker in this example through Powershell (win 10). The only difference here is that I executed ES and then Kibana one by one using docker command rather then docker-compose.

The other POST is a bit better detailed. I really needed the user security role feature. But no matter what I try works.

Vannazux · April 25, 2018, 3:11pm

If you run the docker compose files from the other POST, do you get the same results as I? Does the user security feature also doesn't work?

system · May 23, 2018, 3:11pm

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