So I've seen several posts about this however I'm in the same boat since upgrading from 1.x to 2.3.1
I've set my elasticsearch.yml to be blank and use all the defaults and I still get an issue connecting.
with a config setup:
[2016-04-20 23:38:44,323][WARN ][transport.netty ] [Elasticsearch] exception caught on transport layer [[id: 0x1a04f52d, /127.0.0.1:48126 => /127.0.0.1:9300]], closing connection
java.lang.NullPointerException
with a blank config:
[2016-04-20 23:38:44,323][WARN ][transport.netty ] [Bloodshed] exception caught on transport layer [[id: 0x18ad695a, /127.0.0.1:36462 => /127.0.0.1:9300]], closing connection
java.lang.NullPointerException
I can curl localhost:9200
erogers@napalprdlog03:/etc/elasticsearch$ curl localhost:9200
{
"name" : "Elasticsearch-Log3",
"cluster_name" : "elasticsearch2",
"version" : {
"number" : "2.3.1",
"build_hash" : "bd980929010aef404e7cb0843e61d0665269fc39",
"build_timestamp" : "2016-04-04T12:25:05Z",
"build_snapshot" : false,
"lucene_version" : "5.5.0"
},
"tagline" : "You Know, for Search"
}
I cannot curl it's own internal ip address from the same box.
erogers@napalprdlog03:/etc/elasticsearch$ curl 10.220.7.19:9200
curl: (7) Failed to connect to 10.220.7.19 port 9200: Connection refused
the purpose of this box is for external points to transmit via TCP windows event logs and other such log files.
I've tried setting network.host everywhich way but loose and it still will not allow 10.220.7.19:9200 to connect.
ufw has been disabled