Two NICs, the primary of which gets a DHCP address = FAIL

[eloyd]

Given a VM with two virtual NICs in it that has NLS installed on it. The primary NIC (eth0) is attached to a public network with a DHCP address that we cannot control. The secondary NIC is private to our network and has a static IP address.

This morning, the primary NIC got a new IP address. Now the cluster says its broken because it's only looking at the previously assigned IP and logstash won't stay running.

Changing or forcing the eth1 IP is not an option. Thoughts?

[eloyd]

Update: After a number of logstash failures to stay running, it is now staying up for no apparent reason (nothing changed on our system except for eth0 IP). We still have "Instance Status" listing the wrong IP though. I fear applying any global changes that it will try to connect to the old IP address. Any way we can convince it to use the static eth1 IP or should we stick that in for the load-balancer IP?

[scottwilkerson]

You can modify these settings in the elasticsearch config
/usr/local/nagioslogserver/elasticsearch/config/elasticsearch.yml

http://www.elasticsearch.org/guide/en/e ... twork.html

One Caveat, DO NOT change the value for http.host or you could expose your server

[eloyd]

Thanks. I'll take a look.