RabbitMQ - AWS Discovery

David Shaw

unread,

Jun 27, 2018, 6:12:56 AM6/27/18

to rabbitmq-users

Hi all,

Sorry to be back asking more questions but this is starting to drive me crazy. Said inherited installation from my previous post seems to have quite a few issues. It was relying on puppet to change the rabbit.config when servers autoscaled, the result being that:

Original Server 1 & Original Server 2 = Happy cluster

Original Server 1 - Original Server 2 & New Autoscaled Server 1 = Happy cluster

Original Server 1 - New Autoscaled Server 1 & New Autoscaled Server 2 = Happy cluster

However:

New Autoscaled Server 3 & New Autoscaled Server 2 = Cluster broken

I researched and put this down to name changes leaving the cluster unreliable. I also didn't like that the cluster relied on puppet to tell it when a new server was in service.

So, I am now armed with a few different documents and given the rabbitmq.conf has changed format, I'm also thoroughly confused or doing something wrong.

My rabbitmq.conf currently looks like this, I've tried adding debug logging twice but with no success. Version is 3.7.6

% This file managed by Puppet
% Template Path: rabbitmq/templates/rabbitmq.config
[
  {rabbit, [
    {log_levels, [{connection, debug}, {autocluster, debug}, {autocluster_log_level, debug}]},
    {default_user, <<"rmq">>},
    {default_pass, <<"rmq">>}
  ]},
  {kernel, [
  ]},


  {autocluster, [
    {autocluster_log_level, debug},
    {backend, aws},
    {aws_autoscaling, true},
    {aws_ec2_region, "us-west-1"}
  ]},


  {rabbitmq_management, [
    {listener, [
      {port, 15672}
    ]}
  ]}
].
% EOF

The logs simply state:

2018-06-27 11:33:58.748 [info] <0.33.0> Application rabbitmq_shovel_management started on node rabbit@007

2018-06-27 11:33:58.795 [notice] <0.93.0> Changed loghwm of /var/log/rabbitmq/rab...@007.log to 50

2018-06-27 11:33:58.975 [info] <0.5.0> Server startup complete; 8 plugins started.

* rabbitmq_shovel_management

* rabbitmq_management

* rabbitmq_management_agent

* rabbitmq_shovel

* rabbitmq_amqp1_0

* rabbitmq_peer_discovery_aws

* rabbitmq_web_dispatch

* rabbitmq_peer_discovery_common

I've tried the new format for the config file but alas, the server won't start at all. Be gentle, it's only my second week on MQ and it's been setup for olde physical hardware.

Thanks
Dave

Michael Klishin

unread,

Jun 27, 2018, 6:45:52 AM6/27/18

to rabbitm...@googlegroups.com

David,

We do not guess on this list. If a node "won't start at all", please post full error messages and logs or we won't be able to help you.

There is a separate section dedicated to peer discovery debugging [1]. There really isn't much to it: 99% of questions come down to

either misunderstanding of when it is or isn't performed or fairly trivial misconfiguration.

We cannot know which is which here since you posted no logs. Please help other help you, guessing is too expensive and our tiny

team cannot afford it.

1. http://www.rabbitmq.com/cluster-formation.html#troubleshooting-cluster-formation

2018-06-27 11:33:58.795 [notice] <0.93.0> Changed loghwm of /var/log/rabbitmq/rabbit@007.log to 50

2018-06-27 11:33:58.975 [info] <0.5.0> Server startup complete; 8 plugins started.
* rabbitmq_shovel_management
* rabbitmq_management
* rabbitmq_management_agent
* rabbitmq_shovel
* rabbitmq_amqp1_0
* rabbitmq_peer_discovery_aws
* rabbitmq_web_dispatch
* rabbitmq_peer_discovery_common

I've tried the new format for the config file but alas, the server won't start at all. Be gentle, it's only my second week on MQ and it's been setup for olde physical hardware.
Thanks
Dave

The information contained in this e-mail communication is solely intended for the person/legal person to whom it has been sent, and as it may contain information of a personal or confidential nature, it may not be made public by virtue of law, regulations or agreement. If someone other than the intended recipient should receive or come into possession of this e-mail communication, he/she will not be entitled to read, disseminate, disclose or duplicate it. If you are not the intended recipient, you are requested to inform the sender of this e-mail message of this immediately, and to destroy the original e-mail communication. Neither Randstad Holding nv nor its subsidiaries accept any liability for incorrect and incomplete transmission or delayed receipt of this e-mail.

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

