erlang OS is not able to retrieve IP address in some conditions ( UI shows "[16:14:07] - IP address seems to have changed. Unable to listen on 'ns_1@169.254.15.168'." message every second after installing 1.8.1 on a windows 7 vm)

Aleksey Kondratenko added a comment - 12/Jun/12 6:19 PM May I ask you to try 2.0 on same box? 2.0 has different code that should have better chance of working. If that's the case I'll just backport that fix

Aliaksey Artamonau added a comment - 12/Jun/12 6:21 PM I've seen this several times on 2.0 HEAD.

Thuan Nguyen added a comment - 13/Jun/12 9:05 PM Integrated in github-ns-server-2-0 #374 (See [ http://qa.hq.northscale.net/job/github-ns-server-2-0/374/ ])      MB-5535 :bp:use gen_udp instead for address changed alert testing (Revision eb37c7ba772149d6cf4838bd10bc3af35227de1d)      Result = SUCCESS Aliaksey Artamonau : Files : * src/menelaus_web_alerts_srv.erl

Farshid Ghods added a comment - 03/Jul/12 2:30 PM i changed VM network settings from NAT to bridged and i didn't see this issue anymore in the installation. so i think this bug only appears when VM uses NAT settings to connect to the network

Aleksey Kondratenko added a comment - 03/Jul/12 2:35 PM Well, windows picks ip at install time. I think we're doing something like picking least IP address. So change of setting may just change set of IP addresses on this host and "fix" it.

Farshid Ghods added a comment - 03/Jul/12 3:44 PM issue exists on the latest 2.0 builds. diag attached.

Aleksey Kondratenko added a comment - 04/Oct/12 1:08 PM In latest diags I see this: [ns_server:error] [2012-07-03 13:43:04] [ ns_1@169.254.130.11 :<0.9898.0>:menelaus_web_alerts_srv:can_listen:330] gen_udp:open failed due to eaddrnotavail Which implies indeed this address is not available anymore. Or at least erlang/OS thinks so. Given we decided to avoid completing proper fix for ip address selection _and_ we have a known workaround (pick address manually) I don't think that's must have for 2.0 and maybe even for resolving as 'Incomplete'

Farshid Ghods added a comment - 04/Oct/12 1:11 PM based on Aliaksey's comment i recommend deferring this to .next

Sriram Melkote added a comment - 03/Jan/13 3:35 PM The specific issue of picking up 169.254 addresses has been fixed in 2.0.1 via MB-7417 . The larger IP address change after install still remains.

Dipti Borkar added a comment - 04/Feb/13 1:10 AM Siri, is this a dupe of the bug you fixed or does it relate to the larger IP problem?

Sriram Melkote added a comment - 04/Feb/13 1:40 AM The specific incorrect chosen range is duplicated by MB-7417 and fixed