Looking for ejabberd docs?

To access the most up-to-date ejabberd documentation, please visit docs.ejabberd.im »

mod_muc_log : can't get any log

Submitted by fcharrier on Thu, 2008-04-24 12:58

Hi,

I hope this message is in the right place.
I installed ejabberd on a debian, version 2.0.0, and everything works fine.
I'm trying to activate the mod_muc_log, but I can't get any log file.

In my ejabberd.cfg, I wrote :

%% All users are allowed to use MUC service:
{access, muc, [{allow, all}]}.

{mod_muc_log, [
{access_log, muc},
{cssfile, false},
{dirtype, subdirs},
{outdir, "/var/www/muclogs"},
{timezone, local}
]},

I check in /var/www, but I can't get any muclogs directory. I created it, but can't get any file...
Of course I checked Linux rights, and I created chatrooms.

Any help will be really appreciated, and sorry for my poor english

Check log files. Enable the option in the chatroom

Submitted by mfoss on Sun, 2008-05-04 16:14.

I guess in your ejabberd.cfg you added mod_muc_log inside of the 'modules' section, like this:

{modules, [
  ...
  {mod_muc_log, [
    {access_log, muc},
    {cssfile, false},
    {dirtype, subdirs},
    {outdir, "/var/www/muclogs"},
    {timezone, local}
  ]},
  ...
]}.

You should check ejabberd log files (ejabberd.log and sasl.log) because maybe they report some error during ejabberd start, or when a user chats in a room and the server attempts to create the log file.

Note that, by default, chatrooms are not logged. You must enable the option in the chatroom. For that you can use a Jabber client that supports MUC (like Psi, Gajim or Tkabber).

It is also possible to define that logging for new chatrooms is enabled by default. Read the ejabberd Guide for more on this possibility.

same problem

Submitted by edwindew on Fri, 2009-07-17 07:21.

I am also tried this, but not creating chat log file. There is no error file in ejabberd.log and sasl.log file. Could you please tell me the steps to enable the mod_muc_log. i refered this http://www.process-one.net/en/ejabberd/guide_en#htoc45

The HTML file and the

Submitted by mfoss on Wed, 2009-07-22 22:26.

The HTML file and the directories are created by ejabberd only when a room is configured to log messages, and somebody chats in that room.

Also remember this:
"Note that, by default, chatrooms are not logged. You must enable the option in the chatroom. For that you can use a Jabber client that supports MUC (like Psi, Gajim or Tkabber)."

mod_muc_log issues

Submitted by augustineike on Fri, 2009-07-31 07:57.

Hi,
I think I agree with this user. There has to be a clearer explanation for this. Enabling chatroom logging from a muc supported client has worked for me but it logs this information on the client system. One would think that that "{outdir, "/var/www/muclogs"}," directs the logs to that location but it has not worked for me.
Am I missing something here? See my mod_muc_log section below

{modules,
[
....
{mod_muc_log,[
{access_log, muc_admin},
{allow_room_log, true},
{outdir, "/var/www/muclogs"},
{dirtype, plain},
{timezone, universal},
{top_link, {"http://www.jabber.ru/", "Jabber.ru"}}
]},
....
]},

This is one of the deal makers or breakers in adopting this in our office. If ejabberd can't log chatrooms, conferences etc to "outdir" We will move to something else.
Any help, assistance or direction will be appreciated.

Thanks
Augustine

> If ejabberd can't log

Submitted by mfoss on Mon, 2009-08-03 10:37.

> If ejabberd can't log chatrooms, conferences etc to "outdir" We will move to something else.

The author of that ultimatum later said in a thread in the mailing list:

> The root cause of the problem seems to be that the system user that runs ejabberd does not have write access in that dir.

I have configured in my

Submitted by karthikeyan on Wed, 2013-09-18 13:22.

I have configured in my personal computer. its working fine.

Same configureation done in my server, it's not working.

Need help

anybody help for this

Submitted by karthikeyan on Wed, 2013-09-18 13:18.

anybody help for this topic.