epmd does not support binding to an IPv4 address anymore
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
erlang (Ubuntu) |
Confirmed
|
High
|
Unassigned |
Bug Description
The bug is actually located in erlang itself. epmd fails to bind to any IPv4 address if instructed to do so
[Impact]
Users of RabbitMQ in IPv4 environments are unable to start rabbitmq unless the environment variable ERL_EPMD_ADDRESS is unset. In case of disabled IPv6 support there is no valid setting for ERL_EPMD_ADDRESS as
* IPv4 addresses will be rejected as syntacitcally invalid
* IPv6 addresses will fail to bind
[Test Case]
service rabbitmq-server stop && killall epmd
ERL_EPMD_
epmd: Thu Sep 25 21:00:16 2014: cannot parse IP address "127.0.0.1"
same could be acieved with the epmd's -address option
In case IPv6 support is disabled:
ERL_EPMD_
epmd: Thu Sep 25 21:01:40 2014: failed to bind socket: Cannot assign requested address
-- rabbitmq case:
cat rabbitmq-env.conf
export RABBITMQ_
export RABBITMQ_
export ERL_EPMD_
service rabbitmq-server start
* Starting message broker rabbitmq-server
* FAILED - check /var/log/
Commenting/removing the "export ERL_EPMD_
[Possible cause]
In this bug: https:/
The issue was fixed using -DEPMD6" in CPPFLAGS (https:/
There is another complaint regarding the same issue here: https:/
[System info]
lsb_release -rd
Description: Ubuntu 14.04.1 LTS
Release: 14.04
apt-cache policy rabbitmq-server
rabbitmq-server:
Installed: 3.2.4-1
Candidate: 3.2.4-1
apt-cache policy erlang-base
erlang-base:
Installed: 1:16.b.
Candidate: 1:16.b.
description: | updated |
description: | updated |
affects: | rabbitmq-server (Ubuntu) → erlang (Ubuntu) |
tags: | added: cts |
Changed in erlang (Ubuntu): | |
assignee: | nobody → Dariusz Gadomski (dgadomski) |
tags: |
added: sts removed: cts |
tags: | removed: sts |
Changed in erlang (Ubuntu): | |
assignee: | Dariusz Gadomski (dgadomski) → nobody |
Status changed to 'Confirmed' because the bug affects multiple users.