You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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 my
ps 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?
The text was updated successfully, but these errors were encountered: