ejabberd - Comments for "Can not start ejabberd 2.0.5"

Working now

sarumont — Tue, 30 Jun 2009 17:45:34 +0000

Installed erlang r12b5, and it works. I did end up having to change my LDAP config (ldap_attrs -> ldap_uids), so I re-installed r13b1. That works, as well. I guess the above ASN1 "bug" is a red herring. Thanks for the help!

No logger error now...

sarumont — Tue, 30 Jun 2009 15:31:09 +0000

Tried trunk, and ejabberd starts successfully - thanks. Now, though, I get the following error:

=ERROR REPORT==== 2009-06-30 10:20:29 ===
Error in process <0.1294.0> on node 'ejabberd@localhost' with exit value: {badarg,[{erlang,register,[asn1_driver_owner,<0.1294.0>]},{asn1rt_driver_handler,init,2}]}

By my reckoning, this is related to LDAP (there is one of these errors for every attempted connection). It also appears as if the bug/issue is in erlang. I'm going to see about reverting my erlang to see if that helps. If anyone has seen this error before, that would be helpful, too.

Thanks!

Strange error, works for me. Try ejabberd trunk SVN

mfoss — Tue, 30 Jun 2009 14:13:26 +0000

I applied the patch to ejabberd 2.0.5, then compiled and installed. It starts correctly. I use Debian unstable.

Your error message probably means that the file ejabberd_logger.beam was not found.

If you can't solve your problem in 2.0.5, you can get ejabberd trunk SVN, which includes the patch already. Maybe that one compiles and starts correctly.

Same problem - patch not working

sarumont — Mon, 29 Jun 2009 01:25:05 +0000

I had the same problem with ejabberd starting on FreeBSD 7.2 w/ erlang r13b01. I've applied the dynamic compile patch, and now I see the following error on start:

=INFO REPORT==== 28-Jun-2009::20:20:54 ===
    application: ejabberd
    exited: {bad_return,
                {{ejabberd_app,start,[normal,[]]},
                 {'EXIT',
                     {undef,
                         [{ejabberd_logger,critical_msg,
                              [ejabberd_loglevel,56,
                               "Error compiling logger (~p): ~p~n",
                               [error,undef]]},
                          {ejabberd_app,start,2},
                          {application_master,start_it_old,4}]}}}}
    type: temporary

Any ideas?

Patch available

mfoss — Sat, 02 May 2009 10:35:19 +0000

lazypiggy wrote:

Erlang R13B and it seems well. I also compile ejabberd 2.0.5 from source code.

You can apply dynamic_compile_loglevel.patch to ejabberd source files.

Erlang R13B issue

Tim Spriggs — Sat, 02 May 2009 10:01:01 +0000

I talked with johnny in the ejabberd MUC and he said it's an erlang issue. Reverting to 12B-5 should fix this problem.

For anyone interested in diving into the issue, it appears to be a problem while compiling the module-embedded-in-a-string inside of ejabberd_loglevel.erl.