ejabberd - Comments for "Stuck during domain change"

Thank you for being here, and

fredrik — Mon, 02 Mar 2015 12:41:14 +0000

Thank you for being here, and caring.
It actually means a lot.

I actually understand better now why it happened, at least.

Hello Fredrik, Actually, I

mremond — Mon, 02 Mar 2015 09:48:24 +0000

Hello Fredrik,

Actually, I have been told, the documentation for hostname change is already written and published here:

https://docs.ejabberd.im/admin/guide/#change-computer-hostname

I hope this helps,

Hello, Thanks for your

mremond — Mon, 02 Mar 2015 08:08:03 +0000

Hello,

Thanks for your feedback.
Yes, this is unexpected, but that related to ability to work as a cluster with multiple nodes.

We plan to write a process for changing server hostname on our new documentation site.

Thanks for the feedback :)

I actually got it to run

fredrik — Sat, 28 Feb 2015 19:44:38 +0000

I actually got it to run again...

My hint was that by new hostname wasn't written down any other place than /etc/hosts.

So I changed the order of the entries written behind '127.0.1.1', so that the first entry was unchanged from before.... and voila... no more crashes.

But seriously... that is unexpected behaviour... I nearly decided to restart and have all my users create new passwords and everything...

Correction: when I deleted

fredrik — Sat, 28 Feb 2015 19:33:10 +0000

Correction: when I deleted the files in /var/lib/ejabberd, ejabberd started again properly... but I lost all my data of course... Is there a way to fix my backed up data manually, so ejabberd can start?

I even tried to delete

fredrik — Sat, 28 Feb 2015 19:15:30 +0000

I even tried to delete everything in /var/lib/ejabberd, and ejabberdctl seems to report about the new hostname.... where is it stored.

I thought I had erased every trace of the new hostname, but ejabberd doesn't ever forget about it.

I have changed the hostname

fredrik — Sat, 28 Feb 2015 18:48:04 +0000

I have changed the hostname back, all of the places where I know I can change it. But ejabberd seems to still use the new node name.

How do I export in this case?

Mnesia database schema can

mremond — Fri, 27 Feb 2015 16:14:47 +0000

Mnesia database schema can work in cluster. For that reason, a database schema is tight to a precise nodename.

If you need to change the Erlang VM nodename (that typically includes your server hostname), then you need to export Mnesia database from one hostname and import it in the new hostname.

I hope this helps,