ejabberd - Comments for "mod_logxml - Log XMPP Packets to XML File"

Cluster

AdamLC — Fri, 16 Nov 2012 16:12:46 +0000

Anyone have a problem getting this working for ejabberd setups that are clustered?

It seems to work before I setup ejabberd in a cluster. There aren't any errors in the logs and the log file directory is completely empty. I am logging message stanzas (or trying to!)

perl script to parse

hellman — Tue, 07 Aug 2012 06:28:00 +0000

Here is simple perl script to parse logxml files. HTML based on xmpp.xsl posted below.

#!/usr/bin/perl

use strict;
use XML::Simple;
use CGI qw(param);


my $str;
open(A,"< ej.xml");
while(<A>) { $str .= $_; }
close(A);

$str .= "<log>";

my $xml = XMLin($str);


print "Content-Type: text/html\r\n\r\n";

print qq|
<html>
        <head>
                <style>
                        body {
                        margin: 10px; 
                        font-family: Verdana, Arial, Helvetica, sans-serif; 
                        font-size: 10pt; 
                        }
                        td {
                        font-family: Verdana, Arial, Helvetica, sans-serif;
                        font-size: 10pt; 
                        }
                        p {
                        color: blue;
                        }
                        td.head_right {
                        background-color: #f0f0f0; 
                        padding: 0px 3px 0px 3px; 
                        font-size: 8pt; 
                        }
                        td.head_left {
                        width: 50px; 
                        background-color: #e0e0e0; 
                        padding: 0px 3px 0px 3px; 
                        font-weight: bold; 
                        font-size: 8pt;
                        }
                        td.header {
                        border: solid 1px silver;
                        }
                        td.message {
                        padding: 3px; 
                        border: solid 1px silver;
                        }
                <style>
        <head>
        <body>
                <table align="center" width="100%" cellspacing="0" cellpadding="0" style="border: solid 1px silver; border-collapse: collapse">

|;

my $ex = param('exclude');

foreach my $packet (@{$xml->{packet}}) {
        if ($packet->{'or'} eq 'send' && $packet->{'message'}->{'body'}) {
        if ($packet->{'ljid'} =~ /$ex/ || $packet->{'message'}->{'to'} =~ /$ex/) { next; }
        if (!param('otr') && $packet->{'message'}->{'body'} =~ /\?OTR/g) { next; }
        print qq|
                <tr><td class="header">
                                                        <table border="0" width="100%" cellspacing="0" cellpadding="0">
                                                                <tr>
                                                                        <td class="head_left">ts: <td>
                                                                        <td class="head_right">$packet->{'ts'}<td>
                                                                <tr>
                                                                <tr>
                                                                        <td class="head_left">from: <td>
                                                                        <td class="head_right">$packet->{'ljid'}<td>
                                                                <tr>
                                                                <tr>
                                                                        <td class="head_left">to: <td>
                                                                        <td class="head_right">$packet->{'message'}->{'to'}<td>
                                                                <tr>
                                                        <table>
                                                <td><tr>
                                                <tr>
                                                        <td class="message">$packet->{'message'}->{'body'}<td>
                                                <tr>

                        |;

        }
}

print qq|
                <table>
        <body>
<html>
|;

Configure like this

mfoss — Wed, 14 Sep 2011 14:15:25 +0000

If you configure like this, the announces are logged:

     {stanza, [message]},
     {direction, [internal]},
     {orientation, [send]},

Announce messages

badgateway — Wed, 14 Sep 2011 08:03:04 +0000

Good day for all!
The announce messages has not stores in log, but i've many users with sending announce rights.
Is there a way to get log for announce messages?
Thanks.

Fixed on 0.2.3

mfoss — Tue, 20 Mar 2007 19:41:15 +0000

Finally, fixed on version 0.2.3. Check SVN.

Bug report: time shift minus 1 hour in the log name

Pontiac — Mon, 05 Mar 2007 07:33:46 +0000

Version: 0.2.2 - 2007-02-13
Names of logs still don't respect the timezone setting. This can be confusing sometimes - for instance first packet in today's log has timestamp ts="20070305T00:00:06", but the log is named srvis03-2007-03-04-23-00-06.xml (so in this case it even has different date in its name due to the one hour difference!)
If you corrected this, the module would be nearly perfect.

closing tag added

Pontiac — Thu, 01 Mar 2007 19:31:09 +0000

Hmm, Badlop. It's weird (but pleasant at the same time :-). The mod_logxml suddenly (from 20.2.2007) started to add the <\log> closing tag. I am going to observe it. Cannot remember of any change I did in ejabberd configuration.

We'll see.

Pontiac

PS: But anyway - is it OK that the ejabberd@conference.jabberd.ru is off-line in my PSI? Is it really off-line? Or am I supposed to set it up somehow?

I have added it

Pontiac — Wed, 28 Feb 2007 18:46:40 +0000

But PSI says it is offline.

It exists, join it

mfoss — Tue, 27 Feb 2007 21:35:15 +0000

Pontiac wrote:

I have just been trying to find chatroom ejabberd at conference.jabber.ru.
So are you sure "ejabberd@conference.jabber.ru" exists?

It exists, but it isn't listed on the MUC service. Tell your Jabber client the details of the chatroom and join it, instead of searching.

No ejabberd chatroom

Pontiac — Tue, 27 Feb 2007 20:57:32 +0000

Hello Badlop,
I have just been trying to find chatroom ejabberd at conference.jabber.ru. All I have found so far is "ejabber" and this one is offline.
So are you sure "ejabberd@conference.jabber.ru" exists?

No errors

Pontiac — Tue, 13 Feb 2007 15:58:39 +0000

Hello,
I have found no error or crashes regarding mod_logxml in ejabberd.log.

I'll try the chatroom ASAP.

log filename still created using universal time

Pontiac — Tue, 13 Feb 2007 15:44:06 +0000

But the log entries are now logged correctly (timezone local). Thanks badlop for quick response.

Pontiac

New timezone option on version 0.2.2

mfoss — Tue, 13 Feb 2007 10:48:41 +0000

The timestamp was specified in universal time. I've added a new option to specify the timezone you want the timestamps to be: local (as you want) or universal (as it was previously).

Strange bug. It works for me.

mfoss — Tue, 13 Feb 2007 10:46:54 +0000

Strange bug.

It works correctly for me, and nobody else complained before. The module should add the closing tag before closing the file.

Check the ejabberd log files for any ERROR or CRASH REPORT.

If you are really interested in fixing this bug, we will have to do some live debugging. If so, join ejabberd chatroom any day between 20.00 and 22.00 GMT+1.

Bug report: time shift minus 1 hour in the log

Pontiac — Mon, 12 Feb 2007 09:50:10 +0000

Briefly: it's 10:25 on the server now and when I send a message, in the log I can read the timestamp: ts="20070212T09:25:19".
I'm in the Czech Republic and it's correctly set on our Win 2003 Server - GMT+01:00 (Prague). The timestamps in "ejabberd.log" are correct. It must be something with mod_logxml.

Have a nice day
Pontiac