HomeEvergreen: Basic System Admin FunctionsProvisioning of machinesCloning machines: Purge ejabberd (mnesia)

6.1. Cloning machines: Purge ejabberd (mnesia)

When cloning EG machines (specifically, the machines running the ejabberd process), it is important that ejabberd be purged from the system (on Debian, this is `apt-get purge ejabberd`), reinstalled, re-configured, and users' re-set up.  The ejabberd.cfg file can (usually) be retained for re-used after ejabberd reinstall.

A cloned ejabberd 'mnesia' database on the LAN can cause network communication issues on other machines - Even if only responding on localhost or 127/8.  For example, a single-server brick cloned to add capacity to a cluster can result in Jabber communication failures on both bricks - presenting as request timeouts, lost listeners, and the like.

This page was: Helpful | Not Helpful