Known Issues in EMQX 5.9
e5.9.0
| Since version | Issue | Workaround | Status |
|---|---|---|---|
| 5.0.0 | Node Crash if Linux monotonic clock steps backward In certain virtual Linux environments, the operating system is unable to keep the clocks monotonic, which may cause Erlang VM to exit with the message OS monotonic time stepped backwards!. | For such environments, you may set the +c flag to false in etc/vm.args. | |
| 5.3.0 | Limitation in SAML-Based SSO EMQX Dashboard supports Single Sign-On based on the Security Assertion Markup Language (SAML) 2.0 standard and integrates with Okta and OneLogin as identity providers. However, the SAML-based SSO currently does not support a certificate signature verification mechanism and is incompatible with Azure Entra ID due to its complexity. | - | |
| 5.1.0 | Replicant nodes may hang on startup when new core nodes are added to the cluster During cluster changes that involve adding new core nodes, the newly added cores may occasionally fail to start replication-related processes required by replicant nodes. This, in turn, caused upgraded or newly added replicant nodes to hang during startup. In Kubernetes deployments, this led to the controller repeatedly restarting replicant pods due to failing readiness probes. This problem typically occurs during upgrade rollouts, for example, when expanding an existing 2-core + 2-replicant cluster by adding two new core nodes and two new replicants running a newer EMQX version. | If one or more replicant nodes hang during startup after being (re)deployed, consider forcefully restarting the newly added core nodes one at a time until the replicants unblock and complete startup. | Fixed in 6.0.1 |