What version of mu-conference are you running??
I'm running an un-modified 0.7 release
On Jun 10, 2009, at 18:03 , Gavin Mogan wrote:
lets try that again to the list.
On Wed, Jun 10, 2009 at 3:02 PM, Gavin Mogan <halk...@gmail.com>
wrote:
Yea. I've tried that too.
From what I can tell (I am pasting the logs below), mu-conference is
sending stanzas that djabberd can't understand (and possibly
shouldn't need to), and sends back an error, so the data never gets
to the user.
Is there an easy way to make the logs show the complete messages?
INFO DJabberd.Connection.XML.ClientIn 1 < <iq type='get'
id='ab89a' to='conference.domain.tld'>...<query xmlns='http://jabber.org/protocol/disco#items'/
>...</iq>
INFO DJabberd.Connection.XML.ComponentIn no_id > <iq
type="get" id="ab89a" xmlns="jabber:client"
to='conference.domain.tld' from='logu...@domain.tld/Psi'>...<query
xmlns='http://jabber.org/protocol/disco#items'/>...</iq>
INFO DJabberd.Connection.XML.ClientIn 1 < <iq type='get'
id='ab8aa' to='conference.domain.tld'>...<query xmlns='http://jabber.org/protocol/disco#info'/
>...</iq>
INFO DJabberd.Connection.XML.ComponentIn no_id > <iq
type="get" id="ab8aa" xmlns="jabber:client"
to='conference.domain.tld' from='logu...@domain.tld/Psi'>...<query
xmlns='http://jabber.org/protocol/disco#info'/>...</iq>
INFO DJabberd.Connection.XML.ComponentIn no_id < <iq
type='result' id='ab89a' from='conference.domain.tld' to='logu...@domain.tld
/Psi'><query xmlns='http://jabber.org/protocol/disco#items'/></iq>
WARN DJabberd.Connection.ComponentIn no_id stream error
'unsupported-stanza-type':
INFO DJabberd.Connection.XML.ComponentIn no_id < <iq
type='result' id='ab8aa' from='conference.domain.tld' to='logu...@domain.tld
/Psi'><query xmlns='http://jabber.org/protocol/disco#info'><identity
type='text' category='conference' name='Public Chatrooms'/><feature
var='http://jabber.org/protocol/muc'/><feature var='http://jabber.org/protocol/muc#unique'/
><feature var='http://jabber.org/protocol/disco'/><feature var='jabber:iq:browse'/
><feature var='jabber:iq:register'/><feature var='jabber:iq:version'/
><feature var='jabber:iq:time'/><feature var='jabber:iq:last'/
><feature var='vcard-temp'/><feature var='urn:xmpp:ping'/></query></
iq>
WARN DJabberd.Connection.ComponentIn no_id stream error
'unsupported-stanza-type':
after that, mu-conference crashes or becomes unresponsive.
mu-conference side (with fuller packets):
MU-Conference: [conference.c:293 (con_server)] Server packet - Disco
Items Request
jcr_deliver.c:36 (deliver): queued 164 bytes : >>> <iq type='result'
id='ab89a' xmlns='jabber:client' to='logu...@airg.com/Psi'
from='conference.airg.com'><query xmlns='http://jabber.org/protocol/disco#items'/
></iq> <<<
MU-Conference: [conference.c:131 (con_server)] server packet
MU-Conference: [conference.c:261 (con_server)] Server packet - Disco
Info Request
jcr_deliver.c:36 (deliver): queued 610 bytes : >>> <iq type='result'
id='ab8aa' xmlns='jabber:client' to='logu...@airg.com/Psi'
from='conference.airg.com'><query xmlns='http://jabber.org/protocol/disco#info'
><identity category='conference' type='text' name='Public Chatrooms'/
><feature var='http://jabber.org/protocol/muc'/><feature var='http://jabber.org/protocol/muc#unique'/
><feature var='http://jabber.org/protocol/disco'/><feature var='jabber:iq:browse'/
><feature var='jabber:iq:register'/><feature var='jabber:iq:version'/
><feature v
jcr_deliver.c:93 (jcr_queue_deliver): wrote 2 packets of 774 bytes
jcr_elements.c:103 (jcr_end_element): 'stream:error' on server
stream: '<stream:error><unsupported-stanza-type xmlns='urn:ietf:param
s:xml:ns:xmpp-streams'/></stream:error>'
jcr_elements.c:115 (jcr_end_element): End of Stream from server:
'<stream:error><unsupported-stanza-type xmlns='urn:ietf:params:xml:ns:xmpp-streams'/
></stream:error>'
jcr_main_stream_error.c:56 (jcr_main_close_stream): Server stream
error, resetting
jcr_deliver.c:101 (jcr_queue_deliver): packet delivery thread exiting.
jcr_deliver.c:102 (jcr_queue_deliver): Last DvryQ Buffer=''
On Wed, Jun 10, 2009 at 11:23 AM, Edward Rudd<er...@netfor.com> wrote:
>
> On Jun 9, 2009, at 18:59 , Gavin Mogan wrote:
>
>> I'm finding that while the DJabberd MUC module works a lot better
now
>> than it did a year ago when i last tried it, I am finding it really
>> only works for basic things.
>
> [snip]
>
>> None of which seems to allow this service to show up in the service
>> discovery in either miranda or psi (nor does mu-conference seem
to get
>> any data sent from the clients)
>> Is anyone successfully using mu-conference and can share how they
get
>> it to work?
>>
>
> Here is my configuration for using DJabbered with mu-conference
>
> ChildService conference.myhost.com Public Conferencing
> <Subdomain conference>
> <Plugin DJabberd::Component::External>
> ListenAddr 127.0.0.1:5290
> Secret Conferencing
> </Plugin>
> </Subdomain>
>
> And I have mu-conference configured to listen on port 5290 on
locahost using
> the conference.myhost.com name/host.
>
> I had to do a small patch to Danga::Socket so that when I restarted
> mu-conference djabbered would re-connect.
>
>
>
>>
>> Just for the record
>>
>> Thanks,
>> Gavin
>
>
>
