Databases
StackOverflow2013
Postsdbo
POErlang crashes (must be ejabberd): Why and how to debug the logfile?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POErlang crashes (must be ejabberd): Why and how to debug the logfile?
    primarykey
    data
    text
    <p>Everyday I have a new Erlang crash report on my server. As ejabberd is the only Erlang-thing I use, this must be the cause of the crash.</p> <p>The logfile (<code>erl_crash.dump</code>) has almost 9,000 lines so I have no idea how to debug that. But when I searched for "ejabberd" in that logfile, there were 5 occurrences - and every single occurrence was something related to "ejabberdctl".</p> <p>I'm addressing ejabberdctl via PHP script (<code>exec()</code>) to programatially create users. Could that be the cause for the crash (somehow)?</p> <p>In <code>/var/log/ejabberd</code> directory, I've found some errors in <code>erlang.log</code> and <code>ejabberd.log</code>. But I don't really know how to resolve them:</p> <pre><code>=ERROR REPORT==== Mnesia('ejabberd@MYHOST'): ** ERROR ** (core dumped to file: "/var/lib/ejabberd/MnesiaCore.ejabberd@MYHOST_...") ** FATAL ** mnesia_monitor crashed: {badarg, [{ets,lookup, [mnesia_decision, 'ejabberdctl@MYHOST']}, {mnesia_recover,has_mnesia_down,1}, {mnesia_monitor,handle_info,2}, {gen_server,handle_msg,5}, {proc_lib,init_p_do_apply,3}]} state: {state, &lt;0.65.0&gt;, [], [], true, [], undefined, []} =ERROR REPORT==== Mnesia('ejabberd@MYHOST'): ** WARNING ** Mnesia is overloaded: {dump_log, time_threshold} =CRASH REPORT==== crasher: initial call: ejabberd_listener:init/3 pid: &lt;0.366.0&gt; registered_name: [] exception exit: {timeout, {gen_server,call, [&lt;0.682.0&gt;,{become_controller,&lt;0.685.0&gt;}]}} in function gen_server:call/2 in call from ejabberd_listener:accept/3 ancestors: [ejabberd_listeners,ejabberd_sup,&lt;0.39.0&gt;] messages: [{#Ref&lt;0.0.0.11304&gt;,ok}] links: [#Port&lt;0.2761&gt;,&lt;0.274.0&gt;] dictionary: [] trap_exit: false status: running heap_size: 2584 stack_size: 24 reductions: 20938 neighbours: </code></pre>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. UScaw
    1. UScaw
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POErlang crashes (must be ejabberd): Why and how to debug the logfile?
      1. UScaw
      1. VTBountyStart
    2. VO
      singulars
      1. POErlang crashes (must be ejabberd): Why and how to debug the logfile?
      1. USAmiramix
      1. VTFavorite
    3. VO
      singulars
      1. POErlang crashes (must be ejabberd): Why and how to debug the logfile?
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThe "slogan" says that the `kernel` application was shut down, but doesn't tell us why. Are there any crash reports in `ejabberd.log` or `sasl.log`? (At least that was what the log files were called when I last ran ejabberd.)
      singulars
      1. POErlang crashes (must be ejabberd): Why and how to debug the logfile?
      1. USlegoscia
    2. CO@legoscia: Thank you! I've added details from that log to the question.
      singulars
      1. POErlang crashes (must be ejabberd): Why and how to debug the logfile?
      1. UScaw
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload