Unable to access ElasticSearch -Standalone Setup using version 6.8.10

[viuha8]

Hello All,

Iam trying to set up a Standalone ElasticSearch instance but not a Cluster One.

For that , i have the following in the yml file:

bootstrap.memory_lock: false
cluster.name: elasticsearch
discovery.zen.minimum_master_nodes: 1
http.port: 9200
network.host: mypcip address.
discovery.type: single-node
node.data: true
node.ingest: false
node.master: true
node.max_local_storage_nodes: 1
node.name: Machine1-VS-016
path.data: C:\ProgramData\Elastic\Elasticsearch\data
path.logs: C:\ProgramData\Elastic\Elasticsearch\logs
transport.tcp.port: 9300
xpack.license.self_generated.type: basic
xpack.security.enabled: false

With this set up, iam not getting any error message in the log , but at the same time, i can n't access the ElasticSearch in port 9200. Please advice us what is the problem in the yml file for this requirement . Iam using ES 6.8.10 version .

Log Details:

[2020-06-29T21:10:00,857][INFO ][o.e.x.m.p.l.CppLogMessageHandler] [MACHINE-VS-016] [controller/6980] [Main.cc@109] controller (64 bit): Version 6.8.10 (Build a5f7163bca0250) Copyright (c) 2020 Elasticsearch BV
[2020-06-29T21:10:01,560][INFO ][o.e.d.DiscoveryModule ] [[2020-06-29T21:10:00,857][INFO ][o.e.x.m.p.l.CppLogMessageHandler] [MACHINE-VS-016] [controller/6980] [Main.cc@109] controller (64 bit): Version 6.8.10 (Build a5f7163bca0250) Copyright (c) 2020 Elasticsearch BV
[2020-06-29T21:10:01,560][INFO ][o.e.d.DiscoveryModule ] [MACHINE-VS-016] using discovery type [single-node] and host providers [settings]
[2020-06-29T21:10:02,388][INFO ][o.e.n.Node ] [MACHINE-VS-016] initialized
[2020-06-29T21:10:02,388][INFO ][o.e.n.Node ] [MACHINE-VS-016] starting ...
[2020-06-29T21:10:02,591][INFO ][o.e.t.TransportService ] [MACHINE-VS-016] publish_address {XX.XX..65.54:9300}, bound_addresses {XX.XX..65.54:9300}
[2020-06-29T21:10:02,732][INFO ][o.e.h.n.Netty4HttpServerTransport] [MACHINE-VS-016] publish_address {XX.XX..65.54:9200}, bound_addresses {XX.XX..65.54:9200}
[2020-06-29T21:10:02,732][INFO ][o.e.n.Node ] [MACHINE-VS-016] started
[2020-06-29T21:10:03,060][INFO ][o.e.l.LicenseService ] [MACHINE-VS-016] license [0e158899-6a4b-4126-8ef6-cc7d65428b39] mode [basic] - valid
[2020-06-29T21:10:03,076][INFO ][o.e.g.GatewayService ] [MACHINE-VS-016] recovered [0] indices into cluster_state
] using discovery type [single-node] and host providers [settings]
[2020-06-29T21:10:02,388][INFO ][o.e.n.Node ] [MACHINE-VS-016] initialized
[2020-06-29T21:10:02,388][INFO ][o.e.n.Node ] [MACHINE-VS-016] starting ...
[2020-06-29T21:10:02,591][INFO ][o.e.t.TransportService ] [MACHINE-VS-016] publish_address {XX.XX..65.54:9300}, bound_addresses {XX.XX..65.54:9300}
[2020-06-29T21:10:02,732][INFO ][o.e.h.n.Netty4HttpServerTransport] [MACHINE-VS-016] publish_address {XX.XX..65.54:9200}, bound_addresses {XX.XX..65.54:9200}
[2020-06-29T21:10:02,732][INFO ][o.e.n.Node ] [MACHINE-VS-016] started
[2020-06-29T21:10:03,060][INFO ][o.e.l.LicenseService ] [MACHINE-VS-016] license [0e158899-6a4b-4126-8ef6-cc7d65428b39] mode [basic] - valid
[2020-06-29T21:10:03,076][INFO ][o.e.g.GatewayService ] [MACHINE-VS-016] recovered [0] indices into cluster_state

[Steve_Mushero (ELKman.io (ELK Stack Management Tool))]

Odd, seems normal - you might try to bind to all addresses (0.0.0.0), but weird it's not coming up for something - is it listening on that port? Not sure how to check that on windows, like 'netstat -l' or you can telnet to that port, then try curl, etc. and work you way up to a browser, but if not listening at all, that's weird = also ensure you have enough heap to get started, like 1GB to make sure it can start (though less should work).

As idiot check, mark darn sure the IP you put in XX.XX..65.54 it really the IP the machine is using; you might be surprised

[viuha8]

If i make network.host: 0.0.0.0 , then atleast , i can able to access Elastic Search using the http://localhost:9200 , but not outside of the server.

Please suggest whether is this due to network issue or some other configuration issue

[Steve_Mushero (ELKman.io (ELK Stack Management Tool))]

What is this on, a VM or Docker or some weird networking situation? Any firewalls, iptables/win FW, etc.? Did you verify the IP is what you think it is and that it's listening (netstat -lrnt but this is Windows so who knows) - with it bound to * and you can reach it we know it's up and listening so we must have networking issues - get reliable machine on same LAN to telnet to that port and work to get that to work, as ES seems fine at least for now (though find way to ensure it's listening on all IPs or *)