Unable to install and configure Membase server 1.7

Daniel, the issue seems to be with getting the list of IP addresses for this server. Can you confirm whether you have multiple addresses on this system? Also, can you please follow the instructions outline here (http://www.couchbase.org/wiki/display/membase/Using+Membase+in+the+Cloud) to force Membase to use a specific interface and let me know if that works for you?

Perry

I have tried following those directions yes, it did not work for me however. This machine does have several ips (10 in fact). I done some digging and found the root of one of the problems in addr_util.erl, in the function list_all_addresses() it makes a call to inet:getif(), and this function will throw an error when that many ips are present on the machine (also, according to the erlang guys, this function should not be used anyway...). I modified the erl as follows, forgive me if the code is not "good" I'm very new to erlang

list_all_addresses() ->
	{ok, AddrInfo} = inet:getifaddrs(),
	AdapterInfo = lists:map(fun(X) -> element(2, X) end, AddrInfo),
	FlatList = lists:flatten(AdapterInfo),
	AddressList = lists:filter(fun(Z) -> element(1, Z) == addr end, FlatList),
	CandidateList = lists:map(fun(A) -> addr_to_s(element(2, A)) end, AddressList),
	lists:filter(fun(B) -> length(string:tokens(B, ".")) == 4 end, CandidateList) -- ["127.0.0.1"].

now the ip_addr.bat file returns one of the ips as expected, however, the server still does not work.

Can you look at the logs and see if you're getting the same error or a different one?

I receive the same error when I run the cmd tool to initialize the cluster.. What logs do you need me to look at?

If you run "C:\Program Files\Membase\Server\bin\mbbrowse_logs" it will print out a bunch of output. There should be an error in there indicating why it wouldn't start.

Feel free to post here and I'll take a look when I can.

Perry

error seems to be here.

ns_log: logging menelaus_web:19:Server error during processing: ["web request failed",
{path,"/pools"},
{type,error},
{what,{badmatch,{error,efault}}},
{trace,
[{uuid,new,1},
{menelaus_web,get_uuid,0},
{menelaus_web,handle_pools,1},
{menelaus_web,loop,3},
{mochiweb_http,headers,5},
{proc_lib,init_p_do_apply,3}]}]

Can you email the full logs to perry@couchbase.com?

Hi Perry, any update on this issue by any chance? We are in the same boat here. Can't configure Membase 1.7.1 after install or upgrade.

Thanks.

The bulk of our Windows installation problems seem to stem from Erlang not being able to handle a multi-homed (multiple IP addresses) properly. We've got some fixes coming down the line, if you sidemail me I can work to get you those and hopefully resolve this.

Perry

Hi Perry,

I'm having the same issue on a 2008 R2 multihomed server. 1.7.1 installed fine on a similar machine with only one IP. I will contact you directly as well.

Thanks,
Aaron

I've emailed some of you directly with what we believe is a fix. Can you please confirm that? Assuming it holds up to testing, we'll be rolling the fix into the product in an upcoming release.

I applied the patch you sent me and can confirm I was able to set up membase successfully. I haven't really tested the product yet other than to join an existing cluster.

I'm having the same issue with windows server 2008 R2. Can I please get a copy of the patch you have mentioned. I'd like to stick with membase 1.7.1 instead of using an earlier version. Thank you.

Sent over, let us know if that solves the problem. We'll have a maintenance release out shortly to address this.

I run into the same issue .would it be possible to get a patch ?

Can i get that patch also... I'm not able to configure on the server but it does work from my home computer.

We released 1.7.1.1 late last week. It's currently available just as Enterprise Edition (Community Edition will be released a bit later)...can you all please try downloading the Enterprise Edition and see if this solves your issues?

Perry

I have this same problem so I tried to download the enterprise edition 1.7.1.1. The DL page only shows 1.7.1 currently: http://www.couchbase.com/downloads/membase-server-enterprise-edition-win...

I looked at the release notes and it doesn't mention a 1.7.1.1 version.. can someone point me in the right direction?

Yeah I could not get the 1.7.1.1 either I tried with all the download links.

As I mentioned above, it's currently only available as the Enterprise Edition (which is free to use for non-production environments and up to 2 nodes in production). We'll be releasing a Community Edition shortly.

Perry

Can you provide a link to the enterprise edition 7.1.1 ? I the public download link and the release notes for the enterprise edition only state 7.1 is available.

Any ETA on the 7.1.1. , I would like to get my cache service up :)

