https://www.ejabberd.im/node/3621 en https://www.ejabberd.im/node/3621#comment-54572 <p>&gt; The users page in the webfrontend has become unusable, it is completely empty.</p> <p>Can users login correctly: do they have their contacts, vcards, etc? If so, then maybe it isn't worth the effort to investigate that further, and better keep it as it is now.</p> <p>Maybe your original problem is caused by a change in the erlang node name. See:<br /> <noindex><a href="http://svn.process-one.net/ejabberd/trunk/doc/guide.html#nodename" title="http://svn.process-one.net/ejabberd/trunk/doc/guide.html#nodename" rel="nofollow" >http://svn.process-one.net/ejabberd/trunk/doc/guide.html#nodename</a></noindex><br /> <noindex><a href="http://svn.process-one.net/ejabberd/trunk/doc/guide.html#changeerlangnodename" title="http://svn.process-one.net/ejabberd/trunk/doc/guide.html#changeerlangnodename" rel="nofollow" >http://svn.process-one.net/ejabberd/trunk/doc/guide.html#changeerlangnod...</a></noindex></p> <p>If that's the case, a solution could be:</p> <ol> <li>What is the new node name? Start ejabberd with empty DB and you will see it:<br /> <pre>=PROGRESS REPORT==== 24-Aug-2009::14:02:57 === application: ejabberd started_at: ejabberd@localhost </pre></li><li>What is the old node name? Maybe if you can find old logs, you can find that information. </li><li>Are both node names identical? I imagine no. </li><li>In that case, put back the old database and let's attempt to start ejabberd with it. </li><li>Edit the script that starts ejabberd. It will have a line similar to: erl -noinput -detached -sname aaa@bbb ... </li><li>Replace aaa@bbb with the old node name. </li><li>Start ejabberd. Now mnesia should start correctly. </li></ol> Mon, 24 Aug 2009 14:03:18 +0000 mfoss comment 54572 at https://www.ejabberd.im https://www.ejabberd.im/node/3621#comment-54561 <p>Ok, I came a step forward by making a backup copy of /var/lib/ejabberd and then deleting all files in that directory. Then I restarted ejabberd and it recreated most of the files and did not crash on start any more.</p> <p>Now I went along and copied all the old configs back file-by-file and restarted ejabberd every time. This way I found out that the file "schema.DAT" was the cause for the crash above. My life would have been a lot simpler in the last hours if ejabberd had proper log reporting.</p> <p>Anyway I have a running ejabberd now - BUT:<br /> The users page in the webfrontend has become unusable, it is completely empty. I presume this would go back to normal if I could manage to fix schema.DAT and put it back in place.</p> <p>Can anyone give me hints on the file format and what I could do about it? Or any other way to get my user table back into the web frontend?</p> Fri, 21 Aug 2009 10:23:57 +0000 bil_ton comment 54561 at https://www.ejabberd.im