ejabberd - Comments for "join cluster node problem"

I have 3 aws ec2 running same

jabber5354 — Fri, 06 May 2016 01:04:02 +0000

I have 3 aws ec2 running same version of ejabberd setup for version 16.04

1st server erlang cookie copied to 2nd and 3rd server.

For all 3 servers under /ejabberd-16.04/conf/ejabberdctl.cfg, line for node=ejabberd@xxxxxxx has been enable.

Now, i login into 2nd server and use command "join_cluster" which is something like this "ejabberdctl join_cluster 'ejabberd@xxx.xxx.xxx.xxx' and i get this error as shown below.

"Error: {no_ping, 'ejabberd@xx.xx.xx.xx'}

I try the same to join_cluster from 3rd server, gaves me same error.

I have all these 3 servers running fine at the moment without join_cluster but if once i do i get the error above.

Anyone can help? Thanks.

Check FIREWALL_WINDOW option

yurii_n — Fri, 18 Mar 2016 15:40:29 +0000

Check FIREWALL_WINDOW option in ejabberd/conf/ejabberdctl.cfg file. Its value should be something like 4200-4210. Also do not forget to open these ports for your nodes.
Check ERLANG_NODE option in the same file. If it is empty, you need to uncomment it and set
ejabberd@domain_name
where domain_name is ouptut of "hostname -f" command in linux shell.

This problem happened to me

davai — Fri, 18 Mar 2016 01:31:13 +0000

This problem happened to me before on Linux : see "resolv.conf" located in "/etc"

cat /etc/resolv.conf

If there is ".nameserver" at the begin u must remove this line. And after restart u must remove this line again then start ejabberd and every thing should work 100%

something is wrong.

taranis — Thu, 10 Dec 2015 09:48:36 +0000

something is wrong.

check erlang.cookie and check

jabber5354 — Wed, 09 Dec 2015 01:28:38 +0000

check erlang.cookie and check all port also, nothing works. report to the china region for compliance already. waiting for news but seems slow to me.

first check .erlangcookie

nets — Sat, 05 Dec 2015 05:00:13 +0000

first check .erlangcookie then open all port and and check it.

have added the 2 ports (4369

jabber5354 — Fri, 04 Dec 2015 01:47:24 +0000

have added the 2 ports (4369 & 5269) at the china region mentioned but problem still the same. not able to connect although the logs describe that it has been started but through web admin it is not accessible.

the logs indicate [warning] web:admin process - access of admin from failed with error: <>

ok will check and report my

jabber5354 — Fri, 04 Dec 2015 01:21:17 +0000

ok will check and report my findings here again. thx mate.

check 4369,5269 ports

nets — Thu, 03 Dec 2015 12:08:27 +0000

check 4369,5269 ports