[ejabberd] another mod_service_log question

Daniel Dormont dan at greywallsoftware.com
Tue Mar 22 18:53:33 MSK 2011


I misspoke a bit. Actually one of the packets is sent to the external
component: the unavailable presence from userA to userB. I missed it in my
initial post due to a setup problem. Sorry about that.

But the one I'd like to see is the one from userA to
room1 at conference.mydomain. That packet is definitely not arriving.
Unfortunately I'm having a bit of a hard time reading the log because it
looks like there are multiple packets in transit at once but roughly
speaking it seems to be this:

=INFO REPORT==== 2011-03-22 11:42:08 ===
D(<0.884.0>:ejabberd_router:313) : route
from {jid,"userA","mydomain","jwchat","userA","mydomain","jwchat"}
to {jid,"room1","conference.mydomain","userA","room1",
                "conference.mydomain","userA"}
packet {xmlelement,"presence",[{"type","unavailable"}],[]}

=INFO REPORT==== 2011-03-22 11:42:08 ===
D(<0.332.0>:mod_muc:507) : MUC: send to process <0.340.0>


=INFO REPORT==== 2011-03-22 11:42:08 ===
D(<0.340.0>:ejabberd_router:313) : route
from {jid,"room1","conference.mydomain","userA","room1",
                  "conference.mydomain","userA"}
to {jid,"userA","mydomain","jwchat","userA","mydomain","jwchat"}
packet {xmlelement,"presence",
                   [{"type","unavailable"}],
                   [{xmlelement,"x",
                        [{"xmlns","http://jabber.org/protocol/muc#user"}],
                        [{xmlelement,"item",
                             [{"affiliation","owner"},{"role","none"}],
                             []}]}]}


=INFO REPORT==== 2011-03-22 11:42:08 ===
D(<0.340.0>:ejabberd_local:286) : local route
from {jid,"room1","conference.mydomain","userA","room1",
                  "conference.mydomain","userA"}
to {jid,"userA","mydomain","jwchat","userA","mydomain","jwchat"}
packet {xmlelement,"presence",
                           [{"type","unavailable"}],
                           [{xmlelement,[...],...}]}


=INFO REPORT==== 2011-03-22 11:42:08 ===
D(<0.340.0>:ejabberd_sm:410) : session manager
from {jid,"room1","conference.mydomain","userA","room1",
                  "conference.mydomain","userA"}
to {jid,"userA","mydomain","jwchat","userA","mydomain","jwchat"}
packet {xmlelement,"presence",
                           [{"type","unavailable"}],
                           [{xmlelement,[...],...}]}


=INFO REPORT==== 2011-03-22 11:42:08 ===
D(<0.340.0>:ejabberd_sm:504) : packet droped

I understand that once the room tries to send the packet back to the user,
that will get dropped and not logged. That's fine. But the very first packet
in my snippet above - the one *from* the user *to* the room - shouldn't that
be logged?

thanks,
Dan

On Tue, Mar 22, 2011 at 12:43 AM, Daniel Dormont
<dan at greywallsoftware.com>wrote:

> Hi folks,
>
> I'm continuing to explore mod_service_log and I noticed a behavior that I
> would like to understand or at least confirm whether it's expected or not:
>
> Suppose that I have userA at mydomain a MUC room on
> room1 at conference.mydomain. Suppose further that userA is connected using
> http_bind but then the user's session times out. I see the following in my
> server log. Also note that userA has userB on its roster and userB is
> currently online.
>
> - a session timeout from http_bind
> - a presence packet from userA to userB with type "unavailable"
> - a presence packet from userA to userA with type "unavailable"
> - a presence packet from userA to room1 at conference.mydomain with type
> "unavailable"
> - a presence packet from room1 at conference.mydomain to userA with type
> "unavailable"
>
> Yet, it appears that none of these packets reach the external component
> configured in mod_service_log. Is this expected, and if so, can someone
> explain why?
>
> thanks,
> Dan
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.jabber.ru/pipermail/ejabberd/attachments/20110322/6a7bcf08/attachment.html>


More information about the ejabberd mailing list