Remove Nodes from RabbitMQ Management Portal

[SallySue]

Hello.  Was able to remove one node of the 3 nodes in a cluster and it was removed from the Management portal.  I've tried the forget_cluster_node command for the other 2, isn't working, says the node isn't part of the cluster, tried a reinstall and a rename, that didn't work.

Is there a registry entry or another way to remove the node from the portal?

Thanks

[Michael Klishin]

How exactly do you remove the other nodes and what is the error message?

Nodes reporting they are not cluster members certainly means something isn't right.

You can completely wipe management database (it's in memory only and is not meant for long term stats

collection by design), see at the bottom of http://www.rabbitmq.com/management.html.

However, if you see the nodes still being cluster members after that, it means at least some nodes

consider them to be such.

[SallySue]

Thank you for the tip, trying to use the command to restart, "rabbitmqctl eval 'supervisor2:terminate_child(rabbit_mgmt_sup_sup, rabbit_mgmt_sup), rabbit_mgmt_sup_sup:start_child().'", however; seems either the syntax needs to be populated with other values or something else is wrong.

It errors "INFO: Could not find files for the given pattern(s).

******************************

ERLANG_HOME not set correctly.

******************************

Please either set ERLANG_HOME to point to your Erlang installation or place the

RabbitMQ server distribution in the Erlang lib folder.

Thoughts?  We are running 2 clusters on a node, I am trying to get rid of the original cluster (which would be the third).

Thanks.

[Michael Klishin]

rabbitmqctl and other RabbitMQ tools need ERLANG_HOME to be set because they run on the Erlang VM.

In other words, they don't even run and abort very early, so it's expected that they don't have any effect.

On Tue, Jun 7, 2016 at 6:36 PM, Nordeng, Jennifer <jennifer...@pearson.com> wrote:

Thank you for the tip, trying to use the command to restart, "rabbitmqctl eval 'supervisor2:terminate_child(rabbit_mgmt_sup_sup, rabbit_mgmt_sup), rabbit_mgmt_sup_sup:start_child().'", however; seems either the syntax needs to be populated with other values or something else is wrong.

It errors "INFO: Could not find files for the given pattern(s).

******************************

ERLANG_HOME not set correctly.

******************************

Please either set ERLANG_HOME to point to your Erlang installation or place the

RabbitMQ server distribution in the Erlang lib folder.

Thoughts?  We are running 2 clusters on a node, I am trying to get rid of the original cluster (which would be the third).

Thanks.

--
You received this message because you are subscribed to a topic in the Google Groups "rabbitmq-users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/rabbitmq-users/9PGIa6uyHAo/unsubscribe.
To unsubscribe from this group and all its topics, send an email to rabbitmq-user...@googlegroups.com.
To post to this group, send email to rabbitm...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Jennifer Nordeng

Systems Analyst, Advanced Technical Solutions

Pearson VUE

5601 Green Valley Drive, Bloomington, MN 55437

+1 952 681 3625

Learn more at pearson.com

--
You received this message because you are subscribed to the Google Groups "rabbitmq-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rabbitmq-user...@googlegroups.com.
To post to this group, send email to rabbitm...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

MK

Staff Software Engineer, Pivotal/RabbitMQ

[SallySue]

Hello.  I've made sure that ERLANG_HOME is set, however; this is not working.

It comes back with something like "Error: operation eval used with invalid parameter: ["'supervisor2:terminate_child(rabbit_mgmt_sup_sup,","rabbit_mgmt_sup),","rabbit_mgmt_sup_sup:start_child()"]

We are running version 3.61 of RabbitMQ and version 7.3 of Erlang.  We are also running this on Windows Server 2012.

At this point, think we're just having issues with the syntax to remove these nodes from displaying in the RabbitMQ Console.

Any further thoughts?

Thanks

On Tuesday, June 7, 2016 at 4:03:34 PM UTC-5, Michael Klishin wrote:

rabbitmqctl and other RabbitMQ tools need ERLANG_HOME to be set because they run on the Erlang VM.

In other words, they don't even run and abort very early, so it's expected that they don't have any effect.

