[rabbitmq-discuss] Identifying TCP Listeners.

[Adam Tauno Williams]

On Wed, 2012-04-11 at 13:15 -0400, Adam Tauno Williams wrote:
> On Wed, 2012-04-11 at 11:59 +0100, Michael Bridgen wrote:
> > On 04/11/2012 11:52 AM, Adam Tauno Williams wrote:
> > > On Wed, 2012-04-11 at 06:49 -0400, Adam Tauno Williams wrote:
> > >> How can I determine what 'service' is active on a port via RabbitMQ?
> > >> I've figured out all but TCP/49974
> > >> 0 0.0.0.0:4369  epmd [Erlang Port Mapper]
> > >> 0.0.0.0:49974   beam.smp [????]
> > >
> > > Actually, this port seems to 'float', as it is different every time I
> > > restart Rabbit.
> > I expect it's Erlang distribution -- i.e., it's the port the node 
> > advertises in epmd so other nodes can communicate with it.
> 
> Ah, that sound's reasonable.
> 
> From netstat:
> tcp   0   0 0.0.0.0:50000  0.0.0.0:*    LISTEN      1434/beam.smp       
> tcp   0   0 0.0.0.0:4369   0.0.0.0:*    LISTEN      1296/epmd           
> tcp   0   0 0.0.0.0:55672  0.0.0.0:*    LISTEN      1434/beam.smp       
> tcp   0   0 127.0.0.1:5672 0.0.0.0:*    LISTEN      1434/beam.smp 
> 
> Are there any configuration parameters to control how that port is
> bound, selected, or published?

With - 
rabbitmq-server-2.8.1-1.suse.noarch
erlang-R15B-2.1.i586
 - I can specify -
{
  kernel, [ {inet_dist_use_interface, [ {"127.0.0.1"} ] } ]
 }
 - /etc/rabbitmq/rabbitmq.config  and the server still starts, but it
has no effect on how the epmd or beam.smp bind.