Couchbase 7.1.1-3175 Enterprise edition fails to start on Windows server 2019 standard edition

Couchbase worked a couple days ago, but now, it will not start.
It is running under “Local System” account.

Windows EventView says "CouchbaseServer Erlang machine stopped instantly (distribution name conflict?). The service is not restarted, ignoring OnFail option."

The only Couchbase logs that get updated is the babysitter.log

[ns_server:info,2023-02-20T10:48:32.060-08:00,babysitter_of_ns_1@cb.local:<0.118.0>:ns_babysitter:init_logging:137]Brought up babysitter logging
[ns_server:info,2023-02-20T10:48:32.066-08:00,babysitter_of_ns_1@cb.local:<0.118.0>:ns_babysitter:log_pending:102]Static config terms:
[{error_logger_mf_dir,"C:/Program Files/Couchbase/Server/var/lib/couchbase/logs"},
 {path_config_bindir,"C:/Program Files/Couchbase/Server/bin"},
 {path_config_etcdir,"C:/Program Files/Couchbase/Server/etc/couchbase"},
 {path_config_libdir,"C:/Program Files/Couchbase/Server/lib"},
 {path_config_datadir,"C:/Program Files/Couchbase/Server/var/lib/couchbase"},
 {path_config_tmpdir,"C:/Program Files/Couchbase/Server/var/lib/couchbase/tmp"},
 {path_config_secdir,"C:/Program Files/Couchbase/Server/etc/security"},
 {nodefile,"C:/Program Files/Couchbase/Server/var/lib/couchbase/couchbase-server.node"},
 {loglevel_default,debug},
 {loglevel_couchdb,info},
 {loglevel_ns_server,debug},
 {loglevel_error_logger,debug},
 {loglevel_user,debug},
 {loglevel_menelaus,debug},
 {loglevel_ns_doctor,debug},
 {loglevel_stats,debug},
 {loglevel_rebalance,debug},
 {loglevel_cluster,debug},
 {loglevel_views,debug},
 {loglevel_mapreduce_errors,debug},
 {loglevel_xdcr,debug},
 {loglevel_access,info},
 {loglevel_cbas,debug},
 {disk_sink_opts,[{rotation,[{compress,true},
                             {size,41943040},
                             {num_files,10},
                             {buffer_size_max,52428800}]}]},
 {disk_sink_opts_json_rpc,[{rotation,[{compress,true},
                                      {size,41943040},
                                      {num_files,2},
                                      {buffer_size_max,52428800}]}]},
 {net_kernel_verbosity,10}]
