Your message dated Fri, 03 Apr 2026 13:39:52 +0200
with message-id <[email protected]>
and subject line Re: Bug#1132445: ERL_EPMD_ADDRESS does not work to assign IP
address to undelying epmd
has caused the Debian Bug report #1132445,
regarding ERL_EPMD_ADDRESS does not work to assign IP address to undelying epmd
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1132445: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1132445
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: ejabberd
Version: 24.12-3+deb13u1
Severity: important
Related: https://github.com/processone/ejabberd/issues/4556
I set `ERL_EPMD_ADDRESS=127.0.0.1` in /etc/default/ejabberdctl.cfg
(iirc) and restart the daemon but epmd still listen on * instead of
127.0.0.1.
The official guide,
https://docs.ejabberd.im/admin/guide/distribution/#epmd said very clear:
"You should block the port 4369 in the firewall in such a way that only
the programs in your machine can access it, or configure the environment
variable ERL_EPMD_ADDRESS in the file ejabberdctl.cfg."
So please do either:
- Add a way to force epmd to use ERL_EPMD_ADDRESS value
- Or add some how-to to package description page:
https://packages.debian.org/trixie/ejabberd
--- End Message ---
--- Begin Message ---
tag 1132445 + invalid
notfound 1132445 24.12-3+deb13u1
thanks
Hi,
thank you for the report, but I believe you are mistaken.
> I set `ERL_EPMD_ADDRESS=127.0.0.1` in /etc/default/ejabberdctl.cfg
> (iirc) and restart the daemon but epmd still listen on * instead of
> 127.0.0.1.
That file does not exist on Debian and has no effect.
The correct file would be /etc/default/ejabberd .
Furthermore, on Debian, epmd is neither started nor controlled by
ejabberd.
epmd is its own systemd service provided by the erlang-base package.
So even if you were to add that setting to /etc/default/ejabberd,
it would have no effect.
> The official guide,
> https://docs.ejabberd.im/admin/guide/distribution/#epmd said very
> clear:
The official guide from upstream does not apply 1:1 to the ejabberd
package in Debian.
That's why ERL_EMPD_ADDRESS is explicitely patched out in the example
file which the package installs, see
https://salsa.debian.org/ejabberd-packaging-team/ejabberd/-/blob/master/debian/patches/ejabberdctl.cfg.example.diff?ref_type=heads
Please see what erlang-base has to offer regarding configuration of
epmd.service, and file a bug report against erlang-base if you think
it's necessary.
I guess you could always add an override to the systemd service for
epmd to adjust its behaviour to your needs.
Best wishes
--
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Philipp Huebner <[email protected]>
⢿⡄⠘⠷⠚⠋⠀ OpenPGP: 671925C5B8CDE74A52253DF9E5CA8C4925E4205F
⠈⠳⣄
--- End Message ---
