[rabbitmq-discuss] Automatic clustering

Michael Journo gobadiah at gmail.com
Fri May 3 12:50:31 BST 2013


Hello,

I'm using the very last rabbitmq version (3.1.0), with 3 nodes and I have
trouble clustering them in an automatic way (using rabbit.config). I'm not
sure it matters but 2 of the nodes are running debian 6 and one is running
debian 7 (beta). But anyway this happens even with only the two squeezes.

In short, if I don't specify any rabbit.config, and do the following :
<node1>: rabbitmq-server -detached
<node2>: rabbitmq-server -detached
<node2>: rabbitmqctl stop_app
<node2>: rabbitmqctl join_cluster [email protected]<node1>
<node2>: rabbitmqctl start_app
<node3>: rabbitmq-server -detached
<node3>: rabbitmqctl stop_app
<node3>: rabbitmqctl join_cluster [email protected]<node1>
<node3>: rabbitmqctl start_app

The cluster works perfectly, BUT if I try to set it up in the rabbit.config
file like so :

           {cluster_nodes, {['[email protected]<node1>', '[email protected]<node2>',
'[email protected]<node3>'],
 disk}},

The first node I start does fine, but the other two crash every time.

Here are a few logs :

> *startup_err*

Crash dump was written to: erl_crash.dump
init terminating in do_boot ()

> *startup_log*

              RabbitMQ 3.1.0. Copyright (C) 2007-2013 VMware, Inc.
  ##  ##      Licensed under the MPL.  See http://www.rabbitmq.com/
  ##  ##
  ##########  Logs: /var/log/rabbitmq/[email protected]<node2>.log
  ######  ##        /var/log/rabbitmq/[email protected]<node2>-sasl.log
  ##########
              Starting broker...

BOOT FAILED
===========

Error description:
   function_clause

Log files (may contain more information):
   /var/log/rabbitmq/[email protected]<node2>.log
   /var/log/rabbitmq/[email protected]<node2>-sasl.log

Stack trace:
   [{rabbit_table,create_local_copy,[disk],[]},
    {rabbit_mnesia,init_db,3,[]},
    {rabbit_mnesia,init_db_and_upgrade,3,[]},
    {rabbit_mnesia,init_from_config,0,[]},
    {rabbit_mnesia,init,0,[]},
    {rabbit,'-run_boot_step/1-lc$^1/1-1-',1,[]},
    {rabbit,run_boot_step,1,[]},
    {rabbit,'-start/2-lc$^0/1-0-',1,[]}]



BOOT FAILED
===========

Error description:
   {could_not_start,rabbit,
       {bad_return,
           {{rabbit,start,[normal,[]]},
            {'EXIT',{rabbit,failure_during_boot,function_clause}}}}}

Log files (may contain more information):
   /var/log/rabbitmq/[email protected]<node2>.log
   /var/log/rabbitmq/[email protected]<node2>-sasl.log

{"init terminating in
do_boot",{rabbit,failure_during_boot,{could_not_start,rabbit,{bad_return,{{rabbit,start,[normal,[]]},{'EXIT',{rabbit,failure_during_boot,function_clause}}}}}}}

> *[email protected]<node2>.log*

=INFO REPORT==== 3-May-2013::13:25:11 ===
Starting RabbitMQ 3.1.0 on Erlang R15B01
Copyright (C) 2007-2013 VMware, Inc.
Licensed under the MPL.  See http://www.rabbitmq.com/

=INFO REPORT==== 3-May-2013::13:25:11 ===
node           : [email protected]<node2>
home dir       : /var/lib/rabbitmq
cookie hash    : *************************
log            : /var/log/rabbitmq/[email protected]<node2>.log
sasl log       : /var/log/rabbitmq/[email protected]<node2>-sasl.log
database dir   : /var/lib/rabbitmq/mnesia/[email protected]<node2>

=INFO REPORT==== 3-May-2013::13:25:11 ===
Limiting to approx 924 file handles (829 sockets)

=INFO REPORT==== 3-May-2013::13:25:11 ===
Error description:
   function_clause

Log files (may contain more information):
   /var/log/rabbitmq/[email protected]<node2>.log
   /var/log/rabbitmq/[email protected]<node2>-sasl.log

Stack trace:
   [{rabbit_table,create_local_copy,[disk],[]},
    {rabbit_mnesia,init_db,3,[]},
    {rabbit_mnesia,init_db_and_upgrade,3,[]},
    {rabbit_mnesia,init_from_config,0,[]},
    {rabbit_mnesia,init,0,[]},
    {rabbit,'-run_boot_step/1-lc$^1/1-1-',1,[]},
    {rabbit,run_boot_step,1,[]},
    {rabbit,'-start/2-lc$^0/1-0-',1,[]}]


=INFO REPORT==== 3-May-2013::13:25:12 ===
Error description:
   {could_not_start,rabbit,
       {bad_return,
           {{rabbit,start,[normal,[]]},
            {'EXIT',{rabbit,failure_during_boot,function_clause}}}}}

Log files (may contain more information):
   /var/log/rabbitmq/[email protected]<node2>.log
   /var/log/rabbitmq/[email protected]<node2>-sasl.log

> *[email protected]<node2>-sasl.log*

=CRASH REPORT==== 3-May-2013::13:25:12 ===
  crasher:
    initial call: application_master:init/4
    pid: <0.70.0>
    registered_name: []
    exception exit: {bad_return,
                        {{rabbit,start,[normal,[]]},
                         {'EXIT',
                             {rabbit,failure_during_boot,function_clause}}}}
      in function  application_master:init/4 (application_master.erl, line
138)
    ancestors: [<0.69.0>]
    messages: [{'EXIT',<0.71.0>,normal}]
    links: [<0.69.0>,<0.7.0>]
    dictionary: []
    trap_exit: true
    status: running
    heap_size: 2584
    stack_size: 24
    reductions: 206
  neighbours:

I'll trying differents things but any help would be appreciated.

Thanks !

-- 
michael
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20130503/073346b4/attachment.htm>


More information about the rabbitmq-discuss mailing list