Hi all.<br><br>I have been trying to get buddies visible in the neighborhood-view, when XOs are communicating via ejabberd-server (via telepathy-gabble).<br>Following are the two cases ::<br><br><br>i)<br>Client :: Sugar (Fedora-18 based) <br>
Server :: ejabberd on CentOS (XS-0.7)<br><br>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).<br>Of course, the buddies are able to see each other too :)<br>
<br><br>ii)<br>
Client :: Sugar (Fedora-18 based) <br>
Server :: ejabberd on Debian-6<br>
<br>
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).<br>Hence, buddies are not able to see each other.<br><br><br><br>Some additional notes ::<br>==================<br>
<br>a)<br>Both servers are running with the same "ejabberd.cfg" file, as attached.<br><br><br>b)<br>On CentOS, following are effective, before starting ejabberd ::<br> <br> setenforce 0<br>
service iptables stop<br> service ip6tables stop<br><br><br>On Debian-6, following are effective, before starting ejabberd ::<br><br> setenforce 0<br>
iptables -F<br> iptables -X<br> iptables -t nat -F<br> iptables -t nat -X <br>
iptables -t mangle -F<br> iptables -t mangle -X<br> ip6tables -F<br> ip6tables -X<br>
ip6tables -t mangle -F<br> ip6tables -t mangle -X<br><br><br><br>c)<br>Both servers are running the same ejabberd codebase (the patched version of 2.1.10), containing all the patches in<br>
<a href="http://dev.laptop.org/xs/repos/stable/olpc/xs-0.7/source/ejabberd-2.1.10-1.el6.olpc1.src.rpm">http://dev.laptop.org/xs/repos/stable/olpc/xs-0.7/source/ejabberd-2.1.10-1.el6.olpc1.src.rpm</a> (Thanks again Jerry).<br>
<br>More importantly, the issue of <a href="https://support.process-one.net/browse/EJAB-1533">https://support.process-one.net/browse/EJAB-1533</a> is fixed via the "persist-all-pubsub.patch" (Thanks Daniel Drake). <br>
The buddy-properties are persisted, as seen via "ejabberdctl dump db.txt" (as seen on both CentOS and Debian).<br><br><br>################################################################################################################<br>
However, very surprisingly, the "__get_members_ready_cb" still receives NOTHING in the failure-debian case (see FAIL-shell.log),<br> but receives the buddy-properties in pass-CentOScase (see PASS-shell.log).<br>
#################################################################################################################<br><br><br><br>d)<br>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.<br>
<br><br>For brevity, I am also pasting the "Send XML Stream" message (which happens to be the same on both the servers) ::<br>======================================================================================<br>
<br><br>=INFO REPORT==== 2013-01-17 23:46:45 ===<br>D(<0.360.0>:ejabberd_c2s:1561) : Send XML on stream = <<"<message from='<a href="mailto:5ccefd7c37c12600296e0505ad3be79c0476e06e@schoolserver.mazaq.org" target="_blank">5ccefd7c37c12600296e0505ad3be79c0476e06e@schoolserver.mazaq.org</a>' to='<a href="http://5ccefd7c37c12600296e0505ad3be79c0476e06e@schoolserver.mazaq.org/sugar" target="_blank">5ccefd7c37c12600296e0505ad3be79c0476e06e@schoolserver.mazaq.org/sugar</a>' type='headline'><event xmlns='<a href="http://jabber.org/protocol/pubsub#event" target="_blank">http://jabber.org/protocol/pubsub#event</a>'><items node='<a href="http://laptop.org/xmpp/buddy-properties" target="_blank">http://laptop.org/xmpp/buddy-properties</a>'><item id='54E6D08D69C42'><properties xmlns='<a href="http://laptop.org/xmpp/buddy-properties" target="_blank">http://laptop.org/xmpp/buddy-properties</a>'><property name='color' type='str'>#00A0FF,#9A5200</property><property name='key' type='bytes'>QUFBQUIzTnphQzFrYzNNQUFBQ0JBTHl2Ly9HUGJ2V3QwaXNQeUJWWmU4aUZ1aDlRUHFaVDQrd0tzOUMwek9kc0g5QlpqVVV4QVNMeEVuUE9lMnJNSjlZL2EvTTBEZmw2SnhKdDEyWTZMdm5JQlV6Rkd1YjBuS1pEQTlpT1BkK1JVMGZEUUxLd1czV3RiNGE5S0s4ZkZsYWtNT092QW5ZTG9VZExjN0ZQZmxjMUFnVDlLU0wwdEptZ1lEekVKTi9UQUFBQUZRQ0hzU093TThtcEFtS0k5U1Y3azNhMzVVR2xMUUFBQUlCWTFQU0ExZUhWN2pFYUZERFZSVHBiQVdhYWVmQ3JCVVJLUFVxam56bDIxR09PQ0xRWWVRR0lYNnpOYlArSUlFaW1QN0E0b3o4cmFyblNIYnNiQjdtNGE3amtWbUpTdTBVYW53TUVWS3VBQnk2bE5oVXVremM2THRiMnJhaXJFcmNQNENzcGNoRk1KOTByWTFXLzVjNWlabXR2NUpFbjBnRmVLWnlibjhIVGJ3QUFBSUVBcXlWdzMzM09GSU83TmRsY1lIVzZoZzVHY0hTUXJBblZmdWY3QWx0L1Z6bHp5cHRQTnN3NlRxN1RIWVcwOEEvVEUzUzd2dlU5WFNHVkhkY3R3Wm9yNmt3elRDYk83WSttUU1pdzViRmc4ZUNYeTcvZENPbHMzUmVhRmc3QVlobDlRR3hjS1ppUmNGRnJwOHVKVlIyQTl5YzZPSEt4Mjh4UmtBRjlkOUN5TDljPQ==</property></properties></item></items></event><addresses xmlns='<a href="http://jabber.org/protocol/address" target="_blank">http://jabber.org/protocol/address</a>'><address type='replyto' jid='<a href="http://5ccefd7c37c12600296e0505ad3be79c0476e06e@schoolserver.mazaq.org/sugar%27/" target="_blank">5ccefd7c37c12600296e0505ad3be79c0476e06e@schoolserver.mazaq.org/sugar'/</a>></addresses></message>">><br>
<br><br>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). :(<br>
<br><br><br>
<br>So. has anyone tried ejabberd on Debian, and faced similar issues?<br>Is it that some additional configuration is needed on Debian; or ejabberd truly doesn't talk gabble well on Debian?<br><br><br>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.<br>
<br><br><br><font face="arial, sans-serif">Regards,<br><br>Ajay Garg</font><br style="font-family:arial,sans-serif;font-size:13px;background-color:rgb(255,255,255)"><font face="arial, sans-serif">Dextrose Developer</font><br style="font-family:arial,sans-serif;font-size:13px;background-color:rgb(255,255,255)">
<span style="font-family:arial,sans-serif;font-size:13px;background-color:rgb(255,255,255)">Activity Central: </span><a href="http://activitycentral.com/" style="font-family:arial,sans-serif;font-size:13px;background-color:rgb(255,255,255)" target="_blank">http://activitycentral.com</a>