So I have installed ejabberd twice, on the same box, two difference configurations, each tied to their own IP address and can't seem to get them started. One will start, or the other will start, but I cannot get both to start at the same time. I get crashes on whichever one starts second. Not only that, but running ejabberdctl stop stops whichever one is started, regardless of which configuration I'm trying to start. For example, if I run A, and run the stop script from the install B with configuration for another IP address, it still kills the A running instance.
Related links (not quite covering what I want to do):
Example multiple IP addresses (http://www.ejabberd.im/node/3374)
I'm running ejabberd-2.1.8
Are there changes I can make to the ejabberdctl command script to allow two instances running on the same box tied to different IP addresses?
Sample configuration:
{listen,
[
{5222, ejabberd_c2s, [
{certfile, "/home/motive/ecs2/ejabberd-2.1.8/conf/server.pem"}, starttls_required,
{access, c2s},
{shaper, c2s_shaper},
{max_stanza_size, 65536},
{ip, {135,13,17,240}}
]},
{5280, ejabberd_http, [
{request_handlers, [
{["rest"], mod_rest}
]},
web_admin,
{ip, {135,13,17,240}}
]}
]}.
Problem solved. The
Problem solved. The collision is in the ejabberd node names. The change was to simply rename the node under the /conf/ejabberdctl.cfg
The entry
ERLANG_NODE=ejabberd@host
just needed to be renamed to
ERLANG_NODE=node2@host