Open aaronbrashears opened 14 years ago
Hi Aaron,
Thank you for you feedback. Yes, modular_muc is unfortunately not compatible with mod_muc_log.
The code is a bit abandoned, but you can find a more recent version here : http://github.com/cstar/ejabberd/tree/cloud/src/mod_muc/
It is still not compatible with modular_muc, but the code is better !
Ok, good to know this is a known incompatibility. I had figured the mod_muc_log bundled with modular_muc would pick up the new log parameters that appear to be used.
Yeah, sorry about that. I had a plan to port it to modular_muc, but never got around it.
Hi there. I pulled the master branch, built according to instructions and installed it into my instance of ejabberd. I reloaded the modules from the webadmin and got similar results so I restarted ejabberd to make sure. It appears that with mod_muc and mod_muc_log disagree on the communication protocol. I am using ejabberd 2.1.3 on erlang R13b with mod_muc and mod_muc_log configured configured as:
The outdir
/var/log/ejabberd/muclogs
is chown ejabberd:adm, owner and group writable, and ejabberd runs as the ejabberd user.When the room is created, there is no problem.
Then, when logging is enabled, we see the first error in ejabberd.log:
And upon saying something ('test'), we get the following error: