[ejabberd] migrating to new domain/host

Mark Keisler mark at mitsein.net
Thu Sep 30 18:20:52 MSD 2010


On Thu, Sep 30, 2010 at 6:56 AM, Badlop <badlop at gmail.com> wrote:

> 2010/9/24 Mark Keisler <mark at mitsein.net>:
> > I followed the procedure at
> > http://www.process-one.net/en/ejabberd/guide_en#htoc76 for changing a
> > hostname but have found that this still leaves me high and dry for muc
> rooms
> > that existed with the old node name.  They do not shwo up under the new
> name
> > but I see them in the mnesia data file.  How would I also migrate those
> > names to the new node name?
>
> If you still have the old mnesia spool dir and you don't have an
> enormous database,
> you can try:
> 1. Install ejabberd in another machine, for example your desktop.
> 2. Copy the old mnesia spool dir.
> 3. Force ejabberd to use the old erlang node name by setting it in
> ejabberdctl.cfg
> 4. Start ejabberd, it should accept the old database.
> 5. Go to ejabberd webadmin, or use ejabberdctl to export the database
> to a text file.
> 6. Edit that text file: remove most records, keep only the muc_room ones.
> 7. In your new server, import that text file, so the old room records
> are added to the table.
> 8. Restart mod_muc or the whole ejabberd so it starts the room processes.
>
>
>
> I do still have the old spool dir, but I also have it migrated onto a new
host with a new node name.  The MUC rooms are there in the mnesia db but
ejabbered does not care because they are not in its domain.  I'll try steps
5-8 on that and see if it works.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.jabber.ru/pipermail/ejabberd/attachments/20100930/d2a00949/attachment.html>


More information about the ejabberd mailing list