ejabberd - Comments for "Cannot start ejabber after VPS host applied security patches" https://www.ejabberd.im/node/4427 en Found out old NODE name was ejabberd@vps https://www.ejabberd.im/node/4427#comment-56863 <p>@badlop, I discovered the old node name was ejabberd@vps. Forcing ejabberd to use that name via the ERLANG_NODE settings enabled me to make a dump of the existing database via the web management console. </p> <p>I am now migrating ejabberd away from WebFusion, along with the rest of the application I host there. Attempting to restart ejabberd with the ERLANG_NODE setting leads to "......................failed" being reported on the console. </p> <p>At least I have the valuable account credential and roster data... </p> <p>Thanks for replying to my original post.</p> Wed, 08 Dec 2010 16:19:12 +0000 landstatic comment 56863 at https://www.ejabberd.im Right now the nodename used https://www.ejabberd.im/node/4427#comment-56857 <p>Right now the nodename used to start ejabberd is ejabberd@lvps109-104-93-116.</p> <p>Maybe previously it was something different. If you still have ejabberd logs from previously, they may indicate the old nodename. For example, in my logs I have:</p> <pre>=INFO REPORT==== 6-Dec-2010::18:52:58 === I(&lt;0.39.0&gt;:ejabberd_app:72) : ejabberd 2.1.x is started in the node ejabberd@localhost</pre><p> Once you remember the old nodename, you can for ejabberdctl to use the old one with this option in the file ejabberdctl.cfg</p> <pre>ERLANG_NODE=ejabberd@whateveroldnodename</pre> Mon, 06 Dec 2010 17:58:12 +0000 mfoss comment 56857 at https://www.ejabberd.im