[erlang-questions] Re: How to tell epmd to release a name rigsitered but not valid any more?

[Michael Santos]

On Fri, May 07, 2010 at 10:31:32AM +0800, Seven Du wrote:
> Was there anyone but me has this problem? I have met quite a few times.
> 
> $ which erl
> /usr/local/bin/erl
> $ erl -v
> Erlang R13B02 (erts-5.7.3) [source] [smp:4:4] [rq:4] [async-threads:0]
> [hipe] [kernel-poll:false]
> 
> Eshell V5.7.3  (abort with ^G)
> 
> $ which epmd
> /usr/local/bin/epmd
> 
> $ epmd -names
> epmd: up and running on port 4369 with data:
> name freeswitch at port 8031
> name mos at port 61573
> name queue at port 58107
> name queue1 at port 16557
> name voiceEvents at port 57340
>
> For some reason I stoped queue,

How did you stop queue?

> $ netstat -an|grep 4369
> tcp        0      0 127.0.0.1:4369          127.0.0.1:23526         ESTABLISHED
> tcp        0      0 127.0.0.1:4369          127.0.0.1:57900         ESTABLISHED
> tcp        0      0 127.0.0.1:4369          127.0.0.1:5976          ESTABLISHED
> tcp        0      0 127.0.0.1:4369          127.0.0.1:30721         ESTABLISHED
> tcp        0      0 127.0.0.1:4369          127.0.0.1:42265         ESTABLISHED

> epmd: up and running on port 4369 with data:
> name freeswitch at port 8031
> name mos at port 61573
> name queue at port 58107
> name queue1 at port 16557
> name voiceEvents at port 57340

There are 5 connections in established state to epmd and 5 registered
names. Is the "queue" erlang node still running?

You can check which processes are holding the sockets open using lsof
(lsof -i tcp:4369)