rguenther-dz

Hi @bb-Ricardo, thanks for the fast response. yes, the error message says it´s an overflow. But it looks like the root cause is inside fritzinfluxdb. Restarting fritzinfluxdb resets the error...

ok. now running in debug mode .. The values correlate to what we see in the grafana panel. Now waiting maybe some days to catch the next error... This looks...

we have the next event.. the incorrect values are also present in the debug output of the TR-069 info.  and we see this is not an overflow, its an...

During the underflow i get the error message. The error messages are concatenated like in the first post, until the string gets too long and the fritzinfluxdb docker container dies....