First of all, you can simply

badlop — Wed, 22 Jun 2016 11:31:48 +0000

First of all, you can simply stop at step 5; after all, ejabberd works correctly, and using a forced erlang node name doesn't hurt. But it's good to attempt to know where the problem is, so let's continue.

Second, I guess in step 9 you edit ejabberdctl.cfg again to set the newhostname.

Third, the problem is that the backup file contains a mnesia table called "config", which was used in ejabberd 2. Nowadays that table is stored in ETS, per vhost, so it isn't required at all.

I can think this solution, split 5 in all those small steps:
5.1 Start ejabberd in live mode, so you get an erlang shell
5.2 Check ejabberd starts correctly, converts the old database, etc.
5.3 In that erlang shell, execute this (remember the dot a the end): mnesia:delete_table(config).
5.4 Backup the database as usual: ejabberdctl backup /path/to/file.bak

Now you can proceed with step 6.
Notice you can repeat step 5.3 if it complains about other tables.

Fourth, if you try this solition, please tell me if it really works, so that I update the explanations in https://docs.ejabberd.im/admin/guide/managing/#change-computer-hostname

ejabberd - Comments for "Migration 2.1.X -&gt; 16.04"

First of all, you can simply

ejabberd - Comments for "Migration 2.1.X -> 16.04"