1 million mqtt messages within 5 minutes #16563
Comments
|
Are you sure about the health of your broker? |
|
The broker is up and running - completely normal behaviour. All other clients connect perfectly without issues. Updated the mqtt-broker - same probleme as before. Tried a test-mqtt-broker - same probleme. Only when I set the ip-addresses for the OpenWB Pros to nirvana then the probleme with millions of mqtt messages disappears. Updated the firmware of my two OpenWB Pros a few minutes ago but same issue... |
Not visible in the log. Dein Broker hat einen Schluckauf und anscheinend funktioniert das Reconnect nicht, deshalb stauen die sich die Nachrichten. Leider kann ich das Reconnect-Issue (das wir auch schon in volkszaehler/mbmd#346 gesehen) nicht reproduzieren. Ohne Reproducer gibts leider keinen Fix. Im Zweifel musst Du versuchen die Ursache lokal mit Deinem Broker zu identifizieren, ein kleines Go-Tool bauen und ggf. ein Ticket bei https://github.com/eclipse/paho.mqtt.golang auf machen. Ich hab leider keinen Anhaltspunkt wo ich suchen könnte. Maybe c5d3168 can help with the load, but it won't fix the reconnect. |
|
I tried another MQTT-broker in my network - the one hosted on my Venus OS installation. Same probleme here - My wild guess is still that it has to do something with the openWB Pros. As soon as EVCC connects to the wallboxes the probleme starts... |
|
OWBPro has nothing to do with mqtt. |
|
@chiefjoejj Can you see any other messages in your broker? |
|
Thanks for all your input guys! In the end I was able to solve the problem. It had nothing to do with the docker environment or network modes but with my buggy config.yaml file. I completely started from scratch using the terminal-config-builder to create a minimal setup that allowed EVCC to start up and then I recursively modified/added the desired sections. After each step I checked the mqtt-behavior and after a perceived infinity all worked again perfectly. So glad I invested the time and got the issue fixed and can continue excess charging with the expected behaviour... |
chiefjoejj
changed the title
Describe the bug
My EVCC-installation pushes out a crazy amount of mqtt-messages which causes a high cpu load within my docker environment. Otherwise I wouldn't care because it is working - apart from the constant error messages telling me that there are "no message IDs availabe" because I guess my mqtt-broker is completely giving up... Tried a couple of modifications within my evcc.yaml but no luck so far to fix it. help, please! :)
Steps to reproduce
...
Configuration details
Log details
What type of operating system are you running?
Linux
Nightly build
Version
v0.130.13
The text was updated successfully, but these errors were encountered: