zmstone
zmstone
@Rotario I guess `fdaa:0:e26a:a7b:8f:ff70:e24:2` is `6e82e56f2e3038`'s address? Is `emqx@fdaa:0:e26a:a7b:8f:ff70:e24:2` by any chance configured in the static discovery node list ? Could you share the output of this command (in the...
Ah. ok. Now I get it. The node name should not use FQDN as host part if you use DNS discovery strategy. This is because DNS resolution is a list...
This only applies to the inflight messages, for messages in mqueue, they should be redispatched. > According to [MQTT Specification](https://docs.oasis-open.org/mqtt/mqtt/v5.0/os/mqtt-v5.0-os.html#_Toc3901250), If the Client's Session terminates before the Client reconnects, the...
I have tested with QoS 1 and QoS 2. Both worked as expected. @rafsawicki I noticed that your subscriptions are both with QoS 1 (which is good). Please make sure...
Internal tracking reference: [EMQX-11120](https://emqx.atlassian.net/browse/EMQX-11120) BTW. Going to support clinetid, but not username
HI @leobesen To help narrow down the investigation scope, could you share with us which features you have enabled ? E.g. rule engine which processes JSON payload? making use of...
we may need to reproduce this issue first. debian 12 on arm plus similar configs and messages as in @leobesen's environment.
Thank you @mdahlmanns This suggestion makes perfect sense.
The client ID prefix config is now configurable from dashboard, at least 5.7.0 has it. Closing this issue. Related fix: https://github.com/emqx/emqx/pull/13216
you mean add queue length in trace logs ?