ejabberd - Comments for "CGI Call to ejabberdctl"

Example system call using regular user

mfoss — Mon, 22 Sep 2008 16:12:45 +0000

Ah, ok, I didn't notice the requirement of executing the script with a regular user, not root.

I tried this using ejabberd trunk SVN. In your system probably you will have different ebin path and cookie path.

$ ejabberdctl
bash: /sbin/ejabberdctl: Permiso denegado

$ erl -noinput -sname ejactl -pa /lib/ejabberd/ebin/ -s ejabberd_ctl -extra ejabberd@localhost connected-users-number
RPC failed on the node ejabberd@localhost: nodedown

And in the ejabberd log files i see:

** Connection attempt from disallowed node ejactl@atenea **

Now i provide the cookie:

$ COOKIE=`sudo cat /var/lib/ejabberd/.erlang.cookie`

$ echo $COOKIE
PVMCWDKIODNMGKFRAJMW

$ erl -setcookie $COOKIE -noinput -sname ejactl -pa /lib/ejabberd/ebin/ -s ejabberd_ctl -extra ejabberd@localhost connected-users-number
1

limited ejabberdctl function from cgi

MikeDunne — Fri, 19 Sep 2008 18:58:44 +0000

1. ejabberdctl has way too many functions to make it available to any user. Therefore, intentionally limiting the call to the user-resources function as a presence check
2. The above script was called from a perl script cgi apache as the apache user.
3. Don't want to run from cgi as root.

ejabberdctl user-resources user server works in 2.0.2 as advertised, but, that's not the point or the issue.

This was just a handy way for processes (not IM stuff) to check for user/resource presence without having to log in, subscribe, etc., or interrogating the database (mnesia).

Once a user/resource was identified as present, then, and only then, would processes be applied to that user/resource.

Looked into XML-RPC methods - seem too complicated. If I could update the script to run with newer versions of the server, that would be great.

What is missing from the script?

Try ejabberdctl

mfoss — Fri, 19 Sep 2008 08:17:37 +0000

I didn't check in detail your script. I think you can use the included ejabberdctl script instead of it.

I tried this:

Installed ejabberd 2.0.2 using source code.
Started ejabberd

Then I execute:

$ sudo ejabberdctl user-resources badlop localhost
Home2
$

Of course, in your case the ejabberdctl script may be in a different location, and may require or not to be root.