This alert is related to VerneMQ
, the open-source, distributed MQTT message broker. If you receive this alert, it means that the number of failed v3/v5 SUBSCRIBE
operations has increased in the last minute.
MQTT v3 and v5 are different versions of the MQTT protocol, used for the Internet of Things (IoT) devices and their communication. The SUBSCRIBE
operation allows a client (device) to subscribe to a specific topic and receive messages published under that topic.
Identify the location of the VerneMQ logs. The default location is /var/log/vernemq
. If you have changed the default location, you can find it in the vernemq.conf
file by looking for log.console.file
and log.error.file
.
grep log.console.file /etc/vernemq/vernemq.conf
grep log.error.file /etc/vernemq/vernemq.conf
Analyze the logs for any errors or issues related to the SUBSCRIBE
operation:
tail -f /path/to/vernemq/logs
Check the available resources (RAM and CPU) on your system:
top
If you find that the system resources are low, consider adding more resources or stopping unnecessary processes/applications.
Most MQTT clients (e.g., Mosquitto, Paho, MQTT.js) provide their logs to help you identify any issues related to the SUBSCRIBE
operation.
Analyze the client logs for errors in connecting, subscribing, or receiving messages from the MQTT broker.
Verify if there are any invalid, restricted, or forbidden topics in your MQTT broker.
Check the ACLs (Access Control Lists) and client authentication settings in your VerneMQ vernemq.conf
file.
grep -E '^(allow_anonymous|vmq_acl.acl_file|vmq_passwd.password_file)' /etc/vernemq/vernemq.conf
Ensure the ACLs
and authentication configuration are correct and allow the clients to subscribe to the required topics.