This doesnt work at all. Doesnt change users, and doesnt modify the back end references in all places.

Garbage.

Dear folks

ejabberd ist great!

However, I cannot manage to migrate from the original hostname (derived from localhost) to a new one (mydomain.com).

Even if I follow the steps above, I still need to have the original hostname ("localhost") in the hosts attribute in the .cfg config file.

As soon, as I modify or add a host in the hosts attribute in .cfg, I receive the error message:

Failed RPC connection to the node ejabberd@xxx: nodedown

Is there a precise step-by-step description what to do to start a fresh ejabberd installation with a new @domainname?

Many thanks in advance!

Hi,

i've tried to migrate my user database to another server. i used the convert.erl script to convert the hostnames, but when trying to restore the database on the new server i get this error:

RPC failed on the node ejabberd@arwen: {'EXIT',
{{case_clause,{aborted,eacces}},
[{ejabberd_ctl,process,1},
{rpc,'-handle_call/3-fun-0-',5}]}}

anyone who could give me a hint, what the problem is?

thanks.

I USE the following command as above to backup ejabberd of the old server.
ejabberd_ctl admin@oldhost backup /tmp/ejabberd.backup"

Then use convert.erl to convert it, but i get the error as below, anyone could help me, what is wrong about it?

---------------
convert.erl as above to
Erlang (BEAM) emulator version 5.5.5 [source] [async-threads:0] [kernel-poll:false]
Eshell v5.5.5 (abort with ^G)
1> c ("convert.erl").
{ok,convert}
2> convert:change_node_name("admin@localhost","admin@ubuntutest","ejabberd.bak","ejabberd2.bak").

=ERROR REPORT==== 28-Oct-2008::17:20:17===
Error in process <0.31.0> with exit value: {undef,[{mnesia,traverse_backup,["ejabberd.bak","ejabberd2.bak",#Fun,switched]},{erl_eval,do_apply,5},{shell,exprs,6},{shell,eval_loop,3}]}

** exited: {undef,[{mnesia,traverse_backup,
["ejabberd.bak",
"ejabberd2.bak",
#Fun,
switched]},
{erl_eval,do_apply,5},
{shell,exprs,6},
{shell,eval_loop,3}]} **

Well...

Case:
=====
Restoring ejabberd mnesia database files to a new machine, because the
old machine is no longer available. Yes, this can happen.

Since ejabberd/erlang/mnesia uses the hostname to check if the database
is valid, we have to change the hostname of the new machine a couple
of time.

Here's how.

Machine names:
============
Old machine: milliways.verwijs.org
New machine: shrek.verwijs.org

Files:
======
database files: /var/lib/ejabberd
config files: /etc/ejabberd

Install Ejabberd:
=================
Install ejabberd;
apt-get install ejabberd

Procedure:
==========

01. stop all ejabberd instances on shrek:
shrek# /etc/init.d/ejabberd stop

02. Move all files to a backup location
mv /etc/ejabberd /etc/ejabberd_shrek
mv /var/lib/ejabberd /var/lib/ejabberd_shrek

03. Get the old files into the new location. I had the backupfiles of the
old server placed on the disk of the new server:
cp -a /data/backups/milliways.verwijs.org/etc/ejabberd /etc/ejabberd
cp -a /data/backups/milliways.verwijs.org/var/lib/ejabberd \
/var/lib/ejabberd

04. Important bit: rename shrek to milliways.
echo "milliways" >> /proc/sys/kernel/hostname
echo "milliways" >> /etc/hostname

05. Now the old hostname has been set, ejabberd-milliways will start
(yay!)
/etc/init.d/ejabberd start

06. Make a backup.
ejabberdctl ejabberd@milliways backup /tmp/backupfile

07. Stop ejabberd
/etc/init.d/ejabberd stop

08. Put the hostname back:
echo "shrek" >> /proc/sys/kernel/hostname
echo "shrek" >> /etc/hostname

09. Put the config-files and database files of shrek back:
rm -rf /etc/ejabberd
mv /etc/ejabberd_shrek /etc/ejabberd
rm -rf /var/lib/ejabberd
mv /var/lib/ejabberd_shrek /var/lib/ejabberd

10. Restart ejabberd
/etc/init.d/ejabberd

11. Use the restore procedure as described here to convert and import you backupfile:
--> http://www.ejabberd.im/migrate-host

12. ??????

13. Profit!

I've never gotten the convert script to work properly however using a TXT dump of the DB works fine for migrating between hosts. I'm not sure of the pros/cons of it vs a restore from a binary backup but I haven't noticed any problems or oddities.

I'm trying to rename my machine, and have gone through these instructions. Everything seems to work fine, until point 8 where I get this error:

darcachon:/var/lib/ejabberd# ejabberdctl restore ejabberd2.backup
RPC failed on the node ejabberd@darcachon: {'EXIT',
                                               {badarg,
                                                   [{ets,
                                                        lookup,
                                                        [config,hosts]},
                                                    {ejabberd_config,
                                                        get_global_option,
                                                        1},
                                                    {ejabberd_admin,
                                                        keep_modules_tables,
                                                        0},
                                                    {ejabberd_admin,
                                                        keep_tables,
                                                        0},
                                                    {ejabberd_admin,restore,1},
                                                    {ejabberd_ctl,process,1},
                                                    {rpc,
                                                        '-handle_call/3-fun-0-',
                                                        5}]}}

I assume this is because the ejabberd cannot start up with the old database; if so, how do I clear down the DB so that it thinks it's starting on a fresh installation?

Cheers,

Giles

In ejabberd 1.1.2 it does not work to me

Script converts backup files - it replaces every occurence of old node name with new node name. To use it, you have to call it from erl.

First, start erl:

erl -name mynode

Name should be unique, there should be no other node named mynode.

Erl shell should start and display prompt.

Inside erl prompt you can load the file you just saved. This file should reside in current directory. Type:

c(convert).

Erl should print status message "ok".

Now call funtion:

convert:change_node_name(ejabberd@oldhost, 'ejabberd@newhost', "/path/to/old/backup-file", "new-backup-file").

If everything works well you'll get "new-backup-file" in current dir ready to be loaded (with ejabberd restore or ejabberd install-fallback) into new node. Of course you'll have to replace "ejabberd@oldhost" and "ejabberd@newhost" with old and new node names. Quotations used above are correct (in sense that they worked - I don't know Erlang and I completely don't understand quotation issues in this language).

Good luck!