[rabbitmq-discuss] Mnesia connection error in a clustered node on a multi NIC PC

[davidib]

Hi,


After getting a small test cluster to run successfully, I am now
getting an unexpected Mnesia error on one of the nodes.  Here is a
snippet of the messages in my RabbitMQ log for the node rabbit at LAKE-
HP165:

Mnesia('rabbit at LAKE-HP165'): ** ERROR ** Mnesia on 'rabbit at LAKE-HP165'
could not connect to node(s) ['rabbit at LAKE-DS140']

This message is apparently being generated about every 30 seconds!


The cluster seemed to work initially, i.e. I could send out a message
from any node to a pub/sub exchange, and each queue/node properly
received the message.  But after that initial test the RabbitMQ
install on the rabbit at LAKE-HP165 does not seem to work, none of the
other nodes can see it if I do a rabbitmqctl -n ... status, the queue
that I created for this node does not show up in the management
console, when I do a rabbitmqctl status on the problem node, none of
the plugins show up, yet they did show up when I initially instaleld
Rabbit, etc.


Two of the nodes in the cluster are dual NIC machines, i.e. the PCs
sit on two different networks (i.e. one NIC is mapped to 172.x.x.x,
other NIC is mapped to 10.x.x.x).  The node/PC that seems to have
failed has two NICs, but one is permanent (i.e. a true NIC card mapped
to 172.x.x.x) and one (mapped to 10.x.x.x) is via a VPN connection
that I connect/disconnect to as needed.

So, quick questions:
1) Is the dual NIC setup of the nodes the cause of the problem (I
realize that a cluster is not designed to work over a partitioned
network)

2) I know that RabbitMQ/erlang can be 'pinned' to a specific IP
address.port.  Would this be a solution if the dual NICS are the
problem?

OR

Is it just not safe to use a cluster on a dual NIC node (i.e. do I
have to use a federation?)

Well, thanks in advance for any help

Regards
David



I've got a small test cluster of three nodes.  Each node is is Windows
XP machine.  Each node has two NICs, one NIC is mapped to our
development environment network, the other NIC is mapped to our
production network.