ejabberd - Comments for "ejabberd-2.0.2 + ejabberd_xmlrpc"

Ha!

xyu — Sun, 02 Nov 2008 19:27:45 +0000

That was strange, but reinstalling PHP5 made example script to work. I gave up trying PHP4 version of script.

Thanks for help.

Khe... Guess what?!

xyu — Fri, 31 Oct 2008 19:37:19 +0000

Right, the scripts are not working :-)) Neither my version for PHP4(in lots of variations and tunings) nor PHP5 Example(raw, modified, re-modified, re-re-modified and so on )! :-)
Interested?
So, simply:
PHP4 - timeouts:
{tcp_serv,139,{xmlrpc_http,handler,timeout}}(ejabberd.log)
and PHP5 has no reaction, giving (immediate) empty response and saying

expat reports error code 3
        description: no element found
        line: 1
        column: 0
        byte index: -1
        total bytes: 0

while $response = xmlrpc_decode($file);, leaving no traces in any log(debug level is 5).

Trunks are the latest: everytime I try to manage this task, i synchronize svn, and if any changes are noticed, I recompile :-)))

As for configuration:

{listen,
 [
    {4560, ejabberd_xmlrpc, [
        {ip, {192, 168, 100, 250}},
        {maxsessions, 10},
        {timeout, 5000},
        {access, all}]}
...

I tried also all for IP, modifying PHP code to request from different, but no changes.

Oh, one notice: when PHP4 script send incorrect(as for HTTP/1.1) request, the server responses like

HTTP/1.1 400 Bad Request
Content-Length: 0
Server: Erlang/1.13
Content-Type: text/xml

so, it's not really dead :-))
Special errors in PHP5-example(like "POASASST" except "POST" as method) didn't make any changes: just quick empty answer.
And I also check available for ejabberdctl commands, and used the simples, which has no empty response: registered_users.
The command from example(user_resources) returns empty, while user is offline. (At first, I thought, that could be the reason)

Posting pre-generated request(from PHP4)

POST /RPC2 HTTP/1.1
User-Agent: XMLRPCClientmod_xmlrpc
Content-Type: text/xml
Content-Length: 303
<?xml version="1.0" encoding="utf-8"?>
<methodCall>
<methodName>registered_users</methodName>
<params>
 <param>
  <value>
   <struct>
    <member>
     <name>host</name>
     <value>
      <string>localhost</string>
     </value>
    </member>
   </struct>
  </value>
 </param>
</params>
</methodCall>

via telnet gives the same - timeout - result.

I have no thoughts not to believe Your words as for everything works for You, so I guess, the problem is in system configurations, or simply in OS differences.
Of course, it can be, that I have "broken" PHP5 :-)) I'll check it later, using another server :-)))
Блять.
Any ideas? :-))))

Next attempt :-)

xyu — Tue, 28 Oct 2008 15:06:17 +0000

