# ELASTICSEARCH STUCK DURING INSTALLATION

**URL:** <https://discuss.elastic.co/t/elasticsearch-stuck-during-installation/179250>\
**Category:** Elasticsearch\
**Created:** [May 1, 2019, 8:17pm UTC](https://discuss.elastic.co/t/elasticsearch-stuck-during-installation/179250 "2019-05-01T20:17:27Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![Debasish\_Rath](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/debasish_rath/32/45380_2.png) [@Debasish\_Rath](https://discuss.elastic.co/u/Debasish_Rath)\
**Post date:** [May 1, 2019, 8:17pm UTC](https://discuss.elastic.co/t/elasticsearch-stuck-during-installation/179250/1 "2019-05-01T20:17:27Z")

</div>

During installation on redhat machine, installation stucked. ANy IDEA? below is the log

[2019-05-01T19:39:46,225][INFO][o.e.p.PluginsService] [srv-appmid-wl.sentel.lan] loaded module [transport-netty4]  
[2019-05-01T19:39:46,225][INFO][o.e.p.PluginsService] [srv-appmid-wl.sentel.lan] loaded module [x-pack-ccr]  
[2019-05-01T19:39:46,225][INFO][o.e.p.PluginsService] [srv-appmid-wl.sentel.lan] loaded module [x-pack-core]  
[2019-05-01T19:39:46,225][INFO][o.e.p.PluginsService] [srv-appmid-wl.sentel.lan] loaded module [x-pack-deprecation]  
[2019-05-01T19:39:46,226][INFO][o.e.p.PluginsService] [srv-appmid-wl.sentel.lan] loaded module [x-pack-graph]  
[2019-05-01T19:39:46,226][INFO][o.e.p.PluginsService] [srv-appmid-wl.sentel.lan] loaded module [x-pack-ilm]  
[2019-05-01T19:39:46,226][INFO][o.e.p.PluginsService] [srv-appmid-wl.sentel.lan] loaded module [x-pack-logstash]  
[2019-05-01T19:39:46,226][INFO][o.e.p.PluginsService] [srv-appmid-wl.sentel.lan] loaded module [x-pack-ml]  
[2019-05-01T19:39:46,227][INFO][o.e.p.PluginsService] [srv-appmid-wl.sentel.lan] loaded module [x-pack-monitoring]  
[2019-05-01T19:39:46,227][INFO][o.e.p.PluginsService] [srv-appmid-wl.sentel.lan] loaded module [x-pack-rollup]  
[2019-05-01T19:39:46,227][INFO][o.e.p.PluginsService] [srv-appmid-wl.sentel.lan] loaded module [x-pack-security]  
[2019-05-01T19:39:46,227][INFO][o.e.p.PluginsService] [srv-appmid-wl.sentel.lan] loaded module [x-pack-sql]  
[2019-05-01T19:39:46,228][INFO][o.e.p.PluginsService] [srv-appmid-wl.sentel.lan] loaded module [x-pack-watcher]  
[2019-05-01T19:39:46,228][INFO][o.e.p.PluginsService] [srv-appmid-wl.sentel.lan] no plugins loaded  
[2019-05-01T19:39:50,069][INFO][o.e.x.s.a.s.FileRolesStore] [srv-appmid-wl.sentel.lan] parsed [0] roles from file [/home/l3support/elasticsearch-7.0.0/config/roles.yml]  
[2019-05-01T19:39:50,733][INFO][o.e.x.m.p.l.CppLogMessageHandler] [srv-appmid-wl.sentel.lan] [controller/54146] [Main.cc@109] controller (64 bit): Version 7.0.0 (Build cdaa022645f38d) Copyright (c) 2019 Elasticsearch BV  
[2019-05-01T19:39:51,116][DEBUG][o.e.a.ActionModule] [srv-appmid-wl.sentel.lan] Using REST wrapper from plugin org.elasticsearch.xpack.security.Security  
[2019-05-01T19:39:51,543][INFO][o.e.d.DiscoveryModule] [srv-appmid-wl.sentel.lan] using discovery type [zen] and seed hosts providers [settings]  
[2019-05-01T19:39:52,359][INFO][o.e.n.Node] [srv-appmid-wl.sentel.lan] initialized  
[2019-05-01T19:39:52,359][INFO][o.e.n.Node] [srv-appmid-wl.sentel.lan] starting ...  
[2019-05-01T19:39:52,486][INFO][o.e.t.TransportService] [srv-appmid-wl.sentel.lan] publish\_address {127.0.0.1:9300}, bound\_addresses {[::1]:9300}, {127.0.0.1:9300}  
[2019-05-01T19:39:52,499][WARN][o.e.b.BootstrapChecks] [srv-appmid-wl.sentel.lan] system call filters failed to install; check the logs and fix your configuration or disable system call filters at your own risk  
[2019-05-01T19:39:52,499][WARN][o.e.b.BootstrapChecks] [srv-appmid-wl.sentel.lan] the default discovery settings are unsuitable for production use; at least one of [discovery.seed\_hosts, discovery.seed\_providers, cluster.initial\_master\_nodes] must be configured  
[2019-05-01T19:39:52,515][INFO][o.e.c.c.ClusterBootstrapService] [srv-appmid-wl.sentel.lan] no discovery configuration found, will perform best-effort cluster bootstrapping after [3s] unless existing master is discovered  
[2019-05-01T19:39:55,532][INFO][o.e.c.c.Coordinator] [srv-appmid-wl.sentel.lan] setting initial configuration to VotingConfiguration{-cjKp6RiRQu4cD9426K1Ug}  
[2019-05-01T19:39:55,781][INFO][o.e.c.s.MasterService] [srv-appmid-wl.sentel.lan] elected-as-master ([1] nodes joined)[{srv-appmid-wl.sentel.lan}{-cjKp6RiRQu4cD9426K1Ug}{KrNMocnzRc6eRcWzHY0pmQ}{127.0.0.1}{127.0.0.1:9300}{ml.machine\_memory=135290077184, xpack.installed=true, ml.max\_open\_jobs=20} elect leader, _BECOME\_MASTER\_TASK_, _FINISH\_ELECTION_], term: 1, version: 1, reason: master node changed {previous , current [{srv-appmid-wl.sentel.lan}{-cjKp6RiRQu4cD9426K1Ug}{KrNMocnzRc6eRcWzHY0pmQ}{127.0.0.1}{127.0.0.1:9300}{ml.machine\_memory=135290077184, xpack.installed=true, ml.max\_open\_jobs=20}]}  
[2019-05-01T19:39:55,999][INFO][o.e.c.s.ClusterApplierService] [srv-appmid-wl.sentel.lan] master node changed {previous , current [{srv-appmid-wl.sentel.lan}{-cjKp6RiRQu4cD9426K1Ug}{KrNMocnzRc6eRcWzHY0pmQ}{127.0.0.1}{127.0.0.1:9300}{ml.machine\_memory=135290077184, xpack.installed=true, ml.max\_open\_jobs=20}]}, term: 1, version: 1, reason: Publication{term=1, version=1}  
[2019-05-01T19:39:56,039][INFO][o.e.h.AbstractHttpServerTransport] [srv-appmid-wl.sentel.lan] publish\_address {127.0.0.1:9200}, bound\_addresses {[::1]:9200}, {127.0.0.1:9200}  
[2019-05-01T19:39:56,039][INFO][o.e.n.Node] [srv-appmid-wl.sentel.lan] started  
[2019-05-01T19:39:56,092][WARN][o.e.x.s.a.s.m.NativeRoleMappingStore] [srv-appmid-wl.sentel.lan] Failed to clear cache for realms []  
[2019-05-01T19:39:56,142][INFO][o.e.g.GatewayService] [srv-appmid-wl.sentel.lan] recovered [0] indices into cluster\_state  
[2019-05-01T19:39:56,314][INFO][o.e.c.m.MetaDataIndexTemplateService] [srv-appmid-wl.sentel.lan] adding template [.triggered\_watches] for index patterns [.triggered\_watches\*]  
[2019-05-01T19:39:56,452][INFO][o.e.c.m.MetaDataIndexTemplateService] [srv-appmid-wl.sentel.lan] adding template [.watch-history-9] for index patterns [.watcher-history-9\*]  
[2019-05-01T19:39:56,795][INFO][o.e.c.m.MetaDataIndexTemplateService] [srv-appmid-wl.sentel.lan] adding template [.watches] for index patterns [.watches\*]  
[2019-05-01T19:39:57,035][INFO][o.e.c.m.MetaDataIndexTemplateService] [srv-appmid-wl.sentel.lan] adding template [.monitoring-logstash] for index patterns [.monitoring-logstash-7-_]  
[2019-05-01T19:39:57,183][INFO][o.e.c.m.MetaDataIndexTemplateService] [srv-appmid-wl.sentel.lan] adding template [.monitoring-es] for index patterns [.monitoring-es-7-_]  
[2019-05-01T19:39:57,311][INFO][o.e.c.m.MetaDataIndexTemplateService] [srv-appmid-wl.sentel.lan] adding template [.monitoring-beats] for index patterns [.monitoring-beats-7-_]  
[2019-05-01T19:39:57,456][INFO][o.e.c.m.MetaDataIndexTemplateService] [srv-appmid-wl.sentel.lan] adding template [.monitoring-alerts-7] for index patterns [.monitoring-alerts-7]  
[2019-05-01T19:39:57,555][INFO][o.e.c.m.MetaDataIndexTemplateService] [srv-appmid-wl.sentel.lan] adding template [.monitoring-kibana] for index patterns [.monitoring-kibana-7-_]  
[2019-05-01T19:39:57,673][INFO][o.e.x.i.a.TransportPutLifecycleAction] [srv-appmid-wl.sentel.lan] adding index lifecycle policy [watch-history-ilm-policy]  
[2019-05-01T19:39:58,004][INFO][o.e.l.LicenseService] [srv-appmid-wl.sentel.lan] license [7093a0ee-2432-4ce5-b71f-4c53c4f05d2f] mode [basic] - valid

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [May 1, 2019, 8:24pm UTC](https://discuss.elastic.co/t/elasticsearch-stuck-during-installation/179250/2 "2019-05-01T20:24:09Z")

</div>

That's not stuck, it's running and waiting for traffic.

---

<div class="post-metadata">

**Author:** ![Debasish\_Rath](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/debasish_rath/32/45380_2.png) [@Debasish\_Rath](https://discuss.elastic.co/u/Debasish_Rath)\
**Post date:** [May 1, 2019, 8:25pm UTC](https://discuss.elastic.co/t/elasticsearch-stuck-during-installation/179250/3 "2019-05-01T20:25:44Z")

</div>

Hi .. thanks for prompt replay. SO I can see it's running as a process. What will be the next step. Will I let it run in background and start installing kibana ?

[root@srv-appmid-wl ELK\_BACKUP]# curl 192.168.41.3:9200  
curl: (7) couldn't connect to host  
[root@srv-appmid-wl ELK\_BACKUP]# ps -ef|grep elasticsearch  
1010 53993 33652 1 19:39 pts/9 00:00:50 /usr/java/jdk1.8.0\_144/bin/java -Xms1g -Xmx1g -XX:+UseConcMarkSweepGC -XX:CMSInitiatingOccupancyFraction=75 -XX:+UseCMSInitiatingOccupancyOnly -Des.networkaddress.cache.ttl=60 -Des.networkaddress.cache.negative.ttl=10 -XX:+AlwaysPreTouch -Xss1m -Djava.awt.headless=true -Dfile.encoding=UTF-8 -Djna.nosys=true -XX:-OmitStackTraceInFastThrow -Dio.netty.noUnsafe=true -Dio.netty.noKeySetOptimization=true -Dio.netty.recycler.maxCapacityPerThread=0 -Dlog4j.shutdownHookEnabled=false -Dlog4j2.disable.jmx=true -Djava.io.tmpdir=/tmp/elasticsearch-7780707558332565336 -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=data -XX:ErrorFile=logs/hs\_err\_pid%p.log -XX:+PrintGCDetails -XX:+PrintGCDateStamps -XX:+PrintTenuringDistribution -XX:+PrintGCApplicationStoppedTime -Xloggc:logs/gc.log -XX:+UseGCLogFileRotation -XX:NumberOfGCLogFiles=32 -XX:GCLogFileSize=64m -Dio.netty.allocator.type=unpooled -Des.path.home=/home/l3support/elasticsearch-7.0.0 -Des.path.conf=/home/l3support/elasticsearch-7.0.0/config -Des.distribution.flavor=default -Des.distribution.type=tar -Des.bundled\_jdk=true -cp /home/l3support/elasticsearch-7.0.0/lib/\* org.elasticsearch.bootstrap.Elasticsearch  
1010 54146 53993 0 19:39 pts/9 00:00:00 /home/l3support/elasticsearch-7.0.0/modules/x-pack-ml/platform/linux-x86\_64/bin/controller  
root 60841 34531 0 20:24 pts/11 00:00:00 grep elasticsearch

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [May 1, 2019, 8:25pm UTC](https://discuss.elastic.co/t/elasticsearch-stuck-during-installation/179250/4 "2019-05-01T20:25:59Z")

</div>

How did you start it?

---

<div class="post-metadata">

**Author:** ![Debasish\_Rath](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/debasish_rath/32/45380_2.png) [@Debasish\_Rath](https://discuss.elastic.co/u/Debasish_Rath)\
**Post date:** [May 1, 2019, 8:27pm UTC](https://discuss.elastic.co/t/elasticsearch-stuck-during-installation/179250/5 "2019-05-01T20:27:43Z")

</div>

I am installing elasticsearch7.0.0 in redhat. from below url. I started the script with ./bin/elasticsearch

wget [https://artifacts.elastic.co/downloads/elasticsearch/elasticsearch-7.0.0-linux-x86\_64.tar.gz](https://artifacts.elastic.co/downloads/elasticsearch/elasticsearch-7.0.0-linux-x86_64.tar.gz)

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [May 1, 2019, 8:31pm UTC](https://discuss.elastic.co/t/elasticsearch-stuck-during-installation/179250/6 "2019-05-01T20:31:13Z")

</div>

Why not use the RPM repo, that has service files?

---

<div class="post-metadata">

**Author:** ![Debasish\_Rath](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/debasish_rath/32/45380_2.png) [@Debasish\_Rath](https://discuss.elastic.co/u/Debasish_Rath)\
**Post date:** [May 1, 2019, 8:31pm UTC](https://discuss.elastic.co/t/elasticsearch-stuck-during-installation/179250/7 "2019-05-01T20:31:52Z")

</div>

Ok let me try and get back to you. Thanks!!

---

<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:** [May 29, 2019, 8:31pm UTC](https://discuss.elastic.co/t/elasticsearch-stuck-during-installation/179250/8 "2019-05-29T20:31:58Z")

</div>

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