/
Diagnostic Archive generation failed
Diagnostic Archive generation failed
Problem
After clicking the button “Generate Diagnostic Archive”, the progress reached almost 100% but then failed and no archive was created.
Solution
There is a way to retrieve the diagnostic archive zip files from the nodes of the broker, if those were generated but failed to get downloaded.
Check the hivemq.log file at each cluster node
Make sure on every node there is a success log message like the following:
Node AAAAA:INFO - Created diagnostic zip '/opt/hivemq/log/diagnostic/diagnostic-20230501-061447-AAAAA.zip' successfully.
Node BBBBB:
INFO - Created diagnostic zip '/opt/hivemq/log/diagnostic/diagnostic-20230501-061447-BBBBB.zip' successfully.
Node CCCC:
INFO - Created diagnostic zip '/opt/hivemq/log/diagnostic/diagnostic-20230501-061447-CCCCC.zip' successfully.
Download files which have the same date and time from all nodes manually and upload to HiveMQ Support for analysis.
The file name diagnostic-20230501-061447-CCCCC.zip
means that the archive generation started on the date 2023-05-01
at 06:14:47
and the node is CCCCC
.
Related articles
, multiple selections available,
Related content
HiveMQ platform operator pod fails to start
HiveMQ platform operator pod fails to start
More like this
“Not Enough Disk Space” Warning in the HiveMQ Control Center
“Not Enough Disk Space” Warning in the HiveMQ Control Center
More like this
Sanity checks take a long time during HiveMQ startup
Sanity checks take a long time during HiveMQ startup
More like this
Increased Heap Consumption or Consistently Rising in HiveMQ
Increased Heap Consumption or Consistently Rising in HiveMQ
More like this