[ejabberd] ejabberdctl won't talk to ejabberd

Badlop badlop at safe-mail.net
Wed Mar 9 18:18:01 MSK 2005

Michael Christian escribió:
> So is there a secret to getting ejabberdctl to talk to ejabberd?
> I have ejabberd running well:
> /******************************/
> -bash-2.05b$ ejabberd
> Erlang (BEAM) emulator version 5.4.3 [source] [hipe] [threads:0]
> [kernel-poll]
>  Eshell V5.4.3  (abort with ^G)
> (ejabberd at foo.bar.com)1>
> /******************************/

Just curiosity: what operating system are you running, FreeBSD?

You have kernel-poll enabled on Erlang and on the OS, so you are one of the few lucky 
people able to use Kernel Poll with ejabberd (and any Jabber server, actually), a feature 
that reduces enormously CPU consumption on high number of connections to the server.


> But ejabberdctl refuses to talk to that node:
> /******************************/
> -bash-2.05b$ sudo ejabberdctl ejabberd at foo.bar.com status
> Can't get node 'ejabberd at foo.bar.com' status: nodedown
> /******************************/
> Is there some erlang configuration piece I might be missing?  I'm using
> -name, rather than -sname.

Maybe you are messing with the Erlang cookie (not related to web browser 'cookies').

If this is the case, ejabberd will show that message:

> =ERROR REPORT==== 9-Mar-2005::14:37:43 ===
> ** Connection attempt from disallowed node ejabberdctl at myserver **

You can make sure ejabberd and ejabberdctl have the same cookie
setting it in an option, adding to ejabberd start script:
erl .... -setcookie mycookie232eE
and to ejabberdctl start script
erl .... -setcookie mycookie232eE

If this solves the problem, you should check why did ejabberd and ejabberdctl use 
different cookies. One reason is that you run each command one as a different user.

If it finally works, please comment how did you solve it, so we can help other people with 
the same problem.

More information about the ejabberd mailing list