I see this same error in the logs every few days in the couchbase console:
Control connection to memcached on 'ns_1@10.0.0.10' disconnected: {badmatch,
{error,
timeout}}
Then in the same second it will say:
Bucket "auth" loaded on node 'ns_1@10.0.0.10' in 0 seconds.
I looked into the error.log and saw these details for the first couple occurrences:
[ns_doctor:error,2015-03-22T8:21:30.829,ns_1@10.0.0.30:ns_log<0.11472.0>:ns_doctor:get_node:189]Error attempting to get node 'ns_1@10.0.0.10': {exit,
{noproc,
{gen_server,call,
[ns_doctor,
{get_node,
'ns_1@10.0.0.10'}]}}}
[stats:error,2015-04-22T17:13:30.067,ns_1@10.0.0.30:<0.29087.6>:stats_collector:handle_info:124]Exception in stats collector: {exit,
{{badmatch,{error,timeout}},
{gen_server,call,
['ns_memcached-auth',
{stats,<<>>},
180000]}},
[{gen_server,call,3,
[{file,"gen_server.erl"},{line,188}]},
{ns_memcached,do_call,3,
[{file,"src/ns_memcached.erl"},
{line,1399}]},
{stats_collector,grab_all_stats,1,
[{file,"src/stats_collector.erl"},
{line,84}]},
{stats_collector,handle_info,2,
[{file,"src/stats_collector.erl"},
{line,116}]},
{gen_server,handle_msg,5,
[{file,"gen_server.erl"},{line,604}]},
{proc_lib,init_p_do_apply,3,
[{file,"proc_lib.erl"},{line,239}]}]}
And these for subsequent occurrences:
[ns_server:error,2015-05-04T19:57:03.107,ns_1@10.0.0.30:ns_doctor<0.11518.0>:ns_doctor:update_status:229]The following buckets became not ready on node 'ns_1@10.0.0.10': ["auth"], those of them are active ["auth"]
[ns_server:error,2015-05-04T19:57:03.112,ns_1@10.0.0.30:ns_doctor<0.11518.0>:ns_doctor:update_status:229]The following buckets became not ready on node 'ns_1@10.0.0.30': ["auth"], those of them are active ["auth"]
We’re running Couchbase Server Enterprise 3.0.2 on Ubuntu, in a cluster with 2 nodes and sync gateway on each node. We have only noticed one possible error client side due to this, where a client using a mobile couchbase lite client wasn’t able to replicate all their documents when doing the replication around the time one of these issues occurred. We’re not sure if it’s related though, so is this a normal couchbase error that doesn’t affect anything that we can ignore, or do we have something configured wrong on the server?
Thanks in advance for any help anyone can give on this topic.