Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ejabberd fails to start when docker container id changes #169

Open
diegofal opened this issue Jun 18, 2018 · 1 comment
Open

Ejabberd fails to start when docker container id changes #169

diegofal opened this issue Jun 18, 2018 · 1 comment
Labels

Comments

@diegofal
Copy link

Currently, when ejabberd inits I can see this message:

"Application ejabberd started on node 'Mnesia@fe29feed088d'" -> after the @, "fe29feed088d" is the current container id.

When the container id changes, the database fails to start since the owner is attached to the previous container id.

Any thoughts on this?
Thanks!!

@rroemhild
Copy link
Owner

This is how mnesia setup database. You can set ERLANG_NODE env to i.e. ejabberd@localhost and the mnesia database will be the same on each reboot / re-creation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants