It is often wise to enable extra logging feature to be able to trace back the cause of potential problems in ejabberd.
This is done by enabling SASL logs in Erlang, by following the given steps:
-
Create a sys.config file containing the SASL parameters:
[{sasl, [{sasl_error_logger, false}, {error_logger_mf_dir, "logs/sasl"}, {error_logger_mf_maxfiles, 10}, {error_logger_mf_maxbytes, 1000000}]}].
-
Launch ejabberd by refering to this Erlang system config file from the erl command line:
erl -config sys -boot start_sasl -s ejabberd
The SASL logs are stored in binary format and can be browsed with the Erlang report browser (rb).
Ensure that the logs/sasl is configured to point to a correct, existing directory.