same thing... the enterprise edition download is only 7.1...

try it yourself!!! jmacduff even posted a link to the download page!!! and it only has 7.1!

Hey guys, so sorry about that...I thought things had been updated when they hadn't.

The Enterprise Edition should be updated now and Community will be coming next week.

Perry

Thanks for the reply Perry. I downloaded the 7.1.1. enterprise edition and just installed it on two Server 2008 r2 boxes.

Box1 started the server properly, however box2 cannot join the server. The error from box2 remains the same:

Attention - Failed to reach erlang port mapper. Timeout connecting to "10.10.10.6" on port "4369". This could be due to an incorrect host/port combination or a firewall in place between the servers.

Happy to send any logs you need.

For me the new version worked! 7.1.1!

were you getting the same error like I was before?

well it just would not connnect... asked for a password and username... now it connects fine...

Are you saying it wouldn't connect after the cluster was already setup (nodes added), or the setup was blocked (my case)?

I am just trying to narrow down the problem my side.

jmacduff, the major change in 1.7.1.1 was to support systems with multiple IP addresses. Basically, the service would say it was starting but you'd never be able to connect.

If you've having other issues after trying 1.7.1.1, we'll be happy to work those through with you as well.

Windows has long been a bit of a thorn in our side since each end system can be wildly different than others. I guarantee that we test and QA Windows, yet we still have problems out in the field unfortunately.

Perry

I certainly appreciate the assistance (even if it's the dreaded windows) and happy to help debug the problem.

Let me explain the setup:

-- 3 machines to start with (Pip, Eric, Tweek)
-- No domain, the machines are in a workgroup
-- Each is Windows Server 2008
-- Each has 24+ gigs of ram , starting cluster at 10gig's each
-- Each box has a set of public IP's and private ips.
-- The private Ip's are static are the connection is marked private , the public IP's are from the host on a public connection

When I setup the cluster on the first machine ( Pip) the service immediately starts up on the private IP. From the other machines (eric and tweek) I try to connect to the "existing" cluster on Pip. Every time I get the same error ( as stated above). I have tried to connect both to pip/s private IP (which Eric and Tweek can see) and the public IP's both by the ip and a dns entry.

I have tried starting the cluster on all 3 machines and then joining the other machines, it's always the same outcome with the same error.

The error message:
Attention - Failed to reach erlang port mapper. Timeout connecting to "10.10.10.6" on port "4369". This could be due to an incorrect host/port combination or a firewall in place between the servers.

Seems to imply that there is something preventing erlang from communicating between the two nodes. It doesn't actually matter which IP you tell the nodes to join as...each node "identifies" itself with it's own chosen IP address and that's what's used for communication between them. We can set that IP address to have each node identify itself as something non-default (http://www.couchbase.org/wiki/display/membase/Using+Membase+in+the+Cloud)

-Is the 10.10.10.6 address your public or private? Can all your nodes talk to each other on both networks?
-Is Windows firewall running on any of these machines? Can you simply turn it off and try again?
-Can you try telnetting from one node to another on port 4369 (and 11210 needs to be open as well)?

Perry

Thanks for the reply Perry.

A few replies:

-- Yes the 10.10.10.* addresses are private, the other addresses are public. By public I mean anyone can connect/ping them assuming no firewall restrictions.

-- I disabled the firewalls on all the machines even though I had added the port, just to try and reduce the problem set.

-- Yes the machines can see each other, I can telnet from 10.10.10.5 to 10.10.10.6

Update: This mornign I decided to try the install and setup without the private IP's. I disabled the private IP adaptor (which left only the public IP's).

I installed the 7.1.1.1 package on PIP and it grabbed the public IP 208.99.X.X . I then tried to connect to PIP from TWEEK (again 7.1.1.1 package) and got the following error trying to join the cluster:

Attention - Failed to reach erlang port mapper. Timeout connecting to "169.254.15.59" on port "4369". This could be due to an incorrect host/port combination or a firewall in place between the servers.

So at this point I am really stumped.. I have no idea why it's trying to connect on a 169 address.

Well that's new and confusing to me as well...a 169.254.x.y address comes from a very special (and reserved) IP space so i'm not sure how Membase would be generating that, it's usually used for Bonjour-like services to do autodiscovery (I only know that because of a previous company).

Can I get an 'ipconfig' from these machines?

Perry

No problem... I dont see a way to attach a file to a post so here is the data (ipconfig /all). I removed some of the end host addresses so I dont get spammed.

Windows IP Configuration

Host Name . . . . . . . . . . . . : pip
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Mixed
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Private:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom BCM5708C NetXtreme II GigE (NDIS VBD Client) #2
Physical Address. . . . . . . . . : 00-19-B9-F0-62-6A
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::c80f:f535:2e2a:2d24%10(Preferred)
IPv4 Address. . . . . . . . . . . : 10.10.10.6(Preferred)
Subnet Mask . . . . . . . . . . . : 255.0.0.0
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . : 204.8.---.---
204.8.---.---
NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter Swift:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom BCM5708C NetXtreme II GigE (NDIS VBD Client)
Physical Address. . . . . . . . . : 00-19-B9-F0-62-68
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::44b6:5c82:fea0:541a%9(Preferred)
IPv4 Address. . . . . . . . . . . : 208.99.---.---(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.---.---
IPv4 Address. . . . . . . . . . . : 208.99.---.---(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.224
IPv4 Address. . . . . . . . . . . : 208.99.---.---(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.224
Default Gateway . . . . . . . . . : 208.99.212.65
DNS Servers . . . . . . . . . . . : 204.8.34.82
204.8.34.86
NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter Local Area Connection*:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : isatap.{1430023A-B3AC-4C6D-86AD-6C3B570D5394}
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 2:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 10:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft 6to4 Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2002:d063:d443::d063:d443(Preferred)
IPv6 Address. . . . . . . . . . . : 2002:d063:d444::d063:d444(Preferred)
IPv6 Address. . . . . . . . . . . : 2002:d063:d447::d063:d447(Preferred)
Default Gateway . . . . . . . . . : 2002:c058:6301::c058:6301
DNS Servers . . . . . . . . . . . : 204.8---
204.8.---.---
NetBIOS over Tcpip. . . . . . . . : Disabled

Tunnel adapter Local Area Connection* 11:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft Tun Miniport Adapter
Physical Address. . . . . . . . . : 02-00-54-55-4E-01
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2001:0:4137:9e76:2472:188e:2f9c:2bbc(Preferred)
Link-local IPv6 Address . . . . . : fe80::2472:188e:2f9c:2bbc%20(Preferred)
Default Gateway . . . . . . . . . :
NetBIOS over Tcpip. . . . . . . . : Disabled

And when you install Membase, which IP address does it list in the "Manage Servers" screen (before you attempt to cluster anything)?

I have the same problem with version 1.7.1.1. I'm currently trying to set up a development environment with virtual machines (although we will use physical machines in the production environment). The adapters for the virtual machines look like this:

Ethernet adapter Local Area Connection 2:
 
   Connection-specific DNS Suffix  . : ad.company.se
   Link-local IPv6 Address . . . . . : fe80::bd38:898e:e351:bcca%13
   IPv4 Address. . . . . . . . . . . : 172.19.20.6
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 172.19.20.1
 
Ethernet adapter Local Area Connection:
 
   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
 
Tunnel adapter isatap.{0188DB14-E29A-4227-8ED3-DD1FDD954990}:
 
   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
 
Tunnel adapter isatap.ad.company.se:
 
   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . : ad.company.se

When I installed Membase it bound to a 169.254.0.0/16 address, but using the instructions from http://www.couchbase.org/forums/thread/issues-dhcp-development-laptop I was able to bind it to the action ip instead (172.19.20.6).

But when I try to add the second server to the cluster I get the error mentioned above:
"Attention - Failed to reach erlang port mapper. Timeout connecting to "172.19.20.6" on port "4369". This could be due to an incorrect host/port combination or a firewall in place between the servers."

I have verified that the servers can reach each other, when I telnet one server from the other on port 4369 it works, and the firewalls are off on both machines, so it's not a network issue.

Help would be appreciated!

You'll have to apply the same "fix" to the second server since it is likely trying to talk to the first one over it's 169 address

Perry

Thanks perry for giving this informative post you have given best solution of related query.....