Not able to run elastic search on Server IP

Elastic Stack Elasticsearch
1

HI ,

I am new on ElasticSearch and trying to configure it on Fedora VM, Host machine is Windows 10 Pro.
Elastic search ver. 6.6.0
i am able to run elastic search with KIbana on Localhost:9200.
but if change "network.host" to network.host: 0.0.0.0 in elasticsearch.yml then it completely stop working even on localhost.
my aim is to access it on my host machine via url and do R&D then prepare solution design with it for a very heavy search based application.

i need to explore it for all aspect of an application like security, backup, restore etc. i am already behind schedule and new to Linux environment as well.
logs
Feb 09 21:59:03 localhost.localdomain systemd[1]: Started Elasticsearch.
_ Feb 09 21:59:03 localhost.localdomain elasticsearch[15340]: OpenJDK 64-Bit Server VM warning: Option UseConcMarkSweepGC was deprecated in version 9.0 and will likely be>_
_ Feb 09 21:59:34 localhost.localdomain systemd[1]: elasticsearch.service: Main process exited, code=exited, status=78/CONFIG_
_ Feb 09 21:59:34 localhost.localdomain systemd[1]: elasticsearch.service: Failed with result 'exit-code'._

please help.
thank you
Dheeraj Kumar

2

Could you share elasticsearch logs? Please format it with markdown or </> icon.

3

i hope this is what you meant

Feb 10 12:25:50 localhost.localdomain systemd[1]: Started Elasticsearch.
Feb 10 12:25:53 localhost.localdomain elasticsearch[1167]: OpenJDK 64-Bit Server VM warning: Option UseConcMarkSweepGC was deprecated in version 9.0 and will likely be removed in a future release.
Feb 10 12:25:21 localhost.localdomain systemd[1]: elasticsearch.service: Main process exited, code=exited, status=78/CONFIG
Feb 10 12:25:21 localhost.localdomain systemd[1]: elasticsearch.service: Failed with result 'exit-code'.
Feb 10 12:36:42 localhost.localdomain systemd[1]: Started Elasticsearch.
Feb 10 12:36:42 localhost.localdomain elasticsearch[3526]: OpenJDK 64-Bit Server VM warning: Option UseConcMarkSweepGC was deprecated in version 9.0 and will likely be removed in a future release.
Feb 10 12:37:18 localhost.localdomain systemd[1]: elasticsearch.service: Main process exited, code=exited, status=78/CONFIG
Feb 10 12:37:18 localhost.localdomain systemd[1]: elasticsearch.service: Failed with result 'exit-code'.
4

In terms of formatting yes.
But not elasticsearch logs. Have a look at the log dir.

5

I just copied log from there only :slight_smile:

6

I have uploaded whole folder from /var/log/elasticsearch atthis link

Let me know if you need anything else

7

Is it the content of elasticsearch.log file? I suspect it's not. Could paste here that content?

8

i already uploaded that content to cloud and gave the link in previous reply , let me knoe if you can't access it

9

I can't read from my mobile.

10

oh , those logs are from /var/logs/elasticsearch/elsticsearch.log
ok let me do one thing , i will delete all the content from this log file using texteditor and then try to start the service.
then i will copy all the logs from there and paste that here , i think that will be readable for you

11

output of "sudo journalctl --unit elasticsearch --since "2019-02-09 00:17:16""

image
image.png1774×422 96.7 KB

am i looking at wrong thing here ?

12

