Process-one Discussion Forums

Get User Info from ejabbered.

2008-05-08T03:58:36+01:00

Hi All,

I have installed ejabber2.0 on my machine and have created a couple users via UI and adding manually in cfg file. Now i could login with these new users.

I am new to jabber. I want to know:

1. How can i add friends so that i can see them as my friends and chat with them?
2. Do i always need to add users in ejabberd.cfg file, restart to relect the user?

Are there any API support to access the ejabber that i have installed on my machine.

Where can i find documentation regarding this.

Any help would be highly appreciated.

Thanks in advace.

Thanks,
Shridhar

Check if a user is logged on

2008-05-02T22:46:21+01:00

Hi.

Is there an API call I can do in order to check if a user is currently online?

Thanks!
--
Tor-Helge Persett

Sources des installeurs ejabberd sous linux

2008-04-27T22:32:43+01:00

Bonjour,

J’ai développé un module d’installation de ejabberd pour la solution SME Server (smeserver-ejabberd) qui se présente en format rpm et s’appuie sur l’installateur ejabberd-1.1.4-linux-x86-installer.bin.gz que vous avez développé.

Je prépare une mise à jour pour la version 2.0

Mon problème est lié à la licence GNU GPL. Mon paquetage source incorpore actuellement votre installeur, et je dois être capable pour le distribuer en conformité avec la GPL de donner l’accès au sources de l’installeur en question (ou de les incorporer directement dans le rpm source) . Est-il possible de les obtenir ?

Merci de votre réponse

Jean-Paul Leclère

Running yaws using cean

2008-04-25T06:20:53+01:00

Hi,

I am a newbie to erlang and to yaws. I would like to run yaws using cean. I have installed cean and yaws in cean—cean:display(installed). outputs “yaws” as the last entry. (All this is on a 64-bit AMD machine.)

Now how do I run the yaws that I installed using a custom config file that I have made? Is it possible to run the yaws by itself, or do I always have to start it from the interactive shell of cean?

yaws:start(). fails with the “failed to load setuid_drv” error that many people have reported.

Following the steps at http://www.erlang.org/pipermail/erlang-questions/2006-November/024153.html works as expected, without errors.

Is there a way to run yaws from a shell-script or some such, without having to type in all the configuration information in the interactive shell?

Thanks for your patience,
Philip

12.b.1

2008-02-29T22:02:05+01:00

Hi,

Is 12.b.1 supported? If not, is there a planned time-frame for this?

Just checking.

Thanks.

Kicking a user

2008-04-17T23:00:58+01:00

In ejabberd 1.1.4 I had a module which had the ability to kick a user, this was accomplished by routing a broadcast “disconnect” packet to the user via.

force_disconnect(User, Server, Msg) ->
    ejabberd_sm:route(
        jlib:make_jid("", "", ""),
        jlib:make_jid(User, Server, ""),
        {xmlelement, "broadcast", [], [{disconnect, Msg}]}
    ).

This no longer seems to work with ejabberd 2.0, i was wondering if their was an easier way of possibly doing this.

ejabberd-2.0.0 problem!!

2008-04-14T11:12:44+01:00

i encountered a problem with ejabberd 2.0.0 it was running fine with me until an incident happen the machine that hosts my ejabberd shutdowned and when it starts up ejabberd won’t work properly i tried to stop and start it again it files an errors in logs i will attach the log and the crach report

/var/log/ejabberd/sasl.log
=SUPERVISOR REPORT==== 13-Apr-2008::11:06:30 ===
Supervisor: {local,mnesia_sup}
Context: child_terminated
Reason: shutdown
Offender: [{pid,<0.63.0>},
{name,mnesia_kernel_sup},
{mfa,{mnesia_kernel_sup,start,[]}},
{restart_type,permanent},
{shutdown,infinity},
{child_type,supervisor}]

=SUPERVISOR REPORT==== 13-Apr-2008::11:06:30 ===
Supervisor: {local,mnesia_sup}
Context: shutdown
Reason: reached_max_restart_intensity
Offender: [{pid,<0.63.0>},
{name,mnesia_kernel_sup},
{mfa,{mnesia_kernel_sup,start,[]}},
{restart_type,permanent},
{shutdown,infinity},
{child_type,supervisor}]

=PROGRESS REPORT==== 13-Apr-2008::11:06:30 ===
supervisor: {local,crypto_sup}
started: [{pid,<0.120.0>},
{name,crypto_server},
{mfa,{crypto_server,start_link,[]}},
{restart_type,permanent},
{shutdown,2000},
{child_type,worker}]

