5.0.0-rc1 Setting network.host <NIC IP> fails

Elastic Stack Elasticsearch
1

If I go into /etc/elasticsearch/elasticsearch.yml, set network.host to IP of the nic on the server, and restart the service it will not start:

[root@centos-7 ~]# systemctl status elasticsearch -l
● elasticsearch.service - Elasticsearch
   Loaded: loaded (/usr/lib/systemd/system/elasticsearch.service; disabled; vendor preset: disabled)
   Active: failed (Result: exit-code) since Wed 2016-10-12 12:00:30 EDT; 5min ago
     Docs: http://www.elastic.co
  Process: 4388 ExecStart=/usr/share/elasticsearch/bin/elasticsearch -p ${PID_DIR}/elasticsearch.pid --quiet -Edefault.path.logs=${LOG_DIR} -Edefault.path.data=${DATA_DIR} -Edefault.path.conf=${CONF_DIR} (code=exited, status=78)
  Process: 4386 ExecStartPre=/usr/share/elasticsearch/bin/elasticsearch-systemd-pre-exec (code=exited, status=0/SUCCESS)
 Main PID: 4388 (code=exited, status=78)

Oct 12 12:00:18 centos-7.lab.local systemd[1]: Starting Elasticsearch...
Oct 12 12:00:18 centos-7.lab.local systemd[1]: Started Elasticsearch.
Oct 12 12:00:30 centos-7.lab.local systemd[1]: elasticsearch.service: main process exited, code=exited, status=78/n/a
Oct 12 12:00:30 centos-7.lab.local systemd[1]: Unit elasticsearch.service entered failed state.
Oct 12 12:00:30 centos-7.lab.local systemd[1]: elasticsearch.service failed.
2

I am also running into s ame issue . this is with elasticsearch 5.x on Centos 7 .

please share if you were able to make it work .

3

I gave up and used an older version, but now I want to try the 5.x GA release, will see if I run into this issue again.

Surprised nobody responded to this.

4

Check you /var/log/elasticsearch/elasticsearch.log
for something like
"
bootstrap checks failed
initial heap size [XXXXXXX] not equal to maximum heap size [YYYYYY]; this can cause resize pauses and prevents mlockall from locking the entire heap
"
It seems strange at first look how external net iface relate with mem heaps , but I found explanation here

Hope it will be useful...