/
"hivemq" service fails during restart on RedHat Enterprise Linux 8
"hivemq" service fails during restart on RedHat Enterprise Linux 8
Problem
Your HiveMQ broker fails to start after a restart on RedHat Enterprise Linux 8.
Steps to Diagnose
In RedHat Enterprise Linux 8, all security and authentication-related messages and errors are recorded in the "/var/log/secure" file. To troubleshoot this issue:
Access the /var/log/secure file:
sudo cat /var/log/secure
Review recent user management activity:
Look for any entries related to user additions (
useradd
) or deletions (userdel
).
Solution
Check if these virtual machines (VMs) were imaged based on user IDs set up by your IT department. Update your IT policies accordingly to prevent this issue in the future.
Related articles
, multiple selections available,
Related content
HiveMQ platform operator pod fails to start
HiveMQ platform operator pod fails to start
More like this
Sanity checks take a long time during HiveMQ startup
Sanity checks take a long time during HiveMQ startup
More like this
ERROR - Could not open data lock file | HiveMQ Platform Operator (new)
ERROR - Could not open data lock file | HiveMQ Platform Operator (new)
More like this
Windows Service Fails to Start
Windows Service Fails to Start
More like this