=PROGRESS REPORT==== 13-Apr-2008::11:06:30 ===
application: crypto
started_at: ejabberd@localhost

=PROGRESS REPORT==== 13-Apr-2008::11:06:30 ===
supervisor: {local,ssl_sup}
started: [{pid,<0.126.0>},
{name,ssl_server},
{mfa,{ssl_server,start_link,[]}},
{restart_type,permanent},
{shutdown,2000},
{child_type,worker}]

=PROGRESS REPORT==== 13-Apr-2008::11:06:30 ===
supervisor: {local,ssl_sup}
started: [{pid,<0.127.0>},
{name,ssl_broker_sup},
{mfa,{ssl_broker_sup,start_link,[]}},
{restart_type,permanent},
{shutdown,2000},
{child_type,supervisor}]

=PROGRESS REPORT==== 13-Apr-2008::11:06:30 ===
application: ssl
started_at: ejabberd@localhost

=PROGRESS REPORT==== 13-Apr-2008::11:06:30 ===
supervisor: {local,stringprep_sup}
started: [{pid,<0.129.0>},
{name,stringprep},
{mfa,{stringprep,start_link,[]}},
{restart_type,permanent},
{shutdown,brutal_kill},
{child_type,worker}]

=CRASH REPORT==== 13-Apr-2008::11:06:31 ===
crasher:
pid: <0.36.0>
registered_name: []
error_info: {bad_return,
{{ejabberd_app,start,[normal,[]]},
{’EXIT’,
{{case_clause,
{aborted,
{node_not_running,ejabberd@localhost}}},
[{ejabberd_config,set_opts,1},
{ejabberd_app,start,2},
{application_master,start_it_old,4}]}}}}
initial_call: {application_master,
init,
[<0.5.0>,
<0.35.0>,
{appl_data,
ejabberd,
[ejabberd,
ejabberd_sup,
ejabberd_auth,
ejabberd_router,
ejabberd_sm,
ejabberd_s2s,
ejabberd_local,
ejabberd_listeners,
ejabberd_iq_sup,
ejabberd_service_sup,
ejabberd_s2s_out_sup,
ejabberd_s2s_in_sup,
ejabberd_c2s_sup,
ejabberd_mod_roster,
ejabberd_mod_echo,
ejabberd_mod_pubsub,
ejabberd_mod_irc,
ejabberd_mod_muc,
ejabberd_offline,
random_generator],
undefined,
{ejabberd_app,[]},
[acl,
adhoc,
configure,
cyrsasl_anonymous,
cyrsasl,
cyrsasl_digest,
cyrsasl_plain,
ejabberd_admin,
ejabberd_app,
ejabberd_auth_anonymous,
ejabberd_auth,
ejabberd_auth_external,
ejabberd_auth_internal,
ejabberd_auth_ldap,
ejabberd_auth_odbc,
ejabberd_auth_pam,
ejabberd,
ejabberd_c2s,
ejabberd_c2s_config,
ejabberd_config,
ejabberd_ctl,
ejabberd_frontend_socket,
ejabberd_hooks,
ejabberd_http,
ejabberd_http_bind,
ejabberd_http_poll,
ejabberd_listener,
ejabberd_local,
ejabberd_logger_h,
ejabberd_loglevel,
ejabberd_node_groups,
ejabberd_rdbms,

Add cookie support to ejabberd

2008-04-04T17:27:27+01:00

Hello,
I posted a brief guide describing how to add cookies support to ejabberd (link below) in a simple way.
I was wondering if it was possible to eventually release a patch for the users who needs this support
The patch is relatively simple and it would patch ejabberd_http.erl module and its header file ejabberd_http.hrl.
It works on ejabberd 1.1.x and ejabberd 2.x.
If needed I could send to you the cookie patch, or attach here the entire code.

(update)
I’m attaching the original post here:

To add cookies to HTTP POST/GET requests in ejabberd (1.1.x and 2.x) we have to add some fields in the request headers, setting up the request and state records in ejabberd_http.erl module and its header file ejabberd_http.hrl.

First of all, we will add the field cookie to the record request in ejabberd_http.hrl header file as follows:

-record(request, {method,
                  path,
                  q = [],
                  us,
                  auth,
                  lang = "",
                  data = "",
                  cookie = "", %% lp: cookie request field
                  ip
                 }).

As you can see we are referring to ejabberd 2.0 (in the request record we have the new field ip for new user info).

Now we will edit the ejabberd_http.erl module, adding the field request_cookie to the record state:

-record(state, {sockmod,
                socket,
                request_method,
                request_version,
                request_path,
                request_auth,
                request_cookie, %% lp: cookie request field
                request_keepalive,
                (...)

At this point, we have to pass cookies to handlers, modifying the process_headers and process_request functions:

In the process_header, we will add to the case construct

process_header(State, Data) ->
    SockMod = State#state.sockmod,
    Socket = State#state.socket,
    case Data of
        {ok, {http_request, Method, Uri, Version}} ->
   
    (...)
        {ok, {http_header, _, 'Authorization', _, Auth}} ->
            State#state{request_auth = parse_auth(Auth)};
        {ok, {http_header, _, 'Cookie', _, Cookie}} ->
            %% lp: setting up request header cookie
            State#state{request_cookie = Cookie};
        {ok, {http_header, _, 'Content-Length', _, SLen}} ->
    (...)

In the process_request we have to modify the function header as follows:

process_request(#state{request_method = 'GET',
                       request_path = {abs_path, Path},
                       request_auth = Auth,
                       request_lang = Lang,
                       request_cookie = Cookie, %% lp: cookie request field
                       request_handlers = RequestHandlers,
                       sockmod = SockMod,
                       socket = Socket} = State) ->
                       
                        (...)
                        Request = #request{method = 'GET',
                               path = LPath,
                               q = LQuery,
                               auth = Auth,
                               lang = Lang,
                               cookie = Cookie, %% lp: here again :)
                               ip=IP},
                        (...)

and in the next header too:

process_request(#state{request_method = 'POST',
                       request_path = {abs_path, Path},
                       request_auth = Auth,
                       request_content_length = Len,
                       request_lang = Lang,
                       request_cookie = Cookie, %% lp: cookie
                       sockmod = SockMod,
                       socket = Socket,
                       request_handlers = RequestHandlers} = State)
  when is_integer(Len) ->

              (...)
              Request = #request{method = 'POST',
                               path = LPath,
                               q = LQuery,
                               auth = Auth,
                               cookie = Cookie, %% lp: cookie the last one ;)
                               data = Data,
                               lang = Lang},
              case process(RequestHandlers, Request) of
                 (...)

