Geek Answers Handbook

How to debug ejabberd crash report?

I am new to ejabberd, I compiled and started the server, but I get this error during startup. The magazine is not very useful, but maybe someone knows how to parse it better than me. Any insight would be great.

=CRASH REPORT==== 17-May-2011::16:30:19 === crasher: initial call: application_master:init/4 pid: <0.39.0> registered_name: [] exception exit: {bad_return, {{ejabberd_app,start,[normal,[]]}, {stringprep,nameprep,exmpp_not_started,"localhost"}}} in function application_master:init/4 ancestors: [<0.38.0>] messages: [] links: [<0.38.0>,<0.40.0>,<0.6.0>] dictionary: [] trap_exit: true status: running heap_size: 610 stack_size: 24 reductions: 132 neighbours: =INFO REPORT==== 17-May-2011::16:30:19 === application: ejabberd exited: {bad_return,{{ejabberd_app,start,[normal,[]]}, {stringprep,nameprep,exmpp_not_started,"localhost"}}} type: temporary
+4
source share
2 answers

Erlang Crashdump Viewer (slightly) is better than the original dump file. You can run it from the console: erl -s crashdump_viewer , then open your browser to http: // localhost: 8888 / and click CrashDumpViewer at the top of the page.

However, looking at your dump, it looks like the exmpp application did not start. If you compiled from source, there are dependencies that may be required for exmpp. What do you see if you try exmpp:start(). from erl console?

+5
source

The problem was that I was using an older version of erlang I, upgraded to R14B02 (erts-5.8.3), and everything was fine.

0
source

More articles:


All Articles