[ns_server:info,2023-02-20T10:48:32.073-08:00,babysitter_of_ns_1@cb.local:sigar<0.126.0>:sigar:spawn_sigar:135]Spawing sigar process 'portsigar for babysitter_of_ns_1@cb.local'("c:/Program Files/Couchbase/Server/bin/sigar_port") with babysitter pid: 2096
[ns_server:error,2023-02-20T10:48:32.111-08:00,babysitter_of_ns_1@cb.local:sigar<0.126.0>:sigar:recv_data_loop:349]Received exit_status 1 from sigar
[error_logger:error,2023-02-20T10:48:32.150-08:00,babysitter_of_ns_1@cb.local:sigar<0.126.0>:ale_error_logger_handler:do_log:101]
=========================ERROR REPORT=========================
** Generic server sigar terminating 
** Last message in was get_cgroups_info
** When Server state == {state,#Port<0.7>,undefined,undefined,undefined}
** Reason for termination ==
** {{sigar,1},
    [{sigar,recv_data_loop,2,[{file,"src/sigar.erl"},{line,350}]},
     {sigar,update_sigar_data,1,[{file,"src/sigar.erl"},{line,420}]},
     {sigar,handle_call,3,[{file,"src/sigar.erl"},{line,97}]},
     {gen_server,try_handle_call,4,[{file,"gen_server.erl"},{line,721}]},
     {gen_server,handle_msg,6,[{file,"gen_server.erl"},{line,750}]},
     {proc_lib,init_p_do_apply,3,[{file,"proc_lib.erl"},{line,226}]}]}
** Client <0.118.0> stacktrace
** [{gen,do_call,4,[{file,"gen.erl"},{line,233}]},
    {gen_server,call,2,[{file,"gen_server.erl"},{line,235}]},
    {ns_babysitter,determine_cpu_num,0,
                   [{file,"src/ns_babysitter.erl"},{line,277}]},
    {ns_babysitter,maybe_set_cpu_count_env,0,
                   [{file,"src/ns_babysitter.erl"},{line,268}]},
    {ns_babysitter,start,2,[{file,"src/ns_babysitter.erl"},{line,41}]},
    {application_master,start_it_old,4,
                        [{file,"application_master.erl"},{line,293}]}]

[error_logger:error,2023-02-20T10:48:32.155-08:00,babysitter_of_ns_1@cb.local:sigar<0.126.0>:ale_error_logger_handler:do_log:101]
=========================CRASH REPORT=========================
  crasher:
    initial call: sigar:init/1
    pid: <0.126.0>
    registered_name: sigar
    exception exit: {sigar,1}
      in function  sigar:recv_data_loop/2 (src/sigar.erl, line 350)
      in call from sigar:update_sigar_data/1 (src/sigar.erl, line 420)
      in call from sigar:handle_call/3 (src/sigar.erl, line 97)
      in call from gen_server:try_handle_call/4 (gen_server.erl, line 721)
      in call from gen_server:handle_msg/6 (gen_server.erl, line 750)
    ancestors: [<0.118.0>]
    message_queue_len: 1
    messages: [{#Port<0.7>,eof}]
    links: [<0.118.0>,#Port<0.7>]
    dictionary: []
    trap_exit: false
    status: running
    heap_size: 6772
    stack_size: 29
    reductions: 34513
  neighbours:

[error_logger:error,2023-02-20T10:48:32.156-08:00,babysitter_of_ns_1@cb.local:<0.117.0>:ale_error_logger_handler:do_log:101]
=========================CRASH REPORT=========================
  crasher:
    initial call: application_master:init/4
    pid: <0.117.0>
    registered_name: []
    exception exit: {bad_return,
                        {{ns_babysitter,start,[normal,[]]},
                         {'EXIT',
                             {{sigar,1},
                              {gen_server,call,[sigar,get_cgroups_info]}}}}}
      in function  application_master:init/4 (application_master.erl, line 142)
    ancestors: [<0.116.0>]
    message_queue_len: 1
    messages: [{'EXIT',<0.118.0>,normal}]
    links: [<0.116.0>,<0.44.0>]
    dictionary: []
    trap_exit: true
    status: running
    heap_size: 376
    stack_size: 29
    reductions: 166
  neighbours:

[error_logger:info,2023-02-20T10:48:32.156-08:00,babysitter_of_ns_1@cb.local:application_controller<0.44.0>:ale_error_logger_handler:do_log:101]
=========================NOTICE REPORT=========================
    application: ns_babysitter
    exited: {bad_return,
                {{ns_babysitter,start,[normal,[]]},
                 {'EXIT',
                     {{sigar,1},{gen_server,call,[sigar,get_cgroups_info]}}}}}
    type: permanent


1 Like

Did you find a solution to this?

I did not. When Couchbase help asked me to log on to the web server and retrieve the logs, I knew this wasn’t going anywhere. Couchbase server will not start and there is only one log file being written to. Couchbase help was either a bot, or did not read what I wrote.

@potto I don’t know much about this but recalled seeing a previous forum post that looks related - Couchbase 7.1.1 fails to start on Windows server 2016 standard edition - #10 by FarisAhmed. The tldr being that you need to use a user with admin permissions on window server.

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.