Crmgo Blog

ejabberd troubleshooting

ejabberd troubleshooting

The problem is in the log: Error reading Mnesia database spool files: The Mnesia database couldn't read the spool file for the table 'config'. ejabberd needs read and write access in the directory: /var/lib/ejabberd/spool Maybe the problem is a change in the…

ejabberd troubleshooting

Problem in the log:

Error reading Mnesia database spool files: The Mnesia database couldn't read the spool file for the table 'config'. ejabberd needs read and write access in the directory: /var/lib/ejabberd/spool Maybe the problem is a change in the computer hostname, or a change in the Erlang node name, which is currently: ejabberd@asterisk Check the ejabberd guide for details about changing the computer hostname or Erlang node name.

 

Solution:

  1. Stop ejabberd.
/etc/init.d/ejabberd stop

 

2. Kill processes: beam, beam.smp, epmd

killall ejabberd

killall beam

killall beam.smp

killall epmd

 

3. Remove the files in /var/lib/ejabberd (Create a backup copy of this folder just in case)

rm -rf /var/lib/ejabberd/*

rm -rf /var/lib/ejabberd/.erlang.cookie

 

4. Try to start ejabberd.

/etc/init.d/ejabberd start

 

Note: This post may be AI-assisted and then human-edited. Editorial responsibility: Dmytro Lomaka, Kaltenkirchen.