Tcp-ip sockets using high port numbers, such as 51842, are being open by process 'beam' on a linux machine, running ejabberd 2.0.0. Are these sockets necessary for ejabberd functionality? Is this something specific to the Erlang VM? I cannot find a port range that includes 51842 in the config file. Is there any way to control this?
Thanks.
http://www.ejabberd.im/listen
http://www.ejabberd.im/listen-strange-port ?
You can also check the newer ejabberd guide
In addition to the link provided by Evadim, you can also check the ejabberd guide, since version 2.0.1 includes some explanations about this topic.
I summarize them here again:
Are these sockets necessary for ejabberd functionality?
Not strictly for Jabber support. Those ports are used by the ejabberdctl command line administration script, commonly used to stop and restart ejabberd. They are also used for clustering if required.
Is this something specific to the Erlang VM?
Yes, that is implemented by Erlang/OTP, hence the options to control it must be passed to 'erl' when starting ejabberd. Check bellow.
I cannot find a port range that includes 51842 in the config file.
Is there any way to control this?
When starting the Erlang VM for ejabberd (usually this is done in a script called ejabberdctl or ejabberd), you can include: