Difference in behaviour of "telepathy-gabble", when ejabberd is used with CentOS and Debian-6
Jerry Vonau
jvonau at shaw.ca
Sun Jan 20 13:41:16 EST 2013
On Sun, 2013-01-20 at 13:44 +0530, Ajay Garg wrote:
> Any ideas, please? :)
>
>
Ok, how about a couple of questions. What version of erlang is
installed? Did you create the *online* group?
Jerry
> On Fri, Jan 18, 2013 at 2:03 PM, Ajay Garg <ajay at activitycentral.com>
> wrote:
> Hi all.
>
> I have been trying to get buddies visible in the
> neighborhood-view, when XOs are communicating via
> ejabberd-server (via telepathy-gabble).
> Following are the two cases ::
>
>
> i)
> Client :: Sugar (Fedora-18 based)
> Server :: ejabberd on CentOS (XS-0.7)
>
> In this case, I am able to register the users on the server;
> and receive the "members changed signals" (as per the
> attached PASS_telepathy_gabble.log).
> Of course, the buddies are able to see each other too :)
>
>
> ii)
> Client :: Sugar (Fedora-18 based)
> Server :: ejabberd on Debian-6
>
> In this case, I am able to register the users on the server;
> but DO NOT receive the "members changed signals" (as per the
> attached FAIL_telepathy_gabble.log).
> Hence, buddies are not able to see each other.
>
>
>
> Some additional notes ::
> ==================
>
> a)
> Both servers are running with the same "ejabberd.cfg" file,
> as attached.
>
>
> b)
> On CentOS, following are effective, before starting
> ejabberd ::
>
> setenforce 0
> service iptables
> stop
> service ip6tables
> stop
>
>
> On Debian-6, following are effective, before starting
> ejabberd ::
>
> setenforce 0
> iptables -F
> iptables -X
> iptables -t nat -F
> iptables -t nat
> -X
> iptables -t mangle
> -F
> iptables -t mangle
> -X
> ip6tables -F
> ip6tables -X
> ip6tables -t mangle
> -F
> ip6tables -t mangle
> -X
>
>
>
> c)
> Both servers are running the same ejabberd codebase (the
> patched version of 2.1.10), containing all the patches in
> http://dev.laptop.org/xs/repos/stable/olpc/xs-0.7/source/ejabberd-2.1.10-1.el6.olpc1.src.rpm (Thanks again Jerry).
>
> More importantly, the issue of
> https://support.process-one.net/browse/EJAB-1533 is fixed via
> the "persist-all-pubsub.patch" (Thanks Daniel Drake).
> The buddy-properties are persisted, as seen via "ejabberdctl
> dump db.txt" (as seen on both CentOS and Debian).
>
>
> ################################################################################################################
> However, very surprisingly, the "__get_members_ready_cb" still
> receives NOTHING in the failure-debian case (see
> FAIL-shell.log),
>
> but receives the buddy-properties in pass-CentOScase (see
> PASS-shell.log).
> #################################################################################################################
>
>
>
> d)
> Most importantly, on both the servers, the "Send XML Stream"
> log is seen in "/var/log/ejabberd/ejabberd.log"; however, the
> members-changed signal is seen only in the CentOS-ejabberd
> case, but not in Debian-6-ejabberd case.
>
>
> For brevity, I am also pasting the "Send XML Stream" message
> (which happens to be the same on both the servers) ::
> ======================================================================================
>
>
> =INFO REPORT==== 2013-01-17 23:46:45 ===
> D(<0.360.0>:ejabberd_c2s:1561) : Send XML on stream =
> <<"<message
> from='5ccefd7c37c12600296e0505ad3be79c0476e06e at schoolserver.mazaq.org' to='5ccefd7c37c12600296e0505ad3be79c0476e06e at schoolserver.mazaq.org/sugar' type='headline'><event xmlns='http://jabber.org/protocol/pubsub#event'><items node='http://laptop.org/xmpp/buddy-properties'><item id='54E6D08D69C42'><properties xmlns='http://laptop.org/xmpp/buddy-properties'><property name='color' type='str'>#00A0FF,#9A5200</property><property name='key' type='bytes'>QUFBQUIzTnphQzFrYzNNQUFBQ0JBTHl2Ly9HUGJ2V3QwaXNQeUJWWmU4aUZ1aDlRUHFaVDQrd0tzOUMwek9kc0g5QlpqVVV4QVNMeEVuUE9lMnJNSjlZL2EvTTBEZmw2SnhKdDEyWTZMdm5JQlV6Rkd1YjBuS1pEQTlpT1BkK1JVMGZEUUxLd1czV3RiNGE5S0s4ZkZsYWtNT092QW5ZTG9VZExjN0ZQZmxjMUFnVDlLU0wwdEptZ1lEekVKTi9UQUFBQUZRQ0hzU093TThtcEFtS0k5U1Y3azNhMzVVR2xMUUFBQUlCWTFQU0ExZUhWN2pFYUZERFZSVHBiQVdhYWVmQ3JCVVJLUFVxam56bDIxR09PQ0xRWWVRR0lYNnpOYlArSUlFaW1QN0E0b3o4cmFyblNIYnNiQjdtNGE3amtWbUpTdTBVYW53TUVWS3VBQnk2bE5oVXVremM2THRiMnJhaXJFcmNQNENzcGNoRk1KOTByWTFXLzVjNWlabXR2NUpFbjBnRmVLWnlibjhIVGJ3QUFBSUVBcXlWdzMzM09GSU83TmRsY1lIVzZoZzVHY0hTUXJBblZmdWY3QWx0L1Z6bHp5cHRQTnN3NlRxN1RIWVcwOEEvVEUzUzd2dlU5WFNHVkhkY3R3Wm9yNmt3elRDYk83WSttUU1pdzViRmc4ZUNYeTcvZENPbHMzUmVhRmc3QVlobDlRR3hjS1ppUmNGRnJwOHVKVlIyQTl5YzZPSEt4Mjh4UmtBRjlkOUN5TDljPQ==</property></properties></item></items></event><addresses xmlns='http://jabber.org/protocol/address'><address type='replyto' jid='5ccefd7c37c12600296e0505ad3be79c0476e06e at schoolserver.mazaq.org/sugar'/></addresses></message>">>
>
>
> It seems that on Debian, the server is sending messages that
> SHOULD trigger the "__get_members_ready_cb" signal (with
> non-empty arguments), but somehow this doesn't happen (in
> Debian case, that is). :(
>
>
>
>
> So. has anyone tried ejabberd on Debian, and faced similar
> issues?
> Is it that some additional configuration is needed on Debian;
> or ejabberd truly doesn't talk gabble well on Debian?
>
>
> I will be grateful for any pointers on this; please let me
> know if you need me to do any additional tests on my side.
>
>
>
> Regards,
>
> Ajay Garg
> Dextrose Developer
> Activity Central: http://activitycentral.com
>
>
>
> --
> Regards,
>
> Ajay Garg
> Dextrose Developer
> Activity Central: http://activitycentral.com
> _______________________________________________
> Devel mailing list
> Devel at lists.laptop.org
> http://lists.laptop.org/listinfo/devel
More information about the Devel
mailing list