-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
Internal server error 500 after upgrading from 5.3.0 to 5.3.2 #12185
Comments
I can confirm that the problem is with 5.3.2, version 5.3.1 works fine. |
Hi.
|
Here comes logs but NOTE: After upgrade and collect logs, when running with 5.3.2, I've disabled the file log and all mqtt authentication, and when back to 5.3.1, emqx crashes. I'm now on 5.3.2 because I can't go back. I suppose that the changes on configuration I've made, makes new configuration incompatible with 5.3.1 and causes the crash. Is possible go back to 5.3.1? |
Thanks for the extra info. I managed to reproduce your issue by starting on 5.3.0, creating an HTTP bridge, and then using the same config on 5.3.2. That produces the following log when starting EMQX:
However, I could not observe the same issue when trying to access the bridges API: the bridge is return correctly when listing all bridges or getting its config. Did you observe the error while trying to list the bridges in a "mixed cluster"? That is: a cluster with some nodes in 5.3.0, some in 5.3.2? That could explain how you experience it. This particular error should be resolved in 5.4.0 (still unreleased), and considering the whole cluster is running the same (new) version.
Automatically downgrading the configuration file is not supported, I'm afraid. If you changed something in 5.3.2, then it probably saved the new state in the new format. You would need to inspect the logs when EMQX crashes and see which configurations it complains about, and then try to manually fix the config before starting it in an older EMQX version. |
No, I only have one node, but in
Ok, no problem I only want to know if there is an easy way, I have backups ( |
Those shouldn't affect your single node. If you are sure the folders are not used by your node (i.e., they don't match the name of such single node or any other in the cluster), then you can remove them.
Both methods should work (using an older |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
What happened?
After upgrading emqx docker version from 5.3.0 to 5.3.2, when accessing Integrations, app shows an error that correspond to the API server response accessing
https://mydomain.com/api/v5/bridges
:Rules are kept, but Data Bridges are not shown.
What did you expect to happen?
Show my previously created Data Bridges and Flow, without any error.
How can we reproduce it (as minimally and precisely as possible)?
I don't know if it is reproducible, but I have some four Rules and two Data Bridges (HTTP and MQTT).
Anything else we need to know?
No response
EMQX version
OS version
Log files
The text was updated successfully, but these errors were encountered: