# X-Pack was Installed for ES and Kibana

**URL:** <https://discuss.elastic.co/t/x-pack-was-installed-for-es-and-kibana/66316>\
**Category:** Kibana\
**Created:** [November 17, 2016, 1:18am UTC](https://discuss.elastic.co/t/x-pack-was-installed-for-es-and-kibana/66316 "2016-11-17T01:18:10Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![lester015](https://avatars.discourse-cdn.com/v4/letter/l/cc9497/32.png) [@lester015](https://discuss.elastic.co/u/lester015)\
**Post date:** [November 17, 2016, 1:18am UTC](https://discuss.elastic.co/t/x-pack-was-installed-for-es-and-kibana/66316/1 "2016-11-17T01:18:10Z")

</div>

Dear team,  
I flow the X-Pack 's install url  
[https://www.elastic.co/guide/en/x-pack/5.0/installing-xpack.html#xpack-installing-offline](https://www.elastic.co/guide/en/x-pack/5.0/installing-xpack.html#xpack-installing-offline)

```
   when I start the Es, it's throw an java UnsupportedOperationException, at the end of Es is running.as fallows:

```

[hadoop@elk-test-6 elasticsearch-5.0.1]$ bin/elasticsearch  
[2016-11-17T09:06:37,196][WARN][o.e.b.JNANatives] unable to install syscall filter:  
java.lang.UnsupportedOperationException: seccomp unavailable: CONFIG\_SECCOMP not compiled into kernel, CONFIG\_SECCOMP and CONFIG\_SECCOMP\_FILTER are needed  
[2016-11-17T08:57:15,122][INFO][o.e.p.PluginsService] [3\_RSmmb] loaded module [reindex]  
[2016-11-17T08:57:15,122][INFO][o.e.p.PluginsService] [3\_RSmmb] loaded module [transport-netty3]  
[2016-11-17T08:57:15,122][INFO][o.e.p.PluginsService] [3\_RSmmb] loaded module [transport-netty4]  
[2016-11-17T08:57:15,124][INFO][o.e.p.PluginsService] [3\_RSmmb] loaded plugin [x-pack]  
[2016-11-17T08:57:17,918][INFO][o.e.n.Node] [3\_RSmmb] initialized  
[2016-11-17T08:57:17,918][INFO][o.e.n.Node] [3\_RSmmb] starting ...  
[2016-11-17T08:57:18,852][INFO][o.e.t.TransportService] [3\_RSmmb] publish\_address {127.0.0.1:9300}, bound\_addresses {[::1]:9300}, {127.0.0.1:9300}  
[2016-11-17T08:57:18,858][WARN][o.e.b.BootstrapCheck] [3\_RSmmb] max file descriptors [8192] for elasticsearch process is too low, increase to at least [65536]  
[2016-11-17T08:57:18,858][WARN][o.e.b.BootstrapCheck] [3\_RSmmb] max number of threads [1024] for user [hadoop] is too low, increase to at least [2048]  
[2016-11-17T08:57:18,858][WARN][o.e.b.BootstrapCheck] [3\_RSmmb] max virtual memory areas vm.max\_map\_count [65530] is too low, increase to at least [262144]  
[2016-11-17T08:57:21,952][INFO][o.e.c.s.ClusterService] [3\_RSmmb] new\_master {3\_RSmmb}{3\_RSmmbbSPakUsC6VwHyzg}{x0StCQTpQDS4VtJelZcpkA}{127.0.0.1}{127.0.0.1:9300}, reason: zen-disco-elected-as-master ([0] nodes joined)  
[2016-11-17T08:57:22,085][INFO][o.e.h.HttpServer] [3\_RSmmb] publish\_address {127.0.0.1:9200}, bound\_addresses {[::1]:9200}, {127.0.0.1:9200}  
[2016-11-17T08:57:22,085][INFO][o.e.n.Node] [3\_RSmmb] started  
[2016-11-17T08:57:22,800][INFO][o.e.g.GatewayService] [3\_RSmmb] recovered [6] indices into cluster\_state  
[2016-11-17T08:57:23,677][INFO][o.e.c.r.a.AllocationService] [3\_RSmmb] Cluster health status changed from [RED] to [YELLOW] (reason: [shards started [[.monitoring-es-2-2016.11.16][0], [.monitoring-data-2][0]] ...]).

the kibana was started status as fallows:

log [01:07:23.899] [info][status][plugin:kibana@5.0.1] Status changed from uninitialized to green - Ready  
log [01:07:23.967] [info][status][plugin:elasticsearch@5.0.1] Status changed from uninitialized to yellow - Waiting for Elasticsearch  
log [01:07:23.991] [info][status][plugin:xpack\_main@5.0.1] Status changed from uninitialized to yellow - Waiting for Elasticsearch  
log [01:07:24.184] [info][status][plugin:graph@5.0.1] Status changed from uninitialized to yellow - Waiting for Elasticsearch  
log [01:07:24.189] [info][status][plugin:elasticsearch@5.0.1] Status changed from yellow to green - Kibana index ready  
log [01:07:24.206] [info][license][xpack] Imported license information from Elasticsearch: mode: trial | status: active | expiry date: 2016-12-16T17:52:09+08:00  
log [01:07:24.228] [info][status][plugin:monitoring@5.0.1] Status changed from uninitialized to yellow - Waiting for Monitoring Health Check  
log [01:07:24.230] [info][status][plugin:xpack\_main@5.0.1] Status changed from yellow to green - Ready  
log [01:07:24.231] [info][status][plugin:graph@5.0.1] Status changed from yellow to green - Ready  
log [01:07:24.242] [warning][reporting] Generating a random key for xpack.reporting.encryptionKey. To prevent pending reports from failing on restart, please set xpack.reporting.encryptionKey in kibana.yml  
log [01:07:24.245] [info][status][plugin:reporting@5.0.1] Status changed from uninitialized to green - Ready  
log [01:07:26.053] [info][status][plugin:console@5.0.1] Status changed from uninitialized to green - Ready  
log [01:07:26.062] [info][status][plugin:monitoring@5.0.1] Status changed from yellow to green - Ready  
log [01:07:26.233] [info][status][plugin:timelion@5.0.1] Status changed from uninitialized to green - Ready  
log [01:07:26.238] [info][listening] Server running at [http://localhost:5601](http://localhost:5601)  
log [01:07:26.239] [info][status][ui settings] Status changed from uninitialized to green - Ready

BTW, I Set the

xpack.security.enabled: false  
action.auto\_create\_index: .security,.monitoring\*,.watches,.triggered\_watches,.watcher-history\*  
in each of elasticsearch.yml and kibana.yml file

But I Cannot visit the kibana UI, any help?

Levi,  
Thanks!

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [November 17, 2016, 6:39am UTC](https://discuss.elastic.co/t/x-pack-was-installed-for-es-and-kibana/66316/2 "2016-11-17T06:39:57Z")

</div>

> [@lester015](#):
>
> [2016-11-17T08:57:18,858][WARN][o.e.b.BootstrapCheck] [3\_RSmmb] max file descriptors [8192] for elasticsearch process is too low, increase to at least [65536]  
> [2016-11-17T08:57:18,858][WARN][o.e.b.BootstrapCheck] [3\_RSmmb] max number of threads [1024] for user [hadoop] is too low, increase to at least [2048]  
> [2016-11-17T08:57:18,858][WARN][o.e.b.BootstrapCheck] [3\_RSmmb] max virtual memory areas vm.max\_map\_count [65530] is too low, increase to at least [262144]

Elasticsearch 5.0 added a number of [bootstrap checks](https://www.elastic.co/guide/en/elasticsearch/reference/5.0/bootstrap-checks.html) that need to be passed, and your Elasticsearch is complaining about these and therefore not starting up. [This blog post](https://www.elastic.co/blog/bootstrap_checks_annoying_instead_of_devastating) also provides some additional background on the introduction of these checks.

---

<div class="post-metadata">

**Author:** ![lester015](https://avatars.discourse-cdn.com/v4/letter/l/cc9497/32.png) [@lester015](https://discuss.elastic.co/u/lester015)\
**Post date:** [November 17, 2016, 8:13am UTC](https://discuss.elastic.co/t/x-pack-was-installed-for-es-and-kibana/66316/3 "2016-11-17T08:13:13Z")

</div>

hi Dahlqvist,  
I set the values in the limits.conf  
hadoop hard nofile 262144  
hadoop hard nproc 2048  
hadoop hard as unlimited  
hadoop soft nofile 262144  
hadoop soft nproc 2048  
hadoop soft as unlimited

when I restart es, the other WARN were resolved, Just the max virtual memory areas is not work. any help?

[2016-11-17T16:04:28,064][INFO][o.e.n.Node] [3\_RSmmb] initialized  
[2016-11-17T16:04:28,064][INFO][o.e.n.Node] [3\_RSmmb] starting ...  
[2016-11-17T16:04:29,070][INFO][o.e.t.TransportService] [3\_RSmmb] publish\_address {127.0.0.1:9300}, bound\_addresses {[::1]:9300}, {127.0.0.1:9300}  
[2016-11-17T16:04:29,077][WARN][o.e.b.BootstrapCheck] [3\_RSmmb] max virtual memory areas vm.max\_map\_count [65530] is too low, increase to at least [262144]  
[2016-11-17T16:04:32,155][INFO][o.e.c.s.ClusterService] [3\_RSmmb] new\_master {3\_RSmmb}{3\_RSmmbbSPakUsC6VwHyzg}{LGqXPMjFSF64UoEf7EjB6Q}{127.0.0.1}{127.0.0.1:9300}, reason: zen-disco-elected-as-master ([0] nodes joined)  
[2016-11-17T16:04:32,209][INFO][o.e.h.HttpServer] [3\_RSmmb] publish\_address {127.0.0.1:9200}, bound\_addresses {[::1]:9200}, {127.0.0.1:9200}  
[2016-11-17T16:04:32,209][INFO][o.e.n.Node] [3\_RSmmb] started  
[2016-11-17T16:04:32,947][INFO][o.e.g.GatewayService] [3\_RSmmb] recovered [6] indices into cluster\_state  
[2016-11-17T16:04:34,208][INFO][o.e.c.r.a.AllocationService] [3\_RSmmb] Cluster health status changed from [RED] to [YELLOW] (reason: [shards started [[.monitoring-es-2-2016.11.16][0], [.monitoring-data-2][0]] ...]).

thanks  
Levi

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [November 17, 2016, 8:16am UTC](https://discuss.elastic.co/t/x-pack-was-installed-for-es-and-kibana/66316/4 "2016-11-17T08:16:31Z")

</div>

Did [this part of the documentation](https://www.elastic.co/guide/en/elasticsearch/reference/5.0/_maximum_map_count_check.html) not work?

---

<div class="post-metadata">

**Author:** ![lester015](https://avatars.discourse-cdn.com/v4/letter/l/cc9497/32.png) [@lester015](https://discuss.elastic.co/u/lester015)\
**Post date:** [November 17, 2016, 8:46am UTC](https://discuss.elastic.co/t/x-pack-was-installed-for-es-and-kibana/66316/5 "2016-11-17T08:46:21Z")

</div>

hi Dahlqvist,  
thanks for suggestion! All the WARN INFO was resolved! I cannot visit the Kibana site and check the 5601 is opening ...

netstat -anp | grep 5601  
tcp 0 0 127.0.0.1:5601 0.0.0.0:\* LISTEN 2197/bin/../node/bi

any help?

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [November 17, 2016, 9:16am UTC](https://discuss.elastic.co/t/x-pack-was-installed-for-es-and-kibana/66316/6 "2016-11-17T09:16:50Z")

</div>

Elasticsearch 5.0 by default binds to localhost.

> [@lester015](#):
>
> [2016-11-17T16:04:32,209][INFO][o.e.h.HttpServer] [3\_RSmmb] publish\_address {127.0.0.1:9200}, bound\_addresses {[::1]:9200}, {127.0.0.1:9200}

Is you Kibana instance on the same host as Elasticsearch? Is Elasticsearch up and running?

---

<div class="post-metadata">

**Author:** ![lester015](https://avatars.discourse-cdn.com/v4/letter/l/cc9497/32.png) [@lester015](https://discuss.elastic.co/u/lester015)\
**Post date:** [November 17, 2016, 9:23am UTC](https://discuss.elastic.co/t/x-pack-was-installed-for-es-and-kibana/66316/7 "2016-11-17T09:23:24Z")

</div>

yes ,there are on the same host, the Elasticsearch is running:

[3278], build[080bb47/2016-11-11T22:08:49.812Z], OS[Linux/2.6.32-642.el6.x86\_64/amd64], JVM[Oracle Corporation/Java HotSpot(TM) 64-Bit Server VM/1.8.0\_73/25.73-b02]  
[2016-11-17T17:14:33,855][WARN][o.e.x.XPackPlugin] the [action.auto\_create\_index] setting is configured to be restrictive [.security,.monitoring\*,.watches,.triggered\_watches,.watcher-history\*]. for the next 6 months daily history indices are allowed to be created, but please make sure that any future history indices after 6 months with the pattern [.watcher-history-YYYY.MM.dd] are allowed to be created  
[2016-11-17T17:14:33,870][INFO][o.e.p.PluginsService] [3\_RSmmb] loaded module [aggs-matrix-stats]  
[2016-11-17T17:14:33,870][INFO][o.e.p.PluginsService] [3\_RSmmb] loaded module [ingest-common]  
[2016-11-17T17:14:33,871][INFO][o.e.p.PluginsService] [3\_RSmmb] loaded module [lang-expression]  
[2016-11-17T17:14:33,871][INFO][o.e.p.PluginsService] [3\_RSmmb] loaded module [lang-groovy]  
[2016-11-17T17:14:33,871][INFO][o.e.p.PluginsService] [3\_RSmmb] loaded module [lang-mustache]  
[2016-11-17T17:14:33,871][INFO][o.e.p.PluginsService] [3\_RSmmb] loaded module [lang-painless]  
[2016-11-17T17:14:33,872][INFO][o.e.p.PluginsService] [3\_RSmmb] loaded module [percolator]  
[2016-11-17T17:14:33,872][INFO][o.e.p.PluginsService] [3\_RSmmb] loaded module [reindex]  
[2016-11-17T17:14:33,872][INFO][o.e.p.PluginsService] [3\_RSmmb] loaded module [transport-netty3]  
[2016-11-17T17:14:33,872][INFO][o.e.p.PluginsService] [3\_RSmmb] loaded module [transport-netty4]  
[2016-11-17T17:14:33,874][INFO][o.e.p.PluginsService] [3\_RSmmb] loaded plugin [x-pack]  
[2016-11-17T17:14:36,734][INFO][o.e.n.Node] [3\_RSmmb] initialized  
[2016-11-17T17:14:36,734][INFO][o.e.n.Node] [3\_RSmmb] starting ...  
[2016-11-17T17:14:37,726][INFO][o.e.t.TransportService] [3\_RSmmb] publish\_address {127.0.0.1:9300}, bound\_addresses {[::1]:9300}, {127.0.0.1:9300}  
[2016-11-17T17:14:40,836][INFO][o.e.c.s.ClusterService] [3\_RSmmb] new\_master {3\_RSmmb}{3\_RSmmbbSPakUsC6VwHyzg}{GaHW\_TVETNuUa\_oy8tp-jw}{127.0.0.1}{127.0.0.1:9300}, reason: zen-disco-elected-as-master ([0] nodes joined)  
[2016-11-17T17:14:40,891][INFO][o.e.h.HttpServer] [3\_RSmmb] publish\_address {127.0.0.1:9200}, bound\_addresses {[::1]:9200}, {127.0.0.1:9200}  
[2016-11-17T17:14:40,892][INFO][o.e.n.Node] [3\_RSmmb] started  
[2016-11-17T17:14:41,747][INFO][o.e.g.GatewayService] [3\_RSmmb] recovered [6] indices into cluster\_state  
[2016-11-17T17:14:42,725][INFO][o.e.c.r.a.AllocationService] [3\_RSmmb] Cluster health status changed from [RED] to [YELLOW] (reason: [shards started [[.monitoring-es-2-2016.11.16][0], [.monitoring-data-2][0]] ...]).

---

<div class="post-metadata">

**Author:** ![lester015](https://avatars.discourse-cdn.com/v4/letter/l/cc9497/32.png) [@lester015](https://discuss.elastic.co/u/lester015)\
**Post date:** [November 17, 2016, 11:02am UTC](https://discuss.elastic.co/t/x-pack-was-installed-for-es-and-kibana/66316/8 "2016-11-17T11:02:23Z")

</div>

thanks for suggestion! it's worked!

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [December 15, 2016, 11:02am UTC](https://discuss.elastic.co/t/x-pack-was-installed-for-es-and-kibana/66316/9 "2016-12-15T11:02:25Z")

</div>

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