On Tue, Sep 18, 2001 at 10:30:17AM -0500, Shane Breland wrote: > Tue Sep 18 09:58:05 2001 io_select.c:339 io_main checking sockets ... > Tue Sep 18 09:58:05 2001 deliver.c:472 DELIVER 4:192.0.0.14 <route > to='[EMAIL PROTECTED]/81931C8' from='12@c2s/819B398'><iq > id='jabberim:prefs3293' type='get'><query > xmlns='jabber:iq:private'><jabberIM > xmlns='jabberim:prefs'/></query></iq></route> > Tue Sep 18 09:58:05 2001 deliver.c:344 delivering to instance 'sessions' > Tue Sep 18 09:58:05 2001 deliver.c:84 (8080488)incoming packet <route > to='[EMAIL PROTECTED]/81931C8' from='12@c2s/819B398'><iq > id='jabberim:prefs3293' type='get'><query > xmlns='jabber:iq:private'><jabberIM > xmlns='jabberim:prefs'/></query></iq></route> > Tue Sep 18 09:58:05 2001 users.c:147 > js_user([EMAIL PROTECTED]/81931C8,80EE980) > Tue Sep 18 09:58:05 2001 mtq 80EF2B0 entering from pth > Tue Sep 18 09:58:05 2001 mtq 80EF2B0 queue call 8197820 > Tue Sep 18 09:58:05 2001 sessions.c:290 THREAD:SESSION:FROM received a > packet! > Tue Sep 18 09:58:05 2001 modules.c:124 mapi_call 1 > Tue Sep 18 09:58:05 2001 modules.c:147 MAPI 81934D8 > Tue Sep 18 09:58:05 2001 modules.c:147 MAPI 81934E8 > Tue Sep 18 09:58:05 2001 modules.c:147 MAPI 8193508 > Tue Sep 18 09:58:05 2001 modules.c:147 MAPI 8193530 > Tue Sep 18 09:58:05 2001 modules.c:147 MAPI 8193540 > Tue Sep 18 09:58:05 2001 modules.c:163 mapi_call returning unhandled > Tue Sep 18 09:58:05 2001 deliver.c:262 > deliver(to[192.0.0.14],from[[EMAIL PROTECTED]/Work],type[4],packet[<iq > id='jabberim:prefs3293' type='get' from='[EMAIL PROTECTED]/Work' > to='192.0.0.14'><query xmlns='jabber:iq:private'><jabberIM > xmlns='jabberim:prefs'/></query></iq>]) Aha, this is very interesting The IQ-get comes in, and the JSM modules are called in turn (the "MAPI" lines). However, note the "returning unhandled" - no module was found that is willing to handle the query in the iq:private namespace. Normally, the mod_xml module should kick in here to handle the request, but it doesn't. I note from your jabber.xml below that you do have the mod_xml module specified in the load of JSM, so I'm a little surprised. This jabber.xml file matches what's in use with the currently running jabberd? Do you still have the first hundred or so lines of output from the debug log? This will show us if the mod_xml module was loaded correctly. In any case, it seems quite evident from this section of the debug that the query isn't being handled by the JSM and so is being re-tried by the delivery mechanism with the JID of the server itself. This is what I meant in my previous post about the oddness of the reply having a from attribute: SENT: <iq id="jabberim:prefs5009" type="get"><query xmlns="jabber:iq:private"><jabberIM xmlns="jabberim:prefs"/></query></iq> RECV: <iq id='jabberim:prefs5009' type='error' from='192.0.0.14' to='[EMAIL PROTECTED]/Work'><query xmlns='jabber:iq:private'><jabberIM xmlns='jabberim:prefs'/></query><error code='404'>Not Found</error></iq> Of course, this isn't going to work either, so you get the error. So, there doesn't seem to be a mod_xml module ready to handle the query. Can you point to the debug log to show me that mod_xml is loading? Secondly, what version of the server are you running? I noticed some 'odd' lines in the debug log ... io_select.c lines, for example... Cheers dj _______________________________________________ jdev mailing list [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev
