Who is 169.254.175.226 ???
Hi all!
Installed 2.0 community, Win 7 64 bit.
Unable to open console http://localhost:8091/
http://localhost:8092/ ok {"couchdb":"Welcome","version":"1.2.0a-be4fa61-git","couchbase":"2.0.0-1976-rel-community"}
Checking E:\Couchbase\Server\var\lib\couchbase\logs\info.1, and keeps writing
[ns_server:warn,2012-12-19T12:18:06.981,ns_1@169.254.175.226:dist_manager<0.272.0>:dist_manager:is_good_address:81]Cannot listen on address `169.254.175.226`: eaddrnotavail [ns_server:info,2012-12-19T12:18:06.981,ns_1@169.254.175.226:dist_manager<0.272.0>:dist_manager:wait_for_address:100]Configured address `169.254.175.226` seems to be invalid. Giving OS a chance to bring it up. [ns_server:error,2012-12-19T12:18:07.995,ns_1@169.254.175.226:dist_manager<0.272.0>:dist_manager:init:148]Configured address `169.254.175.226` seems to be invalid. Will refuse to to start for safety reasons.
with ifconfig /all (i already knew, but just in case) i have NO 169.254.whatever address.
Cheers!
Mimmo
That worked like a charm!!!
Cheers!
It looks like Windows can have "invisible" interfaces with link local addresses automatically assigned. Couchbase is incorrectly picking them up instead of searching further for something more real. I've filed a bug, http://www.couchbase.com/issues/browse/MB-7417
Thanks Siri!
Hello,
I have documented a work around here:
http://tugdualgrall.blogspot.com/2012/12/what-to-do-if-your-couchbase-se...
Regards
Tug
It looks like at the time when you installed Couchbase, your ethernet/wifi device had a "self-assigned" IP... The 169.* range is usually the self-assigned range.
You will need to do a simple IP fix for Windows, to set Couchbase to use 127.0.0.1.
Instructions can be found here: http://www.couchbase.com/docs/couchbase-manual-2.0/couchbase-bestpractice-cloud-ip.html
@scalabl3
Technical Evangelist
Couchbase Inc.