David Shaw

unread,

Jun 27, 2018, 6:54:16 AM6/27/18

to rabbitm...@googlegroups.com

Sorry Michael, the node starts with the config posted above and the management console is accessible.

It won't start at all if I try updating to the new config format.

My main issue is that we're getting no logging about aws at all, it is almost like that block of code for autocluster is being completely ignored. The log stops after this line:

2018-06-27 11:33:58.975 [info] <0.5.0> Server startup complete; 8 plugins started.

* rabbitmq_shovel_management

* rabbitmq_management

* rabbitmq_management_agent

* rabbitmq_shovel

* rabbitmq_amqp1_0

* rabbitmq_peer_discovery_aws

* rabbitmq_web_dispatch

* rabbitmq_peer_discovery_common

Changing the values to debug, trace etc has no effect. Yet the log is clearly looking at the correct .conf file.

Thanks

Dave

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

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

--

Met vriendelijke groet,

David Shaw

Senior ICT consultant

Randstad Groep Nederland

Diemermere 15, 1112 TB Diemen

P.O. Box 12600, NL-1100 AP Amsterdam

david...@randstadgroep.nl

www.randstadgroep.nl

Michael Klishin

unread,

Jun 27, 2018, 7:04:46 AM6/27/18

to rabbitm...@googlegroups.com

We asked for the log file. Can you please post it (at least everything logged on the last boot, from the version header all the way to the last line). Please help others help you.

Are you aware of the section in the Cluster Formation guide that explains when peer discovery is *not* performed? Nodes that already have an initialised data directory will NOT perform peer discovery since they consider themselves to be a cluster [of 1] member.

Has effective configuration been verified? [1]. Can the config be posted (please edit out credentials, domain names and IP addresses)?

1. http://www.rabbitmq.com/configure.html#verify-configuration-config-file-location

To unsubscribe from this group and stop receiving emails from it, send an email to rabbitmq-user...@googlegroups.com.

David Shaw

unread,

Jun 27, 2018, 7:21:31 AM6/27/18

to rabbitmq-users

I don't know where that reply went:

Here is the complete log, I have cleared the mnesia directory and we can see the cluster wants to try to discover other nodes:

Of course, here is the full log:

2018-06-27 13:15:41.719 [info] <0.33.0> Application lager started on node rabbit@myserver1
2018-06-27 13:15:41.723 [info] <0.5.0> Log file opened with Lager
2018-06-27 13:15:42.247 [info] <0.33.0> Application mnesia started on node rabbit@myserver1
2018-06-27 13:15:42.247 [info] <0.33.0> Application recon started on node rabbit@myserver1
2018-06-27 13:15:42.247 [info] <0.33.0> Application jsx started on node rabbit@myserver1
2018-06-27 13:15:42.252 [info] <0.33.0> Application os_mon started on node rabbit@myserver1
2018-06-27 13:15:42.310 [info] <0.33.0> Application inets started on node rabbit@myserver1
2018-06-27 13:15:42.310 [info] <0.33.0> Application crypto started on node rabbit@myserver1
2018-06-27 13:15:42.310 [info] <0.33.0> Application cowlib started on node rabbit@myserver1
2018-06-27 13:15:42.310 [info] <0.33.0> Application asn1 started on node rabbit@myserver1
2018-06-27 13:15:42.310 [info] <0.33.0> Application public_key started on node rabbit@myserver1
2018-06-27 13:15:42.365 [info] <0.33.0> Application ssl started on node rabbit@myserver1
2018-06-27 13:15:42.370 [info] <0.33.0> Application ranch started on node rabbit@myserver1
2018-06-27 13:15:42.370 [info] <0.33.0> Application ranch_proxy_protocol started on node rabbit@myserver1
2018-06-27 13:15:42.372 [info] <0.33.0> Application cowboy started on node rabbit@myserver1
2018-06-27 13:15:42.372 [info] <0.33.0> Application xmerl started on node rabbit@myserver1
2018-06-27 13:15:42.374 [info] <0.33.0> Application rabbitmq_aws started on node rabbit@myserver1
2018-06-27 13:15:42.374 [info] <0.33.0> Application rabbit_common started on node rabbit@myserver1
2018-06-27 13:15:42.381 [info] <0.33.0> Application amqp_client started on node rabbit@myserver1
2018-06-27 13:15:42.389 [info] <0.204.0>
 Starting RabbitMQ 3.7.6 on Erlang 20.3.8
 Copyright (C) 2007-2018 Pivotal Software, Inc.
 Licensed under the MPL.  See http://www.rabbitmq.com/
2018-06-27 13:15:42.408 [info] <0.204.0>
 node           : rabbit@myserver1
 home dir       : /home/rabbitmq
 config file(s) : /etc/rabbitmq/rabbitmq.config
 cookie hash    : CnebT2n4P0I5SHL3VZtImw==
 log(s)         : /var/log/rabbitmq/rabbit@myserver1.log
                : /var/log/rabbitmq/rabbit@myserver1_upgrade.log
 database dir   : /var/lib/rabbitmq/mnesia/rabbit@myserver1
2018-06-27 13:15:44.449 [info] <0.212.0> Memory high watermark set to 1515 MiB (1589416755 bytes) of 3789 MiB (3973541888 bytes) total
2018-06-27 13:15:44.453 [info] <0.214.0> Enabling free disk space monitoring
2018-06-27 13:15:44.453 [info] <0.214.0> Disk free limit set to 50MB
2018-06-27 13:15:44.457 [info] <0.216.0> Limiting to approx 16284 file handles (14653 sockets)
2018-06-27 13:15:44.457 [info] <0.217.0> FHC read buffering:  OFF
2018-06-27 13:15:44.457 [info] <0.217.0> FHC write buffering: ON
2018-06-27 13:15:44.458 [info] <0.204.0> Node database directory at /var/lib/rabbitmq/mnesia/rabbit@myserver1 is empty. Assuming we need to join an existing cluster or initialise from scratch...
2018-06-27 13:15:44.458 [info] <0.204.0> Configured peer discovery backend: rabbit_peer_discovery_classic_config
2018-06-27 13:15:44.458 [info] <0.204.0> Will try to lock with peer discovery backend rabbit_peer_discovery_classic_config
2018-06-27 13:15:44.458 [info] <0.204.0> Peer discovery backend does not support locking, falling back to randomized delay
2018-06-27 13:15:44.458 [info] <0.204.0> Peer discovery backend rabbit_peer_discovery_classic_config does not support registration, skipping randomized startup delay.
2018-06-27 13:15:44.458 [info] <0.204.0> All discovered existing cluster peers:
2018-06-27 13:15:44.458 [info] <0.204.0> Discovered no peer nodes to cluster with
2018-06-27 13:15:44.460 [info] <0.33.0> Application mnesia exited with reason: stopped
2018-06-27 13:15:44.475 [info] <0.33.0> Application mnesia started on node rabbit@myserver1
2018-06-27 13:15:44.536 [info] <0.204.0> Waiting for Mnesia tables for 30000 ms, 9 retries left
2018-06-27 13:15:44.569 [info] <0.204.0> Waiting for Mnesia tables for 30000 ms, 9 retries left
2018-06-27 13:15:44.604 [info] <0.204.0> Waiting for Mnesia tables for 30000 ms, 9 retries left
2018-06-27 13:15:44.604 [info] <0.204.0> Peer discovery backend rabbit_peer_discovery_classic_config does not support registration, skipping registration.
2018-06-27 13:15:44.605 [info] <0.204.0> Priority queues enabled, real BQ is rabbit_variable_queue
2018-06-27 13:15:44.608 [info] <0.383.0> Starting rabbit_node_monitor
2018-06-27 13:15:44.638 [info] <0.204.0> message_store upgrades: 1 to apply
2018-06-27 13:15:44.638 [info] <0.204.0> message_store upgrades: Applying rabbit_variable_queue:move_messages_to_vhost_store
2018-06-27 13:15:44.638 [info] <0.204.0> message_store upgrades: No durable queues found. Skipping message store migration
2018-06-27 13:15:44.638 [info] <0.204.0> message_store upgrades: Removing the old message store data
2018-06-27 13:15:44.639 [info] <0.204.0> message_store upgrades: All upgrades applied successfully
2018-06-27 13:15:44.671 [info] <0.204.0> Management plugin: using rates mode 'basic'
2018-06-27 13:15:44.672 [info] <0.204.0> Adding vhost '/'
2018-06-27 13:15:44.684 [info] <0.423.0> Making sure data directory '/var/lib/rabbitmq/mnesia/rabbit@myserver1/msg_stores/vhosts/628WB79CIFDYO9LJI6DKMI09L' for vhost '/' exists
2018-06-27 13:15:44.688 [info] <0.423.0> Starting message stores for vhost '/'
2018-06-27 13:15:44.688 [info] <0.427.0> Message store "628WB79CIFDYO9LJI6DKMI09L/msg_store_transient": using rabbit_msg_store_ets_index to provide index
2018-06-27 13:15:44.689 [info] <0.423.0> Started message store of type transient for vhost '/'
2018-06-27 13:15:44.690 [info] <0.430.0> Message store "628WB79CIFDYO9LJI6DKMI09L/msg_store_persistent": using rabbit_msg_store_ets_index to provide index
2018-06-27 13:15:44.690 [warning] <0.430.0> Message store "628WB79CIFDYO9LJI6DKMI09L/msg_store_persistent": rebuilding indices from scratch
2018-06-27 13:15:44.691 [info] <0.423.0> Started message store of type persistent for vhost '/'
2018-06-27 13:15:44.692 [info] <0.204.0> Creating user 'rmqadmin'
2018-06-27 13:15:44.694 [info] <0.204.0> Setting user tags for user 'rmqadmin' to [administrator]
2018-06-27 13:15:44.695 [info] <0.204.0> Setting permissions for 'rmqadmin' in '/' to '.*', '.*', '.*'
2018-06-27 13:15:44.698 [info] <0.468.0> started TCP Listener on [::]:5672
2018-06-27 13:15:44.701 [info] <0.204.0> Setting up a table for connection tracking on this node: tracked_connection_on_node_rabbit@myserver1
2018-06-27 13:15:44.704 [info] <0.204.0> Setting up a table for per-vhost connection counting on this node: tracked_connection_per_vhost_on_node_rabbit@myserver1
2018-06-27 13:15:44.704 [info] <0.33.0> Application rabbit started on node rabbit@myserver1
2018-06-27 13:15:44.704 [info] <0.482.0> Peer discovery: node cleanup is disabled
2018-06-27 13:15:44.704 [info] <0.33.0> Application rabbitmq_peer_discovery_common started on node rabbit@myserver1
2018-06-27 13:15:44.704 [info] <0.33.0> Application rabbitmq_peer_discovery_aws started on node rabbit@myserver1
2018-06-27 13:15:44.704 [info] <0.33.0> Application rabbitmq_web_dispatch started on node rabbit@myserver1
2018-06-27 13:15:44.704 [info] <0.33.0> Application amqp10_common started on node rabbit@myserver1
2018-06-27 13:15:44.704 [info] <0.33.0> Application amqp10_client started on node rabbit@myserver1
2018-06-27 13:15:44.705 [info] <0.33.0> Application rabbitmq_shovel started on node rabbit@myserver1
2018-06-27 13:15:44.705 [info] <0.33.0> Application rabbitmq_amqp1_0 started on node rabbit@myserver1
2018-06-27 13:15:44.708 [info] <0.33.0> Application rabbitmq_management_agent started on node rabbit@myserver1
2018-06-27 13:15:44.751 [info] <0.546.0> Management plugin started. Port: 15672
2018-06-27 13:15:44.752 [info] <0.652.0> Statistics database started.
2018-06-27 13:15:44.752 [info] <0.33.0> Application rabbitmq_management started on node rabbit@myserver1
2018-06-27 13:15:44.752 [info] <0.33.0> Application rabbitmq_shovel_management started on node rabbit@myserver1
2018-06-27 13:15:44.802 [notice] <0.93.0> Changed loghwm of /var/log/rabbitmq/rabbit@myserver1.log to 50
2018-06-27 13:15:44.976 [info] <0.5.0> Server startup complete; 8 plugins started.


 * rabbitmq_shovel_management
 * rabbitmq_management
 *

 rabbitmq_management_agent
 * rabbitmq_amqp1_0
 * rabbitmq_shovel
 * rabbitmq_web_dispatch
 * rabbitmq_peer_discovery_aws
 * rabbitmq_peer_discovery_common

Thanks

Op woensdag 27 juni 2018 13:04:46 UTC+2 schreef Michael Klishin:

2018-06-27 11:33:58.795 [notice] <0.93.0> Changed loghwm of /var/log/rab...@007.log to 50

2018-06-27 11:33:58.975 [info] <0.5.0> Server startup complete; 8 plugins started.
* rabbitmq_shovel_management
* rabbitmq_management
* rabbitmq_management_agent
* rabbitmq_shovel
* rabbitmq_amqp1_0
* rabbitmq_peer_discovery_aws
* rabbitmq_web_dispatch
* rabbitmq_peer_discovery_common

I've tried the new format for the config file but alas, the server won't start at all. Be gentle, it's only my second week on MQ and it's been setup for olde physical hardware.
Thanks
Dave

The information contained in this e-mail communication is solely intended for the person/legal person to whom it has been sent, and as it may contain information of a personal or confidential nature, it may not be made public by virtue of law, regulations or agreement. If someone other than the intended recipient should receive or come into possession of this e-mail communication, he/she will not be entitled to read, disseminate, disclose or duplicate it. If you are not the intended recipient, you are requested to inform the sender of this e-mail message of this immediately, and to destroy the original e-mail communication. Neither Randstad Holding nv nor its subsidiaries accept any liability for incorrect and incomplete transmission or delayed receipt of this e-mail.

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

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

