You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After importing a previous export containing retained messages, all the retained messages reported an empty payload. The dashboard gave a 404 NOT_FOUND error. New MQTT clients did not receive any retained messages on subscription
Before import I cleared the retained messages in 3 ways. Each test had the same broken behaviour
Publish an empty, retained message
Clear all messages from the dashboard
Remove the persistent volume and re-initialise a new database
What did you expect to happen?
I expected the retained messages to be visible on the dashboard and delivered to any new MQTT client subscribing on that topic
How can we reproduce it (as minimally and precisely as possible)?
Populate some retained messages using an MQTT client
Backup using emqx ctl data export
Clear all retained messages using the EMQX dashboard
Restore using emqx ctl data import <File>
Verify using EMQX dashboard to view the payload of a restored message.
Anything else we need to know?
I managed to clear the fault by running the command
What happened?
After importing a previous export containing retained messages, all the retained messages reported an empty payload. The dashboard gave a 404 NOT_FOUND error. New MQTT clients did not receive any retained messages on subscription
Before import I cleared the retained messages in 3 ways. Each test had the same broken behaviour
What did you expect to happen?
I expected the retained messages to be visible on the dashboard and delivered to any new MQTT client subscribing on that topic
How can we reproduce it (as minimally and precisely as possible)?
emqx ctl data export
emqx ctl data import <File>
Anything else we need to know?
I managed to clear the fault by running the command
After the command completed, I could view all retained messages on the dashboard and receive them on new MQTT client subscriptions
Perhaps this step is missing from the
emqx ctl data import <File>
command - or the Backup and Restore documentation should be updated to include this extra step. https://www.emqx.io/docs/en/latest/operations/backup-restore.html#cli-exampleEMQX version
emqx-operator
emqx/emqx-operator-controller:2.2.21
emqx
emqx/emqx:5.6.1
OS version
Log files
The text was updated successfully, but these errors were encountered: