[rabbitmq-discuss] Unable to cluster..

[iceblaze]

Hello Emilie et all,

OK, so I am now getting a different, cryptic error when trying to cluster:

[root at rabbit-test2 ~]# rabbitmqctl cluster rabbit at rabbit-test1
Clustering node 'rabbit at rabbit-test2' with ['rabbit at rabbit-test1'] ...
Error: {unable_to_join_cluster,
           ['rabbit at rabbit-test1'],
           {aborted,
               {function_clause,
                   [{mnesia_schema,cs2list,
                        [{cstruct,schema,set,[],
                             ['rabbit at rabbit-test1'],
                             [],0,read_write,false,[],[],false,schema,
                             [table,cstruct],
                             [],[],
                             {{1336,612893,960781},'rabbit at rabbit-test1'},
                             {{6,0},
                              {'rabbit at rabbit-test1
',{1337,33903,595724}}}}]},
                    {mnesia_schema,do_merge_schema,0},
                    {mnesia_tm,apply_fun,3},
                    {mnesia_tm,execute_transaction,5},
                    {mnesia_schema,schema_coordinator,3}]}}}


And status now passes correctly as well:

[root at rabbit-test2 ~]# !90
rabbitmqctl -n rabbit at rabbit-test1 status
Status of node 'rabbit at rabbit-test1' ...
[{pid,3680},
 {running_applications,[{rabbit,"RabbitMQ","2.8.2"},
                        {os_mon,"CPO  CXC 138 46","2.2.6"},
                        {sasl,"SASL  CXC 138 11","2.1.9.4"},
                        {mnesia,"MNESIA  CXC 138 12","4.4.19"},
                        {stdlib,"ERTS  CXC 138 10","1.17.4"},
                        {kernel,"ERTS  CXC 138 10","2.14.4"}]},
 {os,{unix,linux}},
 {erlang_version,"Erlang R14B03 (erts-5.8.4) [source] [64-bit] [smp:8:8]
[rq:8] [async-threads:30] [kernel-poll:true]\n"},
 {memory,[{total,25802032},
          {processes,10259256},
          {processes_used,10245896},
          {system,15542776},
          {atom,1136673},
          {atom_used,1134812},
          {binary,82912},
          {code,11341457},
          {ets,783296}]},
 {vm_memory_high_watermark,0.3999999999359184},
 {vm_memory_limit,2496816742},
 {disk_free_limit,6242041856},
 {disk_free,449332170752},
 {file_descriptors,[{total_limit,924},
                    {total_used,3},
                    {sockets_limit,829},
                    {sockets_used,1}]},
 {processes,[{limit,1048576},{used,125}]},
 {run_queue,0},
 {uptime,3743}]
...done.

Thanks,

-James

On Mon, May 14, 2012 at 2:17 AM, iceblaze <iceblaze at gmail.com> wrote:

> Hello Emile,
>
> Ha! I see that I actually did a status against itself (rabbit-test2), and
> not rabbit at rabbit-test1. I will retry and report if I'm still having the
> issue.
>
> -James
>
>
> On Mon, May 14, 2012 at 2:08 AM, iceblaze <iceblaze at gmail.com> wrote:
>
>> Hello Emile,
>>
>> Yes, I did provide a status in my previous email, which suggests it's
>> reachable and not a firewall issue.
>>
>> Cheers,
>>
>> -James
>>
>>
>> On Mon, May 14, 2012 at 2:05 AM, Emile Joubert <emile at rabbitmq.com>wrote:
>>
>>> Hi,
>>>
>>> On 14/05/12 02:36, iceblaze wrote:
>>> > I seem to be having an issue clustering and I don't know why. I
>>> > followed the clustering guide to the T, and my node is reachable.
>>>
>>> The most common cause of these symptoms is a firewall. Have you taken a
>>> look at http://www.rabbitmq.com/clustering.html#firewall and confirmed
>>> that the nodes are reachable in the way required for clustering?
>>>
>>> Also check that you are able to obtain the broker status from each the
>>> prospective clustering partner node:
>>> [root at rabbit-test2 ~]# rabbitmqctl -n rabbit at rabbit-test1 status
>>>
>>>
>>> -Emile
>>>
>>>
>>>
>>
>>
>> --
>> "Of course, the actual government of any computer is run by that fascist
>> dictator known as the operating system. But a wise dictator knows when to
>> let the people think they're capitalists--and when to let them think
>> they're communists." - Programming Perl third edition
>>
>
>
>
> --
> "Of course, the actual government of any computer is run by that fascist
> dictator known as the operating system. But a wise dictator knows when to
> let the people think they're capitalists--and when to let them think
> they're communists." - Programming Perl third edition
>



-- 
"Of course, the actual government of any computer is run by that fascist
dictator known as the operating system. But a wise dictator knows when to
let the people think they're capitalists--and when to let them think
they're communists." - Programming Perl third edition
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20120514/b970f642/attachment.htm>