How to use AWS auto discovery plugin to form cluster

[Sam Sen]

I have two nodes in ASG. I installed the latest 3.6.x version of RabbitMQ along with the latest version of rabbitmq-autoscaler. 

Here's my config file /etc/rabbitmq/rabbitmq.config

{autocluster, [
          {autocluster_log_level, debug},
          {backend, aws},
          {aws_autoscaling, true},
          {aws_ec2_region, "us-east-1"},
          {aws_access_key, "XYZXYZXYZ"},
          {aws_secret_key, "XYZXYYZ"}
      ]}

Each no starts up in standalone mode. I see this in the log file:

=ERROR REPORT==== 7-Nov-2017::16:07:19 ===
autocluster: Skipping step release_startup_lock because backend module is not configured!

[Michael Klishin]

I assume you mean rabbitmq-autocluster.

The config snippet looks OK but the plugin logs that it cannot determine what backend to use.

http://www.rabbitmq.com/configure.html documents how to verify your configuration.

Chances are the autocluster section is incorrectly nested or similar.

There are examples that use and configure this plugin available in https://github.com/rabbitmq/rabbitmq-autocluster/tree/stable/examples.

--
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-users+unsubscribe@googlegroups.com.
To post to this group, send email to rabbitmq-users@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

MK

Staff Software Engineer, Pivotal/RabbitMQ

[Sam Sen]

Turns out it was a security group issue.

On Thursday, November 9, 2017 at 5:37:01 AM UTC-5, Michael Klishin wrote:

I assume you mean rabbitmq-autocluster.

The config snippet looks OK but the plugin logs that it cannot determine what backend to use.

http://www.rabbitmq.com/configure.html documents how to verify your configuration.

Chances are the autocluster section is incorrectly nested or similar.

There are examples that use and configure this plugin available in https://github.com/rabbitmq/rabbitmq-autocluster/tree/stable/examples.

On Wed, Nov 8, 2017 at 12:12 AM, Sam Sen <samna...@gmail.com> wrote:

I have two nodes in ASG. I installed the latest 3.6.x version of RabbitMQ along with the latest version of rabbitmq-autoscaler. 

Here's my config file /etc/rabbitmq/rabbitmq.config

{autocluster, [
          {autocluster_log_level, debug},
          {backend, aws},
          {aws_autoscaling, true},
          {aws_ec2_region, "us-east-1"},
          {aws_access_key, "XYZXYZXYZ"},
          {aws_secret_key, "XYZXYYZ"}
      ]}

Each no starts up in standalone mode. I see this in the log file:

=ERROR REPORT==== 7-Nov-2017::16:07:19 ===
autocluster: Skipping step release_startup_lock because backend module is not configured!

--
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.