ejabberd - Comments for "ejabberd 2.1.6 with postgres 9"

Re

mfoss — Mon, 14 Feb 2011 12:56:32 +0000

natalius wrote:

1. The size of beam file is almost twice size. Not sure has impact or not.

That is normal: the beam files included in the installer are compressed with some option. Don't worry about the size.

natalius wrote:

2. Your modification code looks like just adding some information only.

Right, my modification was intended to print debug information.

natalius wrote:

But the result is I can login successfully with the following error. Looks like the source code of pgsql_proto.erl file (included on the windows installer) is not the same with mine.

Program Files\ejabberd-2.1.6\lib\pgsql-2009.1102\ebin

The last change in pgsql driver was done in 2009/11/02, that's the version included in the installer and that's the version you compiled, so it's strange that your compilation works and the initial did not.

https://forge.process-one.net/changelog/ejabberd-modules/pgsql/trunk/src

natalius wrote:

3. The following error.

Check in the ejabberd Guide the mod_pubsub configuration example that says:
"Using ODBC database requires use of dedicated plugins."

I tried to follow your above

natalius — Mon, 14 Feb 2011 07:53:20 +0000

I tried to follow your above instruction. Here is my steps:

1. Download pgsql_proto.erl from https://svn.process-one.net/ejabberd-modules/pgsql/trunk/src/pgsql_proto...
2. Compile pgsql_proto.erl by using c(pgsql_proto.erl) on Program Files\ejabberd-2.1.6\bin\werl.exe
3. Stop ejabberd service
4. I put the generated beam files to Program Files\ejabberd-2.1.6\lib\pgsql-2009.1102\ebin. The size of pgsql_proto.beam is 12Kb. Comparing with the original one is 6Kb. Not sure why the size has big different.
5. Start the ejabberd service
6. The login process is successfull but I receive the following error. I think this error does not impact with the application. Just want to make sure only. Thanks

My question:
1. The size of beam file is almost twice size. Not sure has impact or not.
2. Your modification code looks like just adding some information only. So basically, I cannot login to ejabberd. But the result is I can login successfully with the following error. Looks like the source code of pgsql_proto.erl file (included on the windows installer) is not the same with mine.
3. The following error.

Thanks for your kind response.

=ERROR REPORT==== 2011-02-14 14:35:06 ===
E(<0.356.0>:mod_pubsub_odbc:3624) : transaction return internal error: {aborted,
{undef,
[{node_flat,
get_entity_subscriptions_for_send_last,
["pubsub.natalius-vaio",
{jid,
"admin",
"natalius-vaio",
"40016422031297668906430002",
"admin",
"natalius-vaio",
"40016422031297668906430002"}]},
{mod_pubsub_odbc,
node_call,
3},
{ejabberd_odbc,
execute_bloc,
1},
{ejabberd_odbc,
run_sql_cmd,
4},
{p1_fsm,
handle_msg,
10},
{proc_lib,
init_p,
5}]}}

=ERROR REPORT==== 2011-02-14 14:35:06 ===
E(<0.356.0>:mod_pubsub_odbc:3624) : transaction return internal error: {aborted,
{undef,
[{node_hometree,
get_entity_subscriptions_for_send_last,
["pubsub.natalius-vaio",
{jid,
"admin",
"natalius-vaio",
"40016422031297668906430002",
"admin",
"natalius-vaio",
"40016422031297668906430002"}]},
{mod_pubsub_odbc,
node_call,
3},
{ejabberd_odbc,
execute_bloc,
1},
{ejabberd_odbc,
run_sql_cmd,
4},
{p1_fsm,
handle_msg,
10},
{proc_lib,
init_p,
5}]}}

=ERROR REPORT==== 2011-02-14 14:35:06 ===
E(<0.356.0>:mod_pubsub_odbc:3624) : transaction return internal error: {aborted,
{undef,
[{node_pep,
get_entity_subscriptions_for_send_last,
["pubsub.natalius-vaio",
{jid,
"admin",
"natalius-vaio",
"40016422031297668906430002",
"admin",
"natalius-vaio",
"40016422031297668906430002"}]},
{mod_pubsub_odbc,
node_call,
3},
{ejabberd_odbc,
execute_bloc,
1},
{ejabberd_odbc,
run_sql_cmd,
4},
{p1_fsm,
handle_msg,
10},
{proc_lib,
init_p,
5}]}}

ejabberd already received a

mfoss — Wed, 02 Feb 2011 10:28:24 +0000

ejabberd already received a change related to PostgreSQL 9 support: https://support.process-one.net/browse/EJAB-1359

Maybe some parts of the code don't yet support 9.

Please edit pgsql_proto.erl and replace the function connected with this one, where I've added some io:fomat lines. Compile that file, install, and trigger again the error. Let's hope you get log lines in ejabberd.log and we can debug the problem.

%% Connected state. Can now start to push messages
%% between frontend and backend. But first some setup.
connected(StateData, Sock) ->
    %% Protocol unwrapping process. Factored out to make future
    %% SSL and unix domain support easier. Store process under
    %% 'socket' in the process dictionary.
    ResStarted = pgsql_tcp:start_link(Sock, self()),
    io:format("startedlink: ~n~p~n", [ResStarted]),
    {ok, Unwrapper} = ResStarted,
    ResControlled = gen_tcp:controlling_process(Sock, Unwrapper),
    io:format("controlledprocess: ~n~p~n", [ResControlled]),
    ok = ResControlled,

    %% Lookup oid to type names and store them in a dictionary under
    %% 'oidmap' in the process dictionary.
    Packet = encode_message(squery, "SELECT oid, typname FROM pg_type"),
    ResSent = send(Sock, Packet),
    io:format("sent: ~n~p~n", [ResSent]),
    ok = ResSent,
    ResProcessed = process_squery([]),
    io:format("processsquery: ~n~p~n", [ResProcessed]),
    {ok, [{"SELECT" ++ _, _ColDesc, Rows}]} = ResProcessed,
    Rows1 = lists:map(fun ([CodeS, NameS]) ->
                              Code = list_to_integer(CodeS),
                              Name = list_to_atom(NameS),
                              {Code, Name}
                      end,
                      Rows),
    OidMap = dict:from_list(Rows1),

    {ok, StateData#state{oidmap = OidMap}}.