How to set up an ejabberd cluster?

I am using 2 instances of ec2 on which ejabberd 13.12 is installed. I follow this guide to configure the cluster. In the second node, when I ran the command -

 erl -sname ejabberd \

-mnesia dir '"/var/lib/ejabberd/"' \

-mnesia extra_db_nodes "['ejabberd@first']" \

-s mnesia

The first time a node error occurs -

Application ejabberd started on node ejabberd@ejabberdn1
dets: file "/var/lib/ejabberd/schema.DAT" not properly closed, repairing ...

=SUPERVISOR REPORT==== 27-May-2014::07:11:59 ===
 Supervisor: {local,mnesia_kernel_sup}
 Context:    child_terminated
 Reason:     killed
 Offender:   [{pid,<0.152.0>},
              {name,mnesia_locker},
              {mfargs,{mnesia_locker,start,[]}},
              {restart_type,permanent},
              {shutdown,3000},
              {child_type,worker}]


=SUPERVISOR REPORT==== 27-May-2014::07:11:59 ===
 Supervisor: {local,mnesia_kernel_sup}
 Context:    shutdown
 Reason:     reached_max_restart_intensity
 Offender:   [{pid,<0.152.0>},
              {name,mnesia_locker},
              {mfargs,{mnesia_locker,start,[]}},
              {restart_type,permanent},
              {shutdown,3000},
              {child_type,worker}]

It gives an error when splitting the mnesia network into the second node. How to solve this problem?

+4
source share
2 answers

Finally, I solved my problem. The problem is the Erlang OTP version. I used Ejabberd 13.12 and Erlang OTP 15B1. Although this combination works well on the local network, it does not work on AWS EC2. Now I have replaced the Erlang OTP OTP 17 version and my cluster is working fine.

0
source

, ..

, this, 5 , ( ). , , , . ( - , , , .;))

+1

Source: https://habr.com/ru/post/1542122/


All Articles