--

Met vriendelijke groet,

David Shaw

Senior ICT consultant

Randstad Groep Nederland

Diemermere 15, 1112 TB Diemen

P.O. Box 12600, NL-1100 AP Amsterdam

david...@randstadgroep.nl

www.randstadgroep.nl

Michael Klishin

unread,

Jun 27, 2018, 7:24:17 AM6/27/18

to David Shaw, rabbitm...@googlegroups.com

Please CC the list, I do not provide 1-on-1 support of any kind.

> 2018-06-27 13:15:44.604 [info] <0.204.0> Peer discovery backend rabbit_peer_discovery_classic_config does not support registration, skipping registration.

> 2018-06-27 13:15:44.458 [info] <0.204.0> All discovered existing cluster peers:
> 2018-06-27 13:15:44.458 [info] <0.204.0> Discovered no peer nodes to cluster with

suggests the node tried to use the default peer discovery mechanism [1] and not the AWS one.

Now let's see what's in /etc/rabbitmq/rabbitmq.config.

1. http://www.rabbitmq.com/cluster-formation.html#peer-discovery-classic-config

2018-06-27 13:15:44.802 [notice] <0.93.0> Changed loghwm of /var/log/rabbitmq/rabbit@myserver1.log to 50 2018-06-27 13:15:44.976 [info] <0.5.0> Server startup complete; 8 plugins started.

* rabbitmq_shovel_management * rabbitmq_management *

rabbitmq_management_agent * rabbitmq_amqp1_0 * rabbitmq_shovel * rabbitmq_web_dispatch * rabbitmq_peer_discovery_aws * rabbitmq_peer_discovery_common

I've cleared the mnesia tables and we can see in the log it assumes it needs to form a new cluster but this is where the log stops.

Thanks

Dave

The information contained in this e-mail communication is solely intended for the person/legal person to whom it has been sent, and as it may contain information of a personal or confidential nature, it may not be made public by virtue of law, regulations or agreement. If someone other than the intended recipient should receive or come into possession of this e-mail communication, he/she will not be entitled to read, disseminate, disclose or duplicate it. If you are not the intended recipient, you are requested to inform the sender of this e-mail message of this immediately, and to destroy the original e-mail communication. Neither Randstad Holding nv nor its subsidiaries accept any liability for incorrect and incomplete transmission or delayed receipt of this e-mail.

--

Michael Klishin

unread,

Jun 27, 2018, 7:24:51 AM6/27/18

to rabbitm...@googlegroups.com

> 2018-06-27 13:15:44.604 [info] <0.204.0> Peer discovery backend rabbit_peer_discovery_classic_config does not support registration, skipping registration.

