-
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
Failed RPC connection to the node 'ejabberd@xxx': timeout #4270
Comments
21.07? why so old.. latest is 24.07 😄 |
Do 'aaa' and 'bbb' resolve on both nodes correctly? And is network setup in such way that they both can access themselves? |
using ping to check, can resolved correctly and can access themselves |
Yes, that probably why this failed. My guess would be ports used for communications aren't accessible between nodes. Or could be issue with cookie used for authentication (to check that you can use debug console and execute |
the cookie were same, I manual added ip and hosts in aaa and bbb's /etc/hosts |
Can you see what |
|
Could you try joining node from debug shell instead of ejabberdctl, just execute |
still timeout |
@zzzZLRzzz: What is your ejabberd version? |
Environment
Errors from error.log/crash.log
No errors
Bug description
deploy ejabberd on k8s, this time when a update the application and create a new node ejabberd@bbb.
using ejabberdctl join_cluster ejabberd@aaa
the log print: "Failed RPC connection to the node 'ejabberd@bbb': timeout"
i found that the application seems to restart after i use the join_cluster command.
but this time it become unhealthy and unrecoverable
The text was updated successfully, but these errors were encountered: