-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
warning Unexpected info: mnesia_up #3842
Comments
Looking at the source code, the opposite The Just looking at this, without knowing that are the exact implications, I would say it's just informative, shouldn't worry, and maybe ejabberd should handle this event and simply do nothing. But before doing any change, all this should be checked. |
More on these warnings. I found out that whenever I run the following command As you said, I guess this is just normal events when you run a join_cluster command. Ejabberd's log could probably be improved by handling such events to display a more informative entry instead of a generic warning. I think something like : |
Thanks for those details! Following them, I found that the two first warnings are generated by ejabberd_s2s and ejabberd_sm_mnesia. The other two are again generated by those two modules. I've added code to handle those cases and provide informative log messages instead of generic warnings. |
Environment
ejabberd version: 21.12
Erlang version: Erlang (SMP,ASYNC_THREADS) (BEAM) emulator version 10.7.2.14
OS: Linux (Buildroot)
Installed from: Buildroot
Errors from error.log/crash.log
Bug description
I have a cluster of 4 ejabberd nodes. Ejabberd log is flooded by the following warning messages:
Should I worry? To be honest, I'm not sure I understand what it means. It looks to me this is simply the mnesia table from another node that inform this ejabberd node that it is up and running again.
Should ejabberd handle such event and do something when it occurs?
The text was updated successfully, but these errors were encountered: