epmd not cleaning up node name if node is down. Click to flag this post

Mickaël Rémond mickael.remond@REDACTED
Thu Dec 31 12:27:42 CET 2009


Hello,

I have found this message from the archive:

By Zbyszek Żółkiewski Aug 15, 2008:

> Hello,
> 
> I have noticed that epmd is not cleaning node names if there are multiple nodes running on the same system and one of the node is shuted down.
> When i try to run node (jggtrans) In logs i can see:
> 
> Aug 15 12:22:05 xmpp epmd: epmd: epmd running - daemon = 1
> Aug 15 12:22:05 xmpp epmd: epmd: node name already occupied jggtrans
> Aug 15 12:22:46 xmpp epmd: epmd: epmd running - daemon = 1
> Aug 15 12:22:46 xmpp epmd: epmd: node name already occupied jggtrans
> 
> epmd - name:
> 
> epmd: up and running on port 4369 with data:
> name jggtrans at port 46477
> name zero at port 58591

We find that this problem happens more and more often. It is reproducible very often on Amazon deployments for example.

The only solution is to kill epmd in this situation, otherwise you are stuck with a duplicate name. If you have other Erlang VM running on the same machine in cluster, you are out of luck because, you have to restart all Erlang VM.

Do you need help to investigate on this problem ?

Thank you !

-- 
Mickaël Rémond
 http://www.process-one.net/



More information about the erlang-bugs mailing list