On Tue, Jun 7, 2016 at 6:36 PM, 

Thank you for the tip, trying to use the command to restart, "rabbitmqctl eval 'supervisor2:terminate_child(rabbit_mgmt_sup_sup, rabbit_mgmt_sup), rabbit_mgmt_sup_sup:start_child().'", however; seems either the syntax needs to be populated with other values or something else is wrong.

It errors "INFO: Could not find files for the given pattern(s).

******************************

ERLANG_HOME not set correctly.

******************************

Please either set ERLANG_HOME to point to your Erlang installation or place the

RabbitMQ server distribution in the Erlang lib folder.

Thoughts?  We are running 2 clusters on a node, I am trying to get rid of the original cluster (which would be the third).

Thanks.

On Mon, Jun 6, 2016 at 7:02 PM, Michael Klishin <mkli...@pivotal.io> wrote:

How exactly do you remove the other nodes and what is the error message?

Nodes reporting they are not cluster members certainly means something isn't right.

You can completely wipe management database (it's in memory only and is not meant for long term stats

collection by design), see at the bottom of http://www.rabbitmq.com/management.html.

However, if you see the nodes still being cluster members after that, it means at least some nodes

consider them to be such.

On Tuesday, June 7, 2016 at 12:13:40 AM UTC+3, SallySue wrote:

Hello.  Was able to remove one node of the 3 nodes in a cluster and it was removed from the Management portal.  I've tried the forget_cluster_node command for the other 2, isn't working, says the node isn't part of the cluster, tried a reinstall and a rename, that didn't work.

Is there a registry entry or another way to remove the node from the portal?

Thanks

-- 

[Michael Klishin]

Can you please post the exact command you run and the exact error you are getting?

You seem to be providing 3 different lines to `rabbitmqctl eval` while it should be a single parameter, e.g.

rabbitmqctl eval 'supervisor2:terminate_child(rabbit_mgmt_sup_sup, rabbit_mgmt_sup), rabbit_mgmt_sup_sup:start_child().'

uses a single argument enclosed in single quotes. It could be a Windows-specific quoting issue, too. You can use

double quotes instead of single quotes.

--

You received this message because you are subscribed to the Google Groups "rabbitmq-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rabbitmq-user...@googlegroups.com.
To post to this group, send email to rabbitm...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[SallySue]

Thanks, that was part of my question, if this is 3 different commands, what is the actual syntax?

Tried for example, the first section, 

rabbitmqctl -n CLU...@server.dn.local -q stop rabbitmq_management

Response:  

DIAGNOSTICS

===========

attempted to contact: ['CLU...@server.dn.local']

CLU...@server.dn.local:

  * connected to epmd (port 4369) on server.dn.local

  * epmd reports: node 'CLUSTER' not running at all

                  other nodes on server.dn.local: ['CLUSTER2']

  * suggestion: start the node

current node details:

- node name: 'rabbitm...@server.dn.local'

- home dir: C:\Users\user

- cookie hash: alphanumericacharacters==

d:\RabbitData>rabbitmqctl -n CLU...@server.dn.local -q start rabbitmq_manage

ment

Error: could not recognize command

Usage:

rabbitmqctl [-n <node>] [-t <timeout>] [-q] <command> [<command options>]

Options:

    -n node

    -q

    -t timeout

The issue here is I believe that the original RabbitMQ Windows Service instance was already removed, the RabbitMQ Databases were removed.  Tried to recreate the node but that wasn't working as it was changing the casing.  Other thoughts to remove these two bad Clusters (that don't exist) from the RabbitmQ Console?

Other Clusters are running happily and displaying green in the management console.

Thank you for your input thus far and hopefully we can figure this out.

Thanks.

[Michael Klishin]

See below. You either want to use CLUSTER2 or start node named CLUSTER.

http://rabbitmq.com/management lists the exact command that needs to be executed except for the -nodeps flag because it is environment-specific.

[Michael Klishin]

It is not 3 different commands, it is a single command that passes 3 statements to be executed. They are passed as a single string argument.

On 10 jun 2016, at 23:27, SallySue <jennifer...@pearson.com> wrote: