ejabberd - Comments for "can't use mnesia database after 17.04->17.06 or 17.07 upgrade: node name mismatch"

Yes, I checked this. The

t.animal — Tue, 11 Jul 2017 10:15:35 +0000

Yes, I checked this. The server started before I changed the config file. I have filed a bug describing the problem in detail: https://github.com/processone/ejabberd/issues/1847

Maybe the configuration file

badlop — Mon, 10 Jul 2017 16:11:41 +0000

Maybe the configuration file you are modifying is not the one read by ejabberd? If you change any other option in that file, does it take effect, or does it have the same problem that ERLANG_NODE?

Ok, so I figured it out, but

t.animal — Sun, 09 Jul 2017 17:11:26 +0000

Ok, so I figured it out, but I'm not sure if this is the way it should be? The way to fix this, is to delete the database directory, starting ejabberd, stopping it and then restoring the backup. So 1) update ejabberd 2) remove database folder 3) start ejabberd with different node name 4) restore backup. Weird, that was easier in previous versions.

EDIT: Nope, sorry. This is obviously not what I did, I must have done something subtly different, because these steps don't work, either.

EDIT2: OK, this is very weird, maybe it's a bug. When I change the ERLANG_NODE in ejabberdctl's config, it does not work, when I change the default value it in ejabberdctl itself it does (that's the subtle difference, I did not set the ERLANG_NODE via the config but in the script itself).

Yes, that is what I am doing.

t.animal — Fri, 07 Jul 2017 21:29:40 +0000

Yes, that is what I am doing. My ejabberdctl says ERLANG_NODE = ejabberd_foo@localhost (which is just the same like starting ejabberd by ejabberdctl --node ejabberd_foo@localhost). The thing is this has always worked, and if I remember correctly it is necesarry on my system as it is a shared environment and other people are using instances of ejabberd, too. Anyway I cannot simply change the node name to ejabberd@localhost, because then users no longer can log in.

I imagine, what I will

badlop — Fri, 07 Jul 2017 14:56:07 +0000

I imagine, what I will mention now you have already think it, but let's make sure:

In ejabberdctl.cfg in my ejabberd 17.07, that works perfectly, I changed ejabberd@localhost to ejabberd11@localhost (which surely will provoke problems). Then, when starting ejabberd, it complains as expected:

16:51:28.582 [critical] Node name mismatch: I'm [ejabberd11@localhost],
 the database is owned by [ejabberd@localhost]