Elasticsearch not starting on centos7

Having issue with elastic search while starting sonarqube , hope its common but tried all possible ways in blogs

[1]the es.log shows

2018.09.10 12:14:09 INFO  es[][o.e.n.Node] node name [sonarqube], node ID [JXa-ZnSUTXmQPV4Qce2xXg]
2018.09.10 12:14:09 INFO  es[][o.e.n.Node] version[5.6.3], pid[7453], build[1a2f265/2017-10-06T20:33:39.012Z], OS[Linux/3.10.0-862.6.3.el7.x86_64/amd64], JVM[Oracle Corporation/Java HotSpot(TM) 64-Bit Server VM/1.8.0_162/25.162-b12]
2018.09.10 12:14:09 INFO  es[][o.e.n.Node] JVM arguments [-XX:+UseConcMarkSweepGC, -XX:CMSInitiatingOccupancyFraction=75, -XX:+UseCMSInitiatingOccupancyOnly, -XX:+AlwaysPreTouch, -Xss1m, -Djava.awt.headless=true, -Dfile.encoding=UTF-8, -Djna.nosys=true, -Djdk.io.permissionsUseCanonicalPath=true, -Dio.netty.noUnsafe=true, -Dio.netty.noKeySetOptimization=true, -Dio.netty.recycler.maxCapacityPerThread=0, -Dlog4j.shutdownHookEnabled=false, -Dlog4j2.disable.jmx=true, -Dlog4j.skipJansi=true, -Xms512m, -Xmx1g, -XX:+HeapDumpOnOutOfMemoryError, -Des.path.home=/opt/sonarqube/elasticsearch]
2018.09.10 12:14:10 INFO  es[][o.e.p.PluginsService] loaded module [aggs-matrix-stats]
2018.09.10 12:14:10 INFO  es[][o.e.p.PluginsService] loaded module [ingest-common]
2018.09.10 12:14:10 INFO  es[][o.e.p.PluginsService] loaded module [parent-join]
2018.09.10 12:14:10 INFO  es[][o.e.p.PluginsService] loaded module [percolator]
2018.09.10 12:14:10 INFO  es[][o.e.p.PluginsService] loaded module [reindex]
2018.09.10 12:14:10 INFO  es[][o.e.p.PluginsService] loaded module [transport-netty4]
2018.09.10 12:14:10 INFO  es[][o.e.p.PluginsService] no plugins loaded
2018.09.10 12:14:14 INFO  es[][o.e.d.DiscoveryModule] using discovery type [zen]
2018.09.10 12:14:15 INFO  es[][o.e.n.Node] initialized
2018.09.10 12:14:15 INFO  es[][o.e.n.Node] starting ...
2018.09.10 12:14:15 INFO  es[][o.e.t.TransportService] publish_address {127.0.0.1:9001}, bound_addresses {127.0.0.1:9001}
2018.09.10 12:14:15 WARN  es[][o.e.b.BootstrapChecks] initial heap size [536870912] not equal to maximum heap size [1073741824]; this can cause resize pauses and prevents mlockall from locking the entire heap
2018.09.10 12:14:15 WARN  es[][o.e.b.BootstrapChecks] max file descriptors [4096] for elasticsearch process is too low, increase to at least [65536]
2018.09.10 12:14:18 INFO  es[][o.e.c.s.ClusterService] new_master {sonarqube}{JXa-ZnSUTXmQPV4Qce2xXg}{KoXVvw-iQQGoeSpdUg_gLQ}{127.0.0.1}{127.0.0.1:9001}{rack_id=sonarqube}, reason: zen-disco-elected-as-master ([0] nodes joined)
2018.09.10 12:14:19 INFO  es[][o.e.n.Node] started
2018.09.10 12:14:19 INFO  es[][o.e.g.GatewayService] recovered [8] indices into cluster_state
2018.09.10 12:14:23 INFO  es[][o.e.c.r.a.AllocationService] Cluster health status changed from [RED] to [GREEN] (reason: [shards started [[components][1], [metadatas][0]] ...]).
2018.09.10 12:14:24 INFO  es[][o.e.n.Node] stopping ...
2018.09.10 12:14:25 INFO  es[][o.e.n.Node] stopped

[2]Have sonar.properties set to : sonar.web.javaOpts=-Xmx1g -Xms512m -XX:+HeapDumpOnOutOfMemoryError
and

[3]# JVM options of Elasticsearch process
sonar.search.javaOpts=-Xms512m -Xmx1g -XX:+HeapDumpOnOutOfMemoryError

[4]and i have setup the requirements based on this link https://docs.sonarqube.org/display/SONAR/Requirements#Requirements-Linux

  • Using sonarqube-7.3 version and i am trying to set it up on centos7

Appreciate your response on it . Let me know if you need anything on this issue.

Best.

These logs in fact do indicate that ElasticSearch components starts well:

Did you check other logs ? (see Troubleshooting Note). It’s possible that overall startup is then interrupted because of a fatal error elsewhere.

verify the logs in web.log file