https://bugzilla.redhat.com/show_bug.cgi?id=1163812
--- Comment #1 from Chris Sharp <chrissharp09(a)comcast.net> ---
In my case, it's doing *anything* with ejabberdctl - not just registering.
My steps on a clean installation of Fedora 21:
1. yum install ejabberd
2. systemctl start ejabberd.service
3. ejabberdctl status
[root@localhost ~]# ejabberdctl status
Failed RPC connection to the node ejabberd@localhost: nodedown
Commands to start an ejabberd node:
start Start an ejabberd node in server mode
debug Attach an interactive Erlang shell to a running ejabberd node
live Start an ejabberd node in live (interactive) mode
Optional parameters when starting an ejabberd node:
--config-dir dir Config ejabberd: /etc/ejabberd
--config file Config ejabberd: /etc/ejabberd/ejabberd.yml
--ctl-config file Config ejabberdctl: /etc/ejabberd/ejabberdctl.cfg
--logs dir Directory for logs: /var/log/ejabberd
--spool dir Database spool dir: /var/lib/ejabberd
--node nodename ejabberd node name: ejabberd@localhost
/var/log/ejabberd/error.log:
2015-03-07 09:18:31.948 [error] <0.562.0> ** Connection attempt from disallowed
node 'ejabberdctl-1@localhost' **
There are hints from possibly related issues from ejabberd support that point
to .erlang.cookie mismatches - that's the current rabbit I'm chasing down the
hole...
--
You are receiving this mail because:
You are on the CC list for the bug.