Now, we are ready to add the cookie request’s field to our modules processing http requests:

process(#request{us = _US,
                     path = "login",
                     q = _Query,
                     lang = _Lang,
                     cookie = _Cookie} = Request) ->
          
              %% _Cookie will contain the request cookie now
              %% Manage request by cookies
              %% Send response :)

Cheers,
LP

Link:
http://erlangdevelopers.splinder.com/post/16609181/Add+cookie+support+in+ejabberd

What is CEAN - A suggestion

2008-03-10T00:50:48+01:00

I am a newbie to erlang.

When I heard of CEAN, I kind of knew what it was, but there was no place which said:

CEAN is a Erlang module that must be installed into a Erlang system before it will work.

Once it is installed, issuing the command cean:help() from a erl shell. will show which functions are made available by the cean module.

As an example:

cean:help().
The functions are: [available,
depends,
display,
help,
install,
installed,
etc....]

I finally figured out that I had to be in a erl shell before I could use cean. The tip-off was “cean:help().” which I recognized as being a erl command to use the cean module and execute the help function.

I would suggest that this information should be made very prominent to help new users of erlang to get up and running.

Windows .exe in linx/amd64 cean distribution

2008-02-22T12:42:31+01:00

hi,

Again, sorry .

appmon:start() doesn’t work here, because it want’s to execute wish84s.exe which might be a problem under linux.

1> appmon:start().
sh: /home/einstein/binsrc/cean/erlang/lib/gs-1.5.6/priv/linux-amd64/tcl/bin/wish84s.exe: cannot execute binary file
sh: /home/einstein/binsrc/cean/erlang/lib/gs-1.5.6/priv/linux-amd64/tcl/bin/wish84s.exe: Success
<shell hangs>

% file erlang/lib/gs-1.5.6/priv/linux-amd64/tcl/bin/wish84s.exe
erlang/lib/gs-1.5.6/priv/linux-amd64/tcl/bin/wish84s.exe: MS-DOS executable PE for MS Windows (GUI) Intel 80386

I’m using lastest cean for linux amd64.
cean:version().
“CEAN Erlang/OTP R11B-4 erts-5.5.4 linux-amd64 devel”

cu,
michael