<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#CCCCFF" text="#000000">
<div class="moz-cite-prefix">Nope, I'm not reissuing the commands. <br>
<br>
One part I omitted was that there was an previous install of
Rabbit on the server, but the rpm was removed, and an rm -r
/var/lib/rabbitmq/* was done. The .erlang.cookie was also removed,
and I double checked that the mnesia files were definitely removed
afore I did anything. <br>
<br>
<br>
<br>
On 27/06/12 15:31, Simon MacMullen wrote:<br>
</div>
<blockquote cite="mid:4FEB0B21.2030203@rabbitmq.com" type="cite">By
"reclustering" I just mean reissuing "rabbitmqctl reset"
"rabbitmqctl cluster ..." commands, and thus redefining the
cluster.
<br>
<br>
Alternatively, could something be removing files from
/var/lib/rabbitmq/mnesia/ ?
<br>
<br>
Cheers, Simon
<br>
<br>
On 27/06/12 14:24, Simon Loewenthal wrote:
<br>
<blockquote type="cite">Hi Simon,
<br>
<br>
I rebooted both servers : /# reboot/
<br>
You've given a good reason to move to 2.8.n
<br>
<br>
> Are you definitely not reclustering at any stage?
<br>
Apologies, but I don't understand the term reclustering.
<br>
<br>
S.
<br>
<br>
<br>
<br>
On 27/06/12 15:20, Simon MacMullen wrote:
<br>
<blockquote type="cite">Hi.
<br>
<br>
You say you "reboot the server" - is this node 1, node 2, or
both?
<br>
<br>
The description you have after rebooting the server is
consistent with
<br>
having one RAM node and one disc node and restarting both of
them - in
<br>
2.7.0 if the RAM node came back up first it would create a
blank
<br>
database. This was fixed in 2.8.x, in that now a RAM node will
refuse
<br>
to start if there are no disc nodes to connect to.
<br>
<br>
However, when you initially create the cluster you are
creating both
<br>
nodes as disc nodes. So I am puzzled as to how you could have
got to
<br>
the state where one node was a RAM node. Are you definitely
not
<br>
reclustering at any stage?
<br>
<br>
Cheers, Simon
<br>
<br>
On 27/06/12 12:48, S.Loewenthal wrote:
<br>
<blockquote type="cite">Hi there,
<br>
<br>
I installed RabbitMQ server but cannot get one node to
retain the
<br>
cluster configuration. Step-by-step account follows for what
I did to
<br>
configure these nodes.
<br>
Node 1: rabbit@iuu-7
<br>
Nide 2: rabbit@iuu-8
<br>
<br>
<br>
On both nodes install 2.7.0 - This version as all other
environment run
<br>
same version.
<br>
# rpm -ivh rabbitmq-server-2.7.0-1.noarch.rpm
<br>
<br>
Start Node 2 (if not already running)
<br>
# /etc/init.d/rabbitmq-server start
<br>
<br>
Shutdown RabbitMQ on Node 2
<br>
# /etc/init.d/rabbitmq-server stop
<br>
<br>
Copied the Erlang cookie so that both nodes have the same
cookie, or
<br>
else these won't talk with each other
<br>
Copy (Node 1) iuu-7:/var/lib/rabbitmq/.erlang.cookie to
(Node 2)
<br>
iuu-8:/var/lib/rabbitmq/.erlang.cookie
<br>
permissions and ownership are : Perms 400 -- Owner
rabbitmq:rabbitmq
<br>
<br>
Start RabbitMQ on Node 2
<br>
# /etc/init.d/rabbitmq-server start
<br>
<br>
Verify that each node can communicate with each other:
<br>
On Node 1
<br>
$ rabbitmqctl -n rabbit@iuu-8 status
<br>
On Node 2
<br>
$ rabbitmqctl -n rabbit@iuu-7 status
<br>
<br>
Reset Node 2 so that it is ready to join the cluster on Node
1
<br>
$ rabbitmqctl stop_app
<br>
$ rabbitmqctl reset
<br>
<br>
Add the Node 2 to the first node with disc writing enabled
on both
<br>
nodes:
<br>
$ rabbitmqctl cluster rabbit@iuu-7 rabbit@iuu-8
<br>
<br>
Start the app on Node 2
<br>
$ rabbitmqctl start_app
<br>
<br>
Verify the cluster status on Node 2 and the same on Node 1
<br>
$ rabbitmqctl cluster_status
<br>
Cluster status of node 'rabbit@iuu-8' ...
<br>
[{nodes,[{disc,['rabbit@iuu-8','rabbit@iuu-7']}]},
<br>
{running_nodes,['rabbit@iuu-7','rabbit@iuu-8']}]
<br>
...done.
<br>
<br>
next I add a few users, and reboot the server. Now the
cluster is
<br>
disconnection, and I cannot get ot to connnect. Also, the
users added
<br>
afore the reboot no longer exist.
<br>
<br>
It comes up without the cluster information nor the users:
<br>
[root@iuu-7 ~]# rabbitmqctl cluster_status
<br>
Cluster status of node 'rabbit@iup-7' ...
<br>
[{nodes,[{ram,['rabbit@iuu-7']}]},{running_nodes,['rabbit@iuu-7']}]
<br>
...done.
<br>
<br>
[root@iup-8 ~]# rabbitmqctl cluster_status
<br>
Cluster status of node 'rabbit@iup-' ...
<br>
[{nodes,[{disc,['rabbit@iup-8']},{ram,['rabbit@iup-7']}]},
<br>
{running_nodes,['rabbit@iup-8']}]
<br>
...done.
<br>
<br>
The cluster configuration does not survive a server restart
and in this
<br>
case user account was was lost. I imagine that I have
misconfigured
<br>
something.
<br>
<br>
** The question **
<br>
How can I ensure that the cluster reconnects after
rabbitmq-server
<br>
restarts, and that data that was written is retained? Or,
what did I
<br>
misconfigure
<br>
<br>
<br>
<br>
Many thanks, S.
<br>
<br>
<br>
_______________________________________________
<br>
rabbitmq-discuss mailing list
<br>
<a class="moz-txt-link-abbreviated" href="mailto:rabbitmq-discuss@lists.rabbitmq.com">rabbitmq-discuss@lists.rabbitmq.com</a>
<br>
<a class="moz-txt-link-freetext" href="https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss">https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</a>
<br>
</blockquote>
<br>
<br>
</blockquote>
<br>
<br>
</blockquote>
<br>
<br>
</blockquote>
<br>
<br>
<pre class="moz-signature" cols="72">--
PGP is optional: 4BA78604
simon @ klunky . org
simon @ klunky . co.uk
I won't accept your confidentiality
agreement, and your Emails are kept.
~Ö¿Ö~
</pre>
</body>
</html>