summaryrefslogtreecommitdiffstats
path: root/.mailmap
blob: 2d43d329c3e8664aed76af0650f7b5e9b8c32788 (plain) 
1
2
3
4
5
6
7
8
9
10
11
12
13
14

<dev@bernhard-posselt.com> <nukeawhale@gmail.com>
<dev@bernhard-posselt.com> <raydiation@users.noreply.github.com>
<dev@bernhard-posselt.com> <bernhard@posselt.at>
<dev@bernhard-posselt.com> <BernhardPosselt@users.noreply.github.com>
<cosenal@gmail.com> <acosenti@malutchosky.(none)>
David-Development <david-dev@live.de>
<hey@morrisjobke.de> <morris.jobke@gmail.com>
Alessandro Cosentino <cosenal@gmail.com> Alessandro <cosenal@gmail.com>
Jenkins for ownCloud <owncloud-bot@tmit.eu> Jenkins for ownCloud <thomas.mueller@tmit.eu>
Thomas Müller <thomas.mueller@tmit.eu> Thomas Mueller <thomas.mueller@tmit.eu>
bastei <bastei@users.noreply.github.com> bastei <none>
Konrad Graefe <konradgraefe@aol.com> kgraefe <konradgraefe@aol.com>
<lukas@owncloud.com> <lukas@statuscode.ch>
<dev@ibboard.co.uk> <github@ibboard.co.uk>
generated by cgit v1.2.3 (git 2.25.1) at 2024-06-22 17:14:39 +0000
ng, and the message wasn't delivered to the client as expected. ### Troubleshoot the alert 1. Check the VerneMQ logs: VerneMQ logs can give you valuable information about possible errors that might have occurred during the processing of `PUBREL` packets. Look for any error messages or traces related to the `PUBREL` packets in the logs. ``` sudo journalctl -u vernemq -f ``` Alternatively, if you're using a custom log location: ``` tail -f /path/to/custom/log ``` 2. Check the MQTT client-side logs: Check the logs of the MQTT client that might have caused the unsuccessful `PUBREL` packets. Look for any connection issues, error messages, or traces related to the MQTT protocol exchanges. 3. Ensure proper configuration for VerneMQ: Verify that the VerneMQ configuration settings related to QoS 2 protocol timeouts and retries are correctly set. Check the VerneMQ [documentation](https://docs.vernemq.com/configuration) for guidance on the proper configuration. ``` cat /etc/vernemq/vernemq.conf ``` 4. Monitor VerneMQ metrics: Use Netdata to monitor VerneMQ metrics to analyze the MQTT server's performance and resource usage. This can help you identify possible issues with the server. 5. Address network or service issues: If the above steps don't resolve the alert, look for possible network or service-related issues that might be causing the unsuccessful `PUBREL` packets. This could require additional investigation based on your specific infrastructure and environment. ### Useful resources 1. [VerneMQ - Official Documentation](https://docs.vernemq.com/) 2. [MQTT Essentials: Quality of Service 2 (QoS 2)](https://www.hivemq.com/blog/mqtt-essentials-part-6-mqtt-quality-of-service-levels/) 3. [Netdata - VerneMQ monitoring](https://learn.netdata.cloud/docs/agent/collectors/go.d.plugin/modules/vernemq)
generated by cgit v1.2.3 (git 2.25.1) at 2024-06-22 17:14:39 +0000