:-))) Hi!
Once again :-))
Really, for the first time I used sources from http://www.process-one.net/en/ejabberd/downloads/ page.
Now I'll show step-by-step process of installing eJabberd+modules.
0) Fully reinstall (ported) Erlang(still having erlang-r12b4)
1) Synchronize SVN(ejabberd:1671;modules:799)
2) cd [path/to/ejabberd/svn/subdirectory]/2.0.x/src
3) ./configure with the same options
4) gmake; gmake install
5) Modifying configuration(as in first post, but removing any "access" rule)
6) cd [path/to/ejabberd_modules/svn/subdirectory]/ejabberd_xmlrpc/trunk
7) ./build.sh
8) Copying ./ebin/*.beam to .../jabber/var/lib/ejabberd/ebin
9) Extract xmlrpc-1.13

cd xmlrpc-1.13/src;
gmake;
cp ../ebin/*.beam /home/jabber/var/lib/ejabberd/ebin;

10) 6)-8) for mysql(as I used odbc authentication)
11) Starting ejabberd
12) Now have running server with working "messaging" service and listening on 4560(as ejabberd_xmlrpc)
13) But :-(( Still have crash of listener with any symbol, sent to this port.

I tried an internal authentication also, but the result was the same.
sasl.log:

=CRASH REPORT==== 27-Oct-2008::14:18:23 ===
  crasher:
    pid: <0.201.0>
    registered_name: []
    exception error: no case clause matching independent
      in function  ejabberd_socket:start/4
      in call from ejabberd_listener:accept/3
    initial call: ejabberd_listener:init(4560,ejabberd_xmlrpc,
                                         [{ip,{192,168,100,250}},
                                          {maxsessions,10},
                                          {timeout,5000}])
    ancestors: [ejabberd_listeners,ejabberd_sup,<0.36.0>]
    messages: []
    links: [#Port<0.350>,<0.200.0>,#Port<0.333>]
    dictionary: []
    trap_exit: false
    status: running
    heap_size: 377
    stack_size: 23
    reductions: 577
  neighbours:
=SUPERVISOR REPORT==== 27-Oct-2008::14:18:23 ===
     Supervisor: {local,ejabberd_listeners}
     Context:    child_terminated
     Reason:     {case_clause,independent}
     Offender:   [{pid,<0.201.0>},
                  {name,4560},
                  {mfa,
                      {ejabberd_listener,start,
                          [4560,ejabberd_xmlrpc,
                           [{ip,{192,168,100,250}},
                            {maxsessions,10},
                            {timeout,5000}]]}},
                  {restart_type,transient},
                  {shutdown,brutal_kill},
                  {child_type,worker}]

ejabberd.log:

=INFO REPORT==== 2008-10-27 14:18:23 ===
I(<0.201.0>:ejabberd_listener:112) : (#Port<0.350>) Accepted connection {{192,168,100,250},56032} -> {{192,168,100,250},4560}

:-)
As soon as I have free time, I'll try to use older version of Erlang, not ported for FreeBSD, but downloaded from their own site :-)))

P.S. Just before posting, I've reread Your answer and got, that 2.0.x is not what I need :-)) and tried ejabberd/trunk/src. But I was surprised at crashing ejabberd at startup even with default configuration :-)) So... I'm lost in conjectures for now :-)) Hope, I will be able to manage it with next attempt :-))

2008-10-28:
P.P.S. Just a sec. The crashing .../trunk installation was "repaired" by killing remaining processes of erlang, running in daemon mode. But I found, that this version is 2.1.0-alpha :-)) So, I guess, that is not, what I really need as working application :-))

P.P.P.S But this alpha version works with ejabberd_xmlrpc at first sight :-)) Thanks for help and advice :-)

A small suggestion: if ejabberd_xmlrpc is not supposed to work with pre-2.1.x versions of ejabberd, it would be nice to notice that fact on http://www.ejabberd.im/ejabberd_xmlrpc, because "ejabberd trunk SVN 1635 or newer" is not very clear condition(because there are alternative sources of distributions, like releases on commercial site http://www.process-one.net/en/ejabberd/downloads/).

Works for me. Ensure you run ejabberd TRUNK svn.

mfoss — Tue, 21 Oct 2008 21:02:39 +0000

It works for me. I tried ejabberd trunk SVN 1662 with ejabberd_xmlrpc trunk from ejabberd-modules SVN 491. I configured similar to you, and tried the revised PHP client from README.txt

Some advices:

Are you sure you are using ejabberd trunk SVN, not the 2.0.x branch, right?
To start playing, don't put the 'access' option in the 4560 port. Once you get the XMLRPC calls working, you can focuse in security.
Use the PHP example client provided in the README.txt . Check the recent SVN, because I've updated it to work with ejabberd_xmlrpc correctly.
I think this is not important, this is only for completeness: I used Erlang R12B-3 (from Debian package), PHP 5.2.6 (Debian package)

Some answers to simple questions

mfoss — Tue, 21 Oct 2008 18:40:36 +0000

xyu wrote:

I'm trying to setup ejabberd_xmlrpc, but smth. goes wrong.
Is it smth. wrong with my system, or within module ejabberd_xmlrpc? :-))

I am not surprised: you are the first person to try ejabberd_xmlrpc, and probably you found some bug in it :)
Thanks for your detailed explanations, I'll look them in detail this week and provide you a response to the main problem.

Until then, I answer the simple questions:

xyu wrote:

but what an irritating warnings appear while compiling patch?
Can this be just ignored, or can it influence the working process in some way?

Don't worry about all those warning messages of Erlang XMLRPC.

xyu wrote:

send notification messages to registered users(not announcements, but personalized), not creating full-featured Jabber-bot with annoying authorization process for every single message.
So if You know, that it is impossible with ejabberd_xmlrpc, just let me know, and mentioned problem will disappear at once. :-)))

If you get ejabberd_xmlrpc working, you can execute any 'ejabberd command' that is available in your ejabberd server. ejabberd trunk SVN provides several commands, and you can install modules that provide more commands. For instance, mod_admin_extra provides the command you want:

$ ejabberdctl help send_message

  Command Name: send_message

  Arguments: from::string
             to::string
             subject::string
             body::string

  Returns: res::rescode

  Tags: stanza

  Description: Send a headline message to a local or remote bare of full JID

Another solution to your initial problem, unrelated to ejabberd_xmlrpc, is to use mod_rest (also available in ejabberd-modules SVN). I didn't try that module, but its README looks interesting:

This is an ejabberd module that adds an HTTP handler that allows HTTP
clients to literally post arbitrary message stanzas to ejabberd. Those
stanzas then get shoved through ejabberd's router just like any other
stanza.

In that case, maybe you need to enable this in your configure:

--enable-web=no \