Closed kmaxat closed 10 years ago
There are some incompatibility issues depending on what headers and/or binaries are available during compile with eJabberd 13.12.
So far the solution has been to remove the lines containing the ?INFO_MSG macro.
I'll leave this open until I have time to properly address the compilation with the new ejabberd version and can provide a more step by step walk through to allow the logging to stay in place.
@kmaxat ^^
Hi! I haven't actually used it, but it seems that the issue has been solved. Look: https://github.com/processone/ejabberd-contrib/issues/13 Don't worry about solving. I will do it.
this solved it for me http://chatlogs.jabber.ru/ejabberd@conference.jabber.ru/2013/11/22.html
There seems to be an issue with eJabberd 13.12. Erlang R16B03-1 (erts-5.10.4) [source] [64-bit] [smp:2:2] [async-threads:10] [kernel-poll:true] Do you have any idea how to solve that?