You didn't specify what you

badlop — Tue, 23 Aug 2016 11:29:09 +0000

You didn't specify what you want exactly. I can imagine many options:

A) If you want to update ejabberd: stop old ejabberd, install new ejabberd, copy mnesia spool dir to new ejabberd, start new ejabberd. It will automatically update mnesia tables.

B) If you want to move old ejabberd from old machine to a new ejabberd in a new machine: stop old ejabberd, install new ejabberd in new machine, copy mnesia spool dir to new ejabberd, start new ejabberd. It will automatically update mnesia tables.

C) If you want to cluster old ejabberd from old machine with a new ejabberd in a new machine: you can't do that, as I explained. Before clustering you must have similar ejabberd versions in both machines. Two options:
C.X) install an old ejabberd in the new machine,
C.Y) or update the old ejabberd of old machine to new ejabberd Let's imagine you want to do that.... how?

How to do C.Y? First do A) to get a new ejabberd in the old machine. Then install the new ejabberd also in the new machine (but it doesn't have any database of course). Then run join_cluster in the ejabberd in the new machine, so it replicates the database from old machine.

In that case, how will I get

Janani — Fri, 19 Aug 2016 12:22:07 +0000

In that case, how will I get the data from the older version moved into the new one?

A generic response: ejabberd

badlop — Fri, 19 Aug 2016 09:59:44 +0000

A generic response: ejabberd clustering uses in part mnesia database clustering, that is, sharing mnesia database tables and their content. As new ejabberd versions may modify those tables, it isn't recommended to cluster ejabberd nodes running different ejabberd versions. Use 15.11 in all nodes, or 16.06 in all nodes, but don't mix them.

ejabberd - Comments for "Issue seen when clustering ejabberd 16.06 with 15.11"

You didn't specify what you

In that case, how will I get

A generic response: ejabberd