Couchbase not starting after reboot

i am using couchbase 4.0. but after sudden restart cluster is not coming up. one node is unhealthy and other is warnup active.
Form this https://issues.couchbase.com/browse/MB-16826 seems like bug in 4.0. just wanted to know recovery process.
below is the error.

/opt/couchbase/bin/couchbase-server bucket-list -u Administrator-p kodiak@123 -c 10.2.2.23:8091
{error_logger,{{2016,3,21},{13,23,58}},“Protocol: ~tp: the name babysitter_of_ns_1@127.0.0.1 seems to be in use by another Erlang node”,[“inet_tcp”]}
{error_logger,{{2016,3,21},{13,23,58}},crash_report,[[{initial_call,{net_kernel,init,[‘Argument__1’]}},{pid,<0.21.0>},{registered_name,[]},{error_info,{exit,{error,badarg},[{gen_server,init_it,6,[{file,“gen_server.erl”},{line,320}]},{proc_lib,init_p_do_apply,3,[{file,“proc_lib.erl”},{line,239}]}]}},{ancestors,[net_sup,kernel_sup,<0.10.0>]},{messages,[]},{links,[#Port<0.64>,<0.18.0>]},{dictionary,[{longnames,true}]},{trap_exit,true},{status,running},{heap_size,987},{stack_size,27},{reductions,1345}],[]]}
{error_logger,{{2016,3,21},{13,23,58}},supervisor_report,[{supervisor,{local,net_sup}},{errorContext,start_error},{reason,{‘EXIT’,nodistribution}},{offender,[{pid,undefined},{name,net_kernel},{mfargs,{net_kernel,start_link,[[‘babysitter_of_ns_1@127.0.0.1’,longnames]]}},{restart_type,permanent},{shutdown,2000},{child_type,worker}]}]}
{error_logger,{{2016,3,21},{13,23,58}},supervisor_report,[{supervisor,{local,kernel_sup}},{errorContext,start_error},{reason,{shutdown,{failed_to_start_child,net_kernel,{‘EXIT’,nodistribution}}}},{offender,[{pid,undefined},{name,net_sup},{mfargs,{erl_distribution,start_link,[]}},{restart_type,permanent},{shutdown,infinity},{child_type,supervisor}]}]}
{error_logger,{{2016,3,21},{13,23,58}},crash_report,[[{initial_call,{application_master,init,[‘Argument__1’,‘Argument__2’,‘Argument__3’,‘Argument__4’]}},{pid,<0.9.0>},{registered_name,[]},{error_info,{exit,{{shutdown,{failed_to_start_child,net_sup,{shutdown,{failed_to_start_child,net_kernel,{‘EXIT’,nodistribution}}}}},{kernel,start,[normal,[]]}},[{application_master,init,4,[{file,“application_master.erl”},{line,133}]},{proc_lib,init_p_do_apply,3,[{file,“proc_lib.erl”},{line,239}]}]}},{ancestors,[<0.8.0>]},{messages,[{‘EXIT’,<0.10.0>,normal}]},{links,[<0.8.0>,<0.7.0>]},{dictionary,[]},{trap_exit,true},{status,running},{heap_size,376},{stack_size,27},{reductions,117}],[]]}
{error_logger,{{2016,3,21},{13,23,58}},std_info,[{application,kernel},{exited,{{shutdown,{failed_to_start_child,net_sup,{shutdown,{failed_to_start_child,net_kernel,{‘EXIT’,nodistribution}}}}},{kernel,start,[normal,[]]}}},{type,permanent}]}
{“Kernel pid terminated”,application_controller,"{application_start_failure,kernel,{{shutdown,{failed_to_start_child,net_sup,{shutdown,{failed_to_start_child,net_kernel,{‘EXIT’,nodistribution}}}}},{kernel,start,[normal,[]]}}}"}

Crash dump was written to: erl_crash.dump.1458546836.20363.babysitter
Kernel pid terminated (application_controller) ({application_start_failure,kernel,{{shutdown,{failed_to_start_child,net_sup,{shutdown,{failed_to_start_child,net_kernel,{‘EXIT’,nodistribution}}}}},{k

Hi Arihant, Issue you mentioned MB-16826 is fixed in upcoming 4.1.1 release and soon will be available for download.

Thanks!

Anil Kumar