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
After installing the plugin in the k8s cluster environment, the repl node cannot be restarted #10282
Comments
Hello, Could you please clarify this part: "3.Delete one of the repl nodes to automatically restart". What do you mean by delete? Remove the pod, or something else? Also I need full logs from the node that experienced the problem. |
|
Is there anything else I can help with? I think this question is easy to reproduce, I don't think it is necessary to use k8s. The problem can be reproduced even in a docker cluster environment or a virtual machine cluster environment. I think the problem is mainly related to the inability to successfully start or find the plug-in when the node starts. |
hey, there is a problem with the repl node in the form of statefulset, but the problem in the form of deployment no longer exists. |
When repl is in the deployment environment (using the cluster built by the official operator), errors may also occur. The error occurs when the plugin is installed, started, uninstalled, and reinstalled, resulting in the following error:
Then, the plugin will continue to display inactive and cannot be activated normally,And cannot be uninstall.
|
@zmstone hi, I think the problem is related to crc32cer and emqx_pluginrel |
What happened?
After installing the plugin in the k8s cluster environment, the repl node cannot be restarted
What did you expect to happen?
The repl node started successfully
How can we reproduce it (as minimally and precisely as possible)?
1.Start 3core node, 6repl node cluster
2.install plugin
3.Delete one of the repl nodes to automatically restart
Anything else we need to know?
Repl node fails to start properly
An error occurs on the dashboard page:
EMQX version
OS version
Log files
The text was updated successfully, but these errors were encountered: