Couchbase 4.5 Windows Returning Error Cluster Setup


#1

Hi, Once Couchbase 4.5 is installed with more or less default settings (reduced RAM) the beer-sample will not load and the Server Node is in Pend State. Within the logs there are the following errors:

Control connection to memcached on ‘ns_1@127.0.0.1’ disconnected: {error,
closed}

Control connection to memcached on ‘ns_1@127.0.0.1’ disconnected: {{badmatch,
{error,
closed}},
[{mc_client_binary,
cmd_vocal,
6,
[{file,
“src/mc_client_binary.erl”},
{line,
146}]},
{mc_client_binary,
stats,4,
[{file,
“src/mc_client_binary.erl”},
{line,
418}]},
{ns_memcached,
handle_info,
2,
[{file,
“src/ns_memcached.erl”},
{line,
723}]},
{gen_server,
handle_msg,
5,
[{file,
“gen_server.erl”},
{line,
604}]},
{ns_memcached,
init,1,
[{file,
“src/ns_memcached.erl”},
{line,
177}]},
{gen_server,
init_it,
6,
[{file,
“gen_server.erl”},
{line,
304}]},
{proc_lib,
init_p_do_apply,
3,
[{file,
“proc_lib.erl”},
{line,
239}]}]

and many of these: Service ‘memcached’ exited with status 255

I am not able to view the documents in the default bucket.
When I try to view the beer-sample bucket the following error is displayed:

Any Ideas on what might be causing the issue?

When I uninstall and use the community edition 4.1 the issues are not seen; only seen on 4.5


#2

Which version of Windows are you using?


#3

Windows 10 Pro - which I understand that windows 10 should now be supported?


#4

There’s a known issue with Windows 10 Anniversary Edition. Check out either our release notes or @btburnett3’s blog where he gave some details.


#5

Thanks for the support ingenthr. I better get it going on my server then!

Cal


#6

It’s nice to see that this is a known issue.

However, it still is a bad situation for me. We’re a small shop (just two devs) and I’ve been running couchbase (community) for several years on my windows box while writing code. (We run on linux for dev and prod) I was unpleasantly surprised when couchbase spontaneously died following my last windows update.

I guess I could roll back the windows update, but I’d rather not. The idea of never updating windows again doesn’t seem like a good one.

I hope to see a more realistic fix than having to run couchbase via docker sometime sooner than later.

Travis


#7

We’re actively working on a better solution. I think @don can give additional detail as it becomes available.