[rabbitmq-discuss] Can't get cluster to work on 2 Windows Machines
caloggins
christopher.loggins at gmail.com
Fri Apr 27 17:44:48 BST 2012
I'm attempting to get a cluster working between a 2008 R2 (rabbit1)
and Windows 7 (rabbit2). I've copied the .erlang.cookie files to all
the directories, opened ports on the firewalls, etc. I can do a status
locally, but not remotely. As illustrated below, rabbitmqctl status
shows the two nodes are not talking. What can/should I next check?
rabbit1 status:
--------------------
c:\Program Files (x86)\RabbitMQ Server
\rabbitmq_server-2.8.1\sbin>rabbitmqctl status
Status of node rabbit at rabbit1 ...
[{pid,6700},
{running_applications,
[{rabbitmq_management,"RabbitMQ Management Console","2.8.1"},
{rabbitmq_management_agent,"RabbitMQ Management Agent","2.8.1"},
{amqp_client,"RabbitMQ AMQP Client","2.8.1"},
{rabbit,"RabbitMQ","2.8.1"},
{os_mon,"CPO CXC 138 46","2.2.9"},
{sasl,"SASL CXC 138 11","2.2.1"},
{rabbitmq_mochiweb,"RabbitMQ Mochiweb Embedding","2.8.1"},
{webmachine,"webmachine","1.7.0-rmq2.8.1-hg"},
{mochiweb,"MochiMedia Web Server","1.3-rmq2.8.1-git"},
{inets,"INETS CXC 138 49","5.9"},
{mnesia,"MNESIA CXC 138 12","4.7"},
{stdlib,"ERTS CXC 138 10","1.18.1"},
{kernel,"ERTS CXC 138 10","2.15.1"}]},
{os,{win32,nt}},
{erlang_version,
"Erlang R15B01 (erts-5.9.1) [64-bit] [smp:2:2] [async-threads:
30]\n"},
{memory,
[{total,33205360},
{processes,12402021},
{processes_used,12401872},
{system,20803339},
{atom,561761},
{atom_used,544299},
{binary,88496},
{code,15357746},
{ets,1272920}]},
{vm_memory_high_watermark,0.39999999981371526},
{vm_memory_limit,1717800140},
{file_descriptors,
[{total_limit,924},{total_used,4},{sockets_limit,829},
{sockets_used,2}]},
{processes,[{limit,1048576},{used,176}]},
{run_queue,0},
{uptime,1368}]
...done.
c:\Program Files (x86)\RabbitMQ Server
\rabbitmq_server-2.8.1\sbin>rabbitmqctl -n rabbit at rabbit2 status
Status of node 'rabbit at rabbit2' ...
Error: unable to connect to node 'rabbit at rabbit2': nodedown
DIAGNOSTICS
===========
nodes in question: ['rabbit at rabbit2']
hosts, their running nodes and ports:
- rabbit2: [{rabbit,45001}]
current node details:
- node name: rabbitmqctl6126 at rabbit1
- home dir: W:\
- cookie hash: 6jCR7HdybYQeos3l+beiNQ==
rabbit2 status:
--------------------
c:\Program Files (x86)\RabbitMQ Server
\rabbitmq_server-2.8.1\sbin>rabbitmqctl status
Status of node 'rabbit at rabbit2' ...
[{pid,10024},
{running_applications,
[{rabbitmq_management,"RabbitMQ Management Console","2.8.1"},
{rabbitmq_management_agent,"RabbitMQ Management Agent","2.8.1"},
{amqp_client,"RabbitMQ AMQP Client","2.8.1"},
{rabbit,"RabbitMQ","2.8.1"},
{os_mon,"CPO CXC 138 46","2.2.9"},
{sasl,"SASL CXC 138 11","2.2.1"},
{rabbitmq_mochiweb,"RabbitMQ Mochiweb Embedding","2.8.1"},
{webmachine,"webmachine","1.7.0-rmq2.8.1-hg"},
{mochiweb,"MochiMedia Web Server","1.3-rmq2.8.1-git"},
{inets,"INETS CXC 138 49","5.9"},
{mnesia,"MNESIA CXC 138 12","4.7"},
{stdlib,"ERTS CXC 138 10","1.18.1"},
{kernel,"ERTS CXC 138 10","2.15.1"}]},
{os,{win32,nt}},
{erlang_version,
"Erlang R15B01 (erts-5.9.1) [64-bit] [smp:8:8] [async-threads:
30]\n"},
{memory,
[{total,34142224},
{processes,12659829},
{processes_used,12650632},
{system,21482395},
{atom,561761},
{atom_used,544353},
{binary,118144},
{code,15357746},
{ets,1280456}]},
{vm_memory_high_watermark,0.4},
{vm_memory_limit,3416358912},
{file_descriptors,
[{total_limit,924},{total_used,4},{sockets_limit,829},
{sockets_used,2}]},
{processes,[{limit,1048576},{used,182}]},
{run_queue,0},
{uptime,1657}]
...done.
c:\Program Files (x86)\RabbitMQ Server
\rabbitmq_server-2.8.1\sbin>rabbitmqctl -n rabbit at rabbit1 status
Status of node rabbit at rabbit1 ...
Error: unable to connect to node rabbit at rabbit1: nodedown
DIAGNOSTICS
===========
nodes in question: [rabbit at rabbit1]
hosts, their running nodes and ports:
- rabbit1: [{rabbit,45001}]
current node details:
- node name: 'rabbitmqctl17565 at rabbit2'
- home dir: W:\
- cookie hash: 6jCR7HdybYQeos3l+beiNQ==
rabbit1 debug:
---------------------
** Found 0 name clashes in code paths
+---+ +---+
| | | |
| | | |
| | | |
| +---+ +-------+
| |
| RabbitMQ +---+ |
| | | |
| v2.8.1 +---+ |
| |
+-------------------+
AMQP 0-9-1 / 0-9 / 0-8
Copyright (C) 2007-2012 VMware, Inc.
Licensed under the MPL. See http://www.rabbitmq.com/
node : rabbit at rabbit1
app descriptor : c:/Program Files (x86)/RabbitMQ Server/
rabbitmq_server-2.8.1/sbin/../ebin/rabbit.app
home dir : C:\Windows
config file(s) : c:/Users/christopher.loggins/AppData/Roaming/RabbitMQ/
rabbitmq.config
cookie hash : 6jCR7HdybYQeos3l+beiNQ==
log : C:/Users/christopher.loggins/AppData/Roaming/RabbitMQ/
log/rabbit at rabbit1.log
sasl log : C:/Users/christopher.loggins/AppData/Roaming/RabbitMQ/
log/rabbit at rabbit1-sasl.log
database dir : c:/Users/christopher.loggins/AppData/Roaming/RabbitMQ/
db/rabbit at rabbit1-mnesia
erlang version : 5.9.1
-- rabbit boot start
starting file handle cache
server ...done
starting worker
pool ...done
starting
database ...done
starting database
sync ...done
starting codec correctness
check ...done
-- external infrastructure ready
starting plugin
registry ...done
starting auth mechanism cr-
demo ...done
starting auth mechanism
amqplain ...done
starting auth mechanism
plain ...done
starting statistics event
manager ...done
starting logging
server ...done
starting exchange type
direct ...done
starting exchange type
fanout ...done
starting exchange type
headers ...done
starting exchange type
topic ...done
-- kernel ready
starting alarm
handler ...done
starting node
monitor ...done
starting cluster
delegate ...done
starting guid
generator ...done
starting memory
monitor ...done
-- core initialized
starting management
agent ...done
starting exchange, queue and binding
recovery ...done
starting configured
definitions ...done
starting empty DB
check ...done
starting mirror queue slave
sup ...done
starting adding mirrors to
queues ...done
-- message delivery logic ready
starting error log
relay ...done
starting
networking ...done
starting direct
client ...done
starting notify cluster
nodes ...done
broker running
Eshell V5.9.1 (abort with ^G)
(rabbit at rabbit1)1>
rabbit2 debug:
--------------------
** Found 0 name clashes in code paths
+---+ +---+
| | | |
| | | |
| | | |
| +---+ +-------+
| |
| RabbitMQ +---+ |
| | | |
| v2.8.1 +---+ |
| |
+-------------------+
AMQP 0-9-1 / 0-9 / 0-8
Copyright (C) 2007-2012 VMware, Inc.
Licensed under the MPL. See http://www.rabbitmq.com/
node : rabbit at rabbit2
app descriptor : c:/Program Files (x86)/RabbitMQ Server/
rabbitmq_server-2.8.1/sbin/../ebin/rabbit.app
home dir : C:\Windows
config file(s) : c:/Users/christopher.loggins/AppData/Roaming/RabbitMQ/
rabbitmq.config
cookie hash : 6jCR7HdybYQeos3l+beiNQ==
log : C:/Users/christopher.loggins/AppData/Roaming/RabbitMQ/
log/rabbit at rabbit2.log
sasl log : C:/Users/christopher.loggins/AppData/Roaming/RabbitMQ/
log/rabbit at rabbit2-sasl.log
database dir : c:/Users/christopher.loggins/AppData/Roaming/RabbitMQ/
db/rabbit at rabbit2-mnesia
erlang version : 5.9.1
-- rabbit boot start
starting file handle cache
server ...done
starting worker
pool ...done
starting
database ...done
starting database
sync ...done
starting codec correctness
check ...done
-- external infrastructure ready
starting plugin
registry ...done
starting auth mechanism cr-
demo ...done
starting auth mechanism
amqplain ...done
starting auth mechanism
plain ...done
starting statistics event
manager ...done
starting logging
server ...done
starting exchange type
direct ...done
starting exchange type
fanout ...done
starting exchange type
headers ...done
starting exchange type
topic ...done
-- kernel ready
starting alarm
handler ...done
starting node
monitor ...done
starting cluster
delegate ...done
starting guid
generator ...done
starting memory
monitor ...done
-- core initialized
starting management
agent ...done
starting exchange, queue and binding
recovery ...done
starting configured
definitions ...done
starting empty DB
check ...done
starting mirror queue slave
sup ...done
starting adding mirrors to
queues ...done
-- message delivery logic ready
starting error log
relay ...done
starting
networking ...done
starting direct
client ...done
starting notify cluster
nodes ...done
broker running
Eshell V5.9.1 (abort with ^G)
(rabbit at rabbit2)1>
win32sysinfo:Erlang has closed.ok
(rabbit at rabbit2)2>
config on both nodes:
------------------------------
[
{kernel,[{inet_dist_listen_min,45001},{inet_dist_listen_max,45001}]}
].
More information about the rabbitmq-discuss
mailing list