[ejabberd] Issues with mod_muc_log

Augustine Ike augustineike at gmail.com
Fri Jul 31 22:01:45 MSD 2009

    You are right. I take back my last post. I sent my post before I
read yours. 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 created a user called jabberadmin since I use the same account
as the Jabber Admin and logged in as this user. I started the service
ejabberdctl start
I then registered new chat rooms and they started popping up in the
logs. I will shutdown tkabber and see what happens. For now, both seem
to work great.
Thanks a Trillion. I can focus on the documentation this weekend and
get set for the implementation next week.


On Fri, Jul 31, 2009 at 1:42 PM, Badlop<badlop at gmail.com> wrote:
> 2009/7/31 Augustine Ike <augustineike at gmail.com>:
>>     Thanks for your reply on this. I tried this entry "{logging,
>> true}" and I did not see any change.
> Ok, this setting will be used for newly created rooms.
>> I can see my conference logs in  client machine or machines I enabled this on in
>> .purple/logs/jabber/jabberadmin@<domain name>/it at conference.<domain name>.chat$
> Those logs are created by your client in your client machine. ejabberd
> is not involved in this.
>> I am using Pidgin in Linux and Windows and I have turned on :Enable
>> Logging" in the conference window.
>> There is nothing in "/var/www/muclogs".
> Those logs should be created by ejabberd, in the server machine.
> If they are not created, check ejabberd.log and sasl.log for error
> messages thay may help to determine the problem.
> Typical problems:
> * maybe the dir  "/var/www/muclogs" doesn't exist
> * maybe the system user that runs ejabberd does not have write access
> in that dir
> ---
> Badlop
> ProcessOne
> _______________________________________________
> ejabberd mailing list
> ejabberd at jabber.ru
> http://lists.jabber.ru/mailman/listinfo/ejabberd

More information about the ejabberd mailing list