RabbitMQ aws discovery plugin fails to discover the local node

112 views

Skip to first unread message

Andrey

unread,

Aug 12, 2022, 3:40:37 PM8/12/22

to rabbitmq-users

I am setting up RabbitMQ 3.10.6 to run on a cluster in EC2's. The error I get when starting the service is:

Failed to lock with peer discovery backend rabbit_peer_discovery_aws: "Local node rabbit@i-0d4f6fe8da16963aa is not part of discovered nodes ['rabbit@ip-10-189-160-84',\n 'rabbit@ip-10-189-160-90',\n 'rabbit@ip-10-189-160-121']"

So, it discovers the nodes correctly, but it fails to match its own node to the list because of naming format - it discovers its own node as rabbit@ip-10-189-160-84 but tries to match it by host name rabbit@i-0d4f6fe8da16963aa and fails, obviously.

RabbitMQ.conf:

cluster_formation.peer_discovery_backend = aws cluster_formation.aws.region = eu-central-1 cluster_formation.aws.instance_tags.service = rabbitmq cluster_formation.randomized_startup_delay_range.min = 5 cluster_formation.randomized_startup_delay_range.max = 60 cluster_formation.node_cleanup.only_log_warning = true