Replacing jabber14 with ejabberd on DH VPS


#1

Hello,

Recognizing the administrative limitations associated with DH-managed jabber14, I am in the process of replacing our XMPP server jabber14 with ejabberd on our VPS. One would imagine the process is simple:

  1. Uncheck the option to manage jabber through the DH panel
  2. Remove jabber14: sudo apt-get remove jabber
  3. Restart the VPS
  4. Install ejabberd: sudo apt-get install ejabberd

However, after installing ejabberd, it fails to start. “/etc/init.d/ejabberd start” continues to fail. “sudo netstat -lnp | grep 5222” shows no service. Does anybody have any experience with this? I’ve included some log files below:

The /var/log/ejabberd/ejabber.log file:

=INFO REPORT==== 2010-05-24 18:57:33 ===
I(<0.305.0>:mod_pubsub:152) : pubsub init “localhost” [{access_createnode,
pubsub_createnode},
{plugins,
[“default”,“pep”]}]

=INFO REPORT==== 2010-05-24 18:57:33 ===
I(<0.305.0>:mod_pubsub:207) : ** tree plugin is nodetree_default

=INFO REPORT==== 2010-05-24 18:57:33 ===
I(<0.305.0>:mod_pubsub:211) : ** init default plugin

=INFO REPORT==== 2010-05-24 18:57:33 ===
I(<0.305.0>:mod_pubsub:211) : ** init pep plugin

A portion of the /var/log/ejabberd/sasl.log file:

=PROGRESS REPORT==== 24-May-2010::18:57:33 ===
supervisor: {local,ejabberd_sup}
started: [{pid,<0.305.0>},
{name,ejabberd_mod_pubsub_localhost},
{mfa,{mod_pubsub,
start_link,
[“localhost”,
[{access_createnode,pubsub_createnode},
{plugins,[“default”,“pep”]}]]}},
{restart_type,transient},
{shutdown,1000},
{child_type,worker}]

=PROGRESS REPORT==== 24-May-2010::18:57:33 ===
application: ejabberd
started_at: ejabberd@ps25005


#2

Problem solved: http://www.ejabberd.im/node/4074