ejabberd - Comments for "Ejabberd not accepting compression after SASL"

Generally yes, it is possible

badlop — Wed, 24 Feb 2016 12:43:46 +0000

Generally yes, it is possible to compile one file, copy it and restart ejabberd.

In your case, the problem is that ejabberd was compiled with lager instead of p1_logger, and you compiled ejabberd_c2s with p1_logger instead of lager. Try compiling again, but when calling ./configure, provide some option to disable logger or to enable lager (I guess there is some option over there).

By the way, 16.02 is expected to be released in a few days, just in case you can't solve the compiling problem.

thank you badlop. can I

nets — Tue, 23 Feb 2016 03:56:27 +0000

thank you badlop.
can I compile ejabberd_c2s.erl separate and use it in ejabberd-16.01-linux-x86_64-install. I means, copy compiled ejabberd_c2s.erl in /opt/ejabberd-16.01/lib/ejabberd-16.01/ebin/ ?
I did that but when my clinet can not connect and it returns this error.

2016-02-22 10:13:07.658 [error] <0.1703.0> CRASH REPORT Process <0.1703.0> with 0 neighbours exited with reason: call to undefined function p1_logger:debug_msg(ejabberd_c2s, 1847, "Send XML on stream = ~p", [<<"<?xml version='1.0'?><stream:stream xmlns='jabber:client' xmlns:stream='http://etherx.jabber....">>]) in p1_fsm:terminate/8 line 760

This feature was recently

badlop — Mon, 22 Feb 2016 15:49:32 +0000

This feature was recently committed to ejabberd source code, see https://github.com/processone/ejabberd/commit/5b4aefbacd260d86e8e78a7d66...