> 2018-06-27 13:15:44.458 [info] <0.204.0> All discovered existing cluster peers:
> 2018-06-27 13:15:44.458 [info] <0.204.0> Discovered no peer nodes to cluster with

suggests the node tried to use the default peer discovery mechanism [1] and not the AWS one.

Now let's see what's in /etc/rabbitmq/rabbitmq.config.

1. http://www.rabbitmq.com/cluster-formation.html#peer-discovery-classic-config

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.

David Shaw

unread,

Jun 28, 2018, 8:26:48 AM6/28/18

to rabbitmq-users

Thanks again for the quick reply. After more digging I eventually got this working with the aws backend, the cluster code needed to be moved up an array.

Final and working rabbit.conf looks like this:

[
  {rabbit, [
    {cluster_nodes, {[], disc}},
    {cluster_partition_handling, ignore},
    {tcp_listen_options, [
         {keepalive,     true},
         {backlog,       128},
         {nodelay,       true},
         {linger,        {true, 0}},
         {exit_on_close, false}
    ]},
    {autocluster, [{backend, aws}, {aws_autoscaling, true}]},
    {cluster_formation, [
      {peer_discovery_backend,rabbit_peer_discovery_aws},
      {peer_discovery_aws, [
        {aws_ec2_region,"us-west-1"},
        {aws_use_private_ip,true},
        {aws_autoscaling,true}]}
      ]},
  {kernel, [




  ]}
,
  {rabbitmq_management, [
    {listener, [
      {port, 15672}
    ]}
  ]}
].

Interestingly I've enabled the cluster cleanup in rabbitmq-env.conf but it doesn't appear to work, server start log says disabled and then enabled:

2018-06-28 14:14:08.147 [info] <0.474.0> Peer discovery: node cleanup is disabled
2018-06-28 14:14:08.147 [debug] <0.467.0> Supervisor rabbit_web_dispatch_sup started gen_event:start_link({local,webmachine_log_event}) at pid <0.469.0>
2018-06-28 14:14:08.147 [info] <0.33.0> Application rabbitmq_web_dispatch started on node 'rab...@172.25.229.33'
2018-06-28 14:14:08.147 [info] <0.386.0> rabbit on node 'rab...@172.25.230.22' up
2018-06-28 14:14:08.147 [debug] <0.473.0> Supervisor rabbit_peer_discovery_common_sup started rabbit_peer_discovery_cleanup:start_link() at pid <0.474.0>

Terminated servers stay in the list, rabbitmq-env.conf looks like this:

AUTOCLUSTER_CLEANUP=true
CLEANUP_WARN_ONLY=false
LC_ALL=en_US.UTF-8
NODE_PORT=5672
RABBITMQ_NODENAME=rabbit@<ip>
RABBITMQ_USE_LONGNAME=true
export ERL_INETRC=/etc/rabbitmq/inetrc

Any suggestions? I'll document this and put up a nice end to end blog for anyone using the puppet module as I've found bits of both everywhere, so I think it'd prove useful to someone.

Thanks

Op woensdag 27 juni 2018 13:24:51 UTC+2 schreef Michael Klishin:

Michael Klishin

unread,

Jun 28, 2018, 9:29:44 AM6/28/18

to rabbitm...@googlegroups.com

The suggestion with any "I did X to the config and it didn't have the effect I want" kind of question is to first verify

your effective configuration [1]. I cannot comment further on "it doesn't work" as that's too light on specifics and we do not guess on this list (too time consuming for our tiny team).

Environment variables for peer discovery configuration were all the rage in the rabbitmq-autocluster days. Try configuring the same

thing using RabbitMQ config file, as the docs recommend.

1. https://github.com/rabbitmq/rabbitmq-server/releases/tag/v3.7.7-rc.1

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.

Michael Klishin

unread,

Jun 28, 2018, 9:30:37 AM6/28/18

to rabbitm...@googlegroups.com

[1] should have been http://www.rabbitmq.com/configure.html#verify-configuration-effective-configuration, not the 3.7.7-rc.1 announcement

I am about to post.

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.

Reply all

Reply to author

Forward

RabbitMQ - AWS Discovery - No logging

David Shaw

Michael Klishin

David Shaw

Michael Klishin

David Shaw

Michael Klishin

Michael Klishin

David Shaw

Michael Klishin

Michael Klishin