Closed kouinkouin closed 1 year ago
epmd is used by the erlang node that contains ejabberd for clustering and accepting ejabberdctl queries. So, it's normal to have epmd running at the same time that the beam process.
What does annoy you is to have a defunct epmd?
epmd is started automatically by erlang when the erlang node is being started, and keeps alive even when the erlang node is stopped. For that reason, the ejabberdctl script attempts to kill epmd when ejabberd stops, but maybe it didn't succeed in your case.
By the way, using recent Erlang versions it's possible to use erlang without epmd. Support for that was recently added to ejabberd, see 30f1e284681db482ef78da6d865ccc79120e4ca3 and the GHCR image 5ee1dc9e8d80d52ec9f3dd3f043dfdd4c90c303a.
Thanks for the explanation and the link to the doc. But I am alone with the issue? You (or someone else) have not the case? If not, I will try to compare with a clean config.
Hi,
First, thanks for the image :-) .
After a
run
(via docker-compose), I got a zombie process "epmd". Here a part of myps faux
(from the host):In a
docker top ejabberd
, the zombie process doesn't appear:ejabberd/ecs
is the only container with zombie processes. Has someone an idea to suppress/fix the process?