[ejabberd] ejabberd opening unperdictable high number ports

zhong ming wu mr.z.m.wu at gmail.com
Sat Nov 27 18:48:41 MSK 2010


On Fri, Nov 26, 2010 at 9:48 PM, Konstantin Khomoutov
<flatworm at users.sourceforge.net> wrote:
>
> Most probably this is a port opened by the Erlang emulator process for
> the communication with the epmd daemon.
> Yoou can run `epmd -names` to see whether the port listed for the
> name "ejabberd" matches that of listed in `netstat -nltp|grep beam`.
>
> This happens because ejabberd processes can form a cluster which is
> maintained using the means inherent to Erlang. Sending messages between
> Erlang processes running on nodes located on physically different boxes
> require TCP connectivity; hence the port open to talk with epmd.
>
> I beleive stock ejabberd features the FIREWALL_WINDOW setting in its
> startup script which allows to restring the port (or port range) used
> for this sort of communication.

Konstantin,

Thanks for your explanation.  I have managed to set FIREWALL_WINDOWS setting
now have a much better handle on this issue.


More information about the ejabberd mailing list