Uploaded image for project: 'Couchbase Server'
  1. Couchbase Server
  2. MB-5884

Moxi port conflict when starting multiple server on the same node using cluster_run

    XMLWordPrintable

Details

    • Bug
    • Resolution: Cannot Reproduce
    • Major
    • 2.0
    • None
    • ns_server
    • Security Level: Public
    • None

    Description

      Using ./cluster_run -n4 to start up 4 servers locally, and try testrunner to test XDCR with rebalance and failover.

      Sometime moxi server is unable to start due to some port issue and ns_port_server just kept crashing. Looks it is not related to XDCR and is a generic issue.

      [ns_server:info] [2012-07-11 19:10:56] [n_3@10.17.17.29:ns_log:ns_log:handle_cast:115] suppressing duplicate log ns_port_server:0("Port server moxi on node 'n_3@10.17.17.29' exited with status 1. Restar\
      ting. Messages: 2012-07-11 19:10:56: (cproxy_config.c.317) env: MOXI_SASL_PLAIN_USR (8)\n2012-07-11 19:10:58: (cproxy.c.330) ERROR: could not listen on port 12009. Please use -Z port_listen=PORT_NUM to \
      specify a different port number.") because it's been seen 8 times in the past 0.398461 secs (last seen 0.051743 secs ago
      [error_logger:error] [2012-07-11 19:10:56] [n_3@10.17.17.29:error_logger:ale_error_logger_handler:log_msg:76] ** Generic server <0.2424.2> terminating

        • Last message in was {#Port<0.70589>,
          Unknown macro: {exit_status,1}

          }

        • When Server state == {state,#Port<0.70589>,moxi,
          {["2012-07-11 19:10:58: (cproxy.c.330) ERROR: could not listen on port 12009. Please use -Z port_listen=PORT_NUM to specify a different port number.", "2012-07-11 19:10:56: (cproxy_config.c.317) env: MOXI_SASL_PLAIN_USR (8)", empty], [empty,empty,empty,empty,empty,empty,empty, empty,empty,empty,empty,empty,empty,empty, empty,empty,empty,empty,empty,empty,empty, empty,empty,empty,empty,empty,empty,empty, empty,empty,empty,empty,empty,empty,empty, empty,empty,empty,empty,empty,empty,empty, empty,empty,empty,empty,empty,empty,empty, empty,empty,empty,empty,empty,empty,empty, empty,empty,empty,empty,empty,empty,empty, empty,empty,empty,empty,empty,empty,empty, empty,empty,empty,empty,empty,empty,empty, empty,empty,empty,empty,empty,empty,empty, empty,empty,empty,empty,empty,empty,empty, empty,empty,empty,empty,empty,empty]}

          ,
          {ok,{1342059056604067,#Ref<0.0.14.256496>}},
          ["2012-07-11 19:10:58: (cproxy.c.330) ERROR: could not listen on port 12009. Please use -Z port_listen=PORT_NUM to specify a different port number.",
          "2012-07-11 19:10:56: (cproxy_config.c.317) env: MOXI_SASL_PLAIN_USR (8)"],
          0,false}

        • Reason for termination ==
        • {abnormal,1}

          [error_logger:error] [2012-07-11 19:10:56] [n_3@10.17.17.29:error_logger:ale_error_logger_handler:log_report:72]
          =========================CRASH REPORT=========================
          crasher:
          initial call: ns_port_server:init/1
          pid: <0.2424.2>
          registered_name: []
          exception exit: {abnormal,1}

          in function gen_server:terminate/6
          ancestors: [ns_moxi_sup,ns_server_sup,ns_server_cluster_sup,<0.60.0>]
          messages: [

          {'EXIT',#Port<0.70589>,normal}

          ]
          links: [<0.2399.2>]
          dictionary: []
          trap_exit: true
          status: running
          heap_size: 2584
          stack_size: 24
          reductions: 2384
          neighbours:

      [error_logger:error] [2012-07-11 19:10:56] [n_3@10.17.17.29:error_logger:ale_error_logger_handler:log_report:72]

      Attachments

        No reviews matched the request. Check your Options in the drop-down menu of this sections header.

        Activity

          People

            ketaki Ketaki Gangal (Inactive)
            junyi Junyi Xie (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Gerrit Reviews

                There are no open Gerrit changes

                PagerDuty