ejabberd - Comments for "Cannot start ejabber after VPS host applied security patches"

Found out old NODE name was ejabberd@vps

landstatic — Wed, 08 Dec 2010 16:19:12 +0000

@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.

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.

At least I have the valuable account credential and roster data...

Thanks for replying to my original post.

Right now the nodename used

mfoss — Mon, 06 Dec 2010 17:58:12 +0000

Right now the nodename used to start ejabberd is ejabberd@lvps109-104-93-116.

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:

=INFO REPORT==== 6-Dec-2010::18:52:58 ===
I(<0.39.0>:ejabberd_app:72) : ejabberd 2.1.x is started in the node ejabberd@localhost

Once you remember the old nodename, you can for ejabberdctl to use the old one with this option in the file ejabberdctl.cfg

ERLANG_NODE=ejabberd@whateveroldnodename