did meant these

 [2019-02-10T15:24:40,789][INFO ][o.e.e.NodeEnvironment    ] [vendorNode001] using [1] data paths, mounts [[/ (/dev/mapper/fedora-root)]], net usable_space [37.6gb], net total_space [48.9gb], types [ext4]
    [2019-02-10T15:24:40,791][INFO ][o.e.e.NodeEnvironment    ] [vendorNode001] heap size [3.9gb], compressed ordinary object pointers [true]
    [2019-02-10T15:24:40,805][INFO ][o.e.n.Node               ] [vendorNode001] node name [vendorNode001], node ID [yIFlywf7SxeWV1Uu8K3elA]
    [2019-02-10T15:24:40,806][INFO ][o.e.n.Node               ] [vendorNode001] version[6.6.0], pid[7983], build[default/rpm/a9861f4/2019-01-24T11:27:09.439740Z], OS[Linux/4.18.16-300.fc29.x86_64/amd64], JVM[Oracle Corporation/OpenJDK 64-Bit Server VM/11-ea/11-ea+28]
    [2019-02-10T15:24:40,806][INFO ][o.e.n.Node               ] [vendorNode001] JVM arguments [-Xms4g, -Xmx4g, -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-8202124475548401032, -XX:+HeapDumpOnOutOfMemoryError, -XX:HeapDumpPath=/var/lib/elasticsearch, -XX:ErrorFile=/var/log/elasticsearch/hs_err_pid%p.log, -Xlog:gc*,gc+age=trace,safepoint:file=/var/log/elasticsearch/gc.log:utctime,pid,tags:filecount=32,filesize=64m, -Djava.locale.providers=COMPAT, -XX:UseAVX=2, -Des.path.home=/usr/share/elasticsearch, -Des.path.conf=/etc/elasticsearch, -Des.distribution.flavor=default, -Des.distribution.type=rpm]
    [2019-02-10T15:24:42,558][INFO ][o.e.p.PluginsService     ] [vendorNode001] loaded module [aggs-matrix-stats]
    [2019-02-10T15:24:42,558][INFO ][o.e.p.PluginsService     ] [vendorNode001] loaded module [analysis-common]
    [2019-02-10T15:24:42,558][INFO ][o.e.p.PluginsService     ] [vendorNode001] loaded module [ingest-common]
    [2019-02-10T15:24:42,559][INFO ][o.e.p.PluginsService     ] [vendorNode001] loaded module [lang-expression]
    [2019-02-10T15:24:42,559][INFO ][o.e.p.PluginsService     ] [vendorNode001] loaded module [lang-mustache]
    [2019-02-10T15:24:42,559][INFO ][o.e.p.PluginsService     ] [vendorNode001] loaded module [lang-painless]
    [2019-02-10T15:24:42,559][INFO ][o.e.p.PluginsService     ] [vendorNode001] loaded module [mapper-extras]
    [2019-02-10T15:24:42,559][INFO ][o.e.p.PluginsService     ] [vendorNode001] loaded module [parent-join]
    [2019-02-10T15:24:42,559][INFO ][o.e.p.PluginsService     ] [vendorNode001] loaded module [percolator]
    [2019-02-10T15:24:42,559][INFO ][o.e.p.PluginsService     ] [vendorNode001] loaded module [rank-eval]
    [2019-02-10T15:24:42,559][INFO ][o.e.p.PluginsService     ] [vendorNode001] loaded module [reindex]
    [2019-02-10T15:24:42,559][INFO ][o.e.p.PluginsService     ] [vendorNode001] loaded module [repository-url]
    [2019-02-10T15:24:42,559][INFO ][o.e.p.PluginsService     ] [vendorNode001] loaded module [transport-netty4]
    [2019-02-10T15:24:42,559][INFO ][o.e.p.PluginsService     ] [vendorNode001] loaded module [tribe]
    [2019-02-10T15:24:42,559][INFO ][o.e.p.PluginsService     ] [vendorNode001] loaded module [x-pack-ccr]
    [2019-02-10T15:24:42,559][INFO ][o.e.p.PluginsService     ] [vendorNode001] loaded module [x-pack-core]
    [2019-02-10T15:24:42,559][INFO ][o.e.p.PluginsService     ] [vendorNode001] loaded module [x-pack-deprecation]
    [2019-02-10T15:24:42,559][INFO ][o.e.p.PluginsService     ] [vendorNode001] loaded module [x-pack-graph]
    [2019-02-10T15:24:42,559][INFO ][o.e.p.PluginsService     ] [vendorNode001] loaded module [x-pack-ilm]
    [2019-02-10T15:24:42,559][INFO ][o.e.p.PluginsService     ] [vendorNode001] loaded module [x-pack-logstash]
    [2019-02-10T15:24:42,560][INFO ][o.e.p.PluginsService     ] [vendorNode001] loaded module [x-pack-ml]
    [2019-02-10T15:24:42,560][INFO ][o.e.p.PluginsService     ] [vendorNode001] loaded module [x-pack-monitoring]
    [2019-02-10T15:24:42,560][INFO ][o.e.p.PluginsService     ] [vendorNode001] loaded module [x-pack-rollup]
    [2019-02-10T15:24:42,560][INFO ][o.e.p.PluginsService     ] [vendorNode001] loaded module [x-pack-security]
    [2019-02-10T15:24:42,560][INFO ][o.e.p.PluginsService     ] [vendorNode001] loaded module [x-pack-sql]
    [2019-02-10T15:24:42,560][INFO ][o.e.p.PluginsService     ] [vendorNode001] loaded module [x-pack-upgrade]
    [2019-02-10T15:24:42,560][INFO ][o.e.p.PluginsService     ] [vendorNode001] loaded module [x-pack-watcher]
    [2019-02-10T15:24:42,560][INFO ][o.e.p.PluginsService     ] [vendorNode001] no plugins loaded
    [2019-02-10T15:24:49,751][INFO ][o.e.x.s.a.s.FileRolesStore] [vendorNode001] parsed [0] roles from file [/etc/elasticsearch/roles.yml]
    [2019-02-10T15:24:50,972][INFO ][o.e.x.m.p.l.CppLogMessageHandler] [vendorNode001] [controller/8066] [Main.cc@109] controller (64 bit): Version 6.6.0 (Build bbb4919f4d17a5) Copyright (c) 2019 Elasticsearch BV
    [2019-02-10T15:24:52,099][DEBUG][o.e.a.ActionModule       ] [vendorNode001] Using REST wrapper from plugin org.elasticsearch.xpack.security.Security
    [2019-02-10T15:24:52,636][INFO ][o.e.d.DiscoveryModule    ] [vendorNode001] using discovery type [zen] and host providers [settings]
    [2019-02-10T15:24:54,083][INFO ][o.e.n.Node               ] [vendorNode001] initialized
    [2019-02-10T15:24:54,085][INFO ][o.e.n.Node               ] [vendorNode001] starting ...
    [2019-02-10T15:24:54,320][INFO ][o.e.t.TransportService   ] [vendorNode001] publish_address {192.168.150.129:9300}, bound_addresses {[::]:9300}
    [2019-02-10T15:24:54,373][INFO ][o.e.b.BootstrapChecks    ] [vendorNode001] bound or publishing to a non-loopback address, enforcing bootstrap checks
    [2019-02-10T15:24:54,407][ERROR][o.e.b.Bootstrap          ] [vendorNode001] node validation exception
    [1] bootstrap checks failed
    [1]: Java version [11-ea] is an early-access build, only use release builds
    [2019-02-10T15:24:54,409][INFO ][o.e.n.Node               ] [vendorNode001] stopping ...
    [2019-02-10T15:24:54,440][INFO ][o.e.n.Node               ] [vendorNode001] stopped
    [2019-02-10T15:24:54,441][INFO ][o.e.n.Node               ] [vendorNode001] closing ...
    [2019-02-10T15:24:54,465][INFO ][o.e.n.Node               ] [vendorNode001] closed
    [2019-02-10T15:24:54,469][INFO ][o.e.x.m.p.NativeController] [vendorNode001] Native controller process has stopped - no new native processes can be started
13

Here's your problem:

[1]: Java version [11-ea] is an early-access build, only use release builds

Update your jvm

2 Likes
14

Thanks, can please help me find how can I do that on fedora desktop

15

I don't know. It's a Java question I guess or a fedora one.

May start here: https://jdk.java.net/11/

16

Yeah, Thats true ,btw thanks a lot

17

how can i mark it close ?

18

Just curious if network.host: 127.0.0.1 might make it work for you?

19

By default it works for Localhost which is equal to 127.0.0.1, but if you try to open it using this loop-back address instead of "localhost" then it will not work.

if i set this ip elastic search opens on this ip.

my intent was to access it from network so i set 0.0.0.0 (its a bad choice, but i am just working on POC)

20

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