Bug: Log is flooded with RequestTimedOutErrors

[winnieXY]

I just recognised that my log is flooded since a unkown time with a massive amount of errors (>200/s).

I've already updated to the newest version 0.7.0 and increased the timeout from 10 -> 15 -> 20 -> 25. Nothing helps.

The setup was running stable at least for three years before - so the write frequency should be okay (~ 1 msg/s roughly).

I saw that there are already several bugs which are however closed. As I'm not sure which of them is the best one to track this down I've created this new one. Please feel free to reopen one of the others and close this one if this is more appropriate.

If you need more information/ debug logs please let me know. I need to get back my debug console for testing as soon as possible :-)

[winnieXY]

After playing a little bit with node-red & influxdb I get now this (slightly different) error:

[Dufty-de]

Hi,
I have the same problem like winnieXY.
I´m also using V0.7.0
I'd triggered a couple of http requests with one inject node and want to transfer the result to influxdb.
In order to strech the requests at the same time, i´ve mulitplied the injects and start each with a time shift of 0,2 s; but, the same result.
A restart of node red helps for a handfull of hours.
NodeRed and influxdb runing in a docker container on a synology with more than enough memory and are both up to date.
If you need more information feel free to contact me.

[winnieXY]

Any news on that? That's really a showstopper right now

[Bond246]

I think i don't have an solution.
But... Do you use influx 2 with flux-query oder with influx 1 and the older query language?

And do you use it in docker or as native installation?

[Dufty-de]

Hi, I use a docker installation on a Synology with influx 2.75 and flux. The problem is, the situation is not reproduceable: sometime it is and sometime not…. (at the moment not) BR Wolfgang Von: Florian ***@***.***> Gesendet: Freitag, 24. Mai 2024 09:35 An: mblackstock/node-red-contrib-influxdb ***@***.***> Cc: Dufty-de ***@***.***>; Manual ***@***.***> Betreff: Re: [mblackstock/node-red-contrib-influxdb] Bug: Log is flooded with RequestTimedOutErrors (Issue #143) I think i don't have an solution. But... Do you use influx 2 with flux-query oder with influx 1 and the older query language? And do you use it in docker or as native installation? — Reply to this email directly, view it on GitHub <#143 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/BFWYD5RXFWSJ5EOOAGIXB23ZD3US3AVCNFSM6AAAAABCDOFUVCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMRYHAYDCMRWGA> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[Dufty-de]

Hi,
yesterday i´ve had again the problem with the RequestTimedOutErrors.
My oberservation: 1st i´ve tried to transfer msg.payload as an array (i.e. msg.measurement = "power"; msg.payload =[{value: #}, {phase: "ph0"}, {level: "basement"}];
(you can transfer to influx not only the meassurement and the value, you can also add attributes to the measurement).
Here I´ve got the errors.
When I reduce the #of attributes to one, the node works without errors.
(i.e. msg.measurement = "powerPhase0"; msg.payload =[{value: #}, {level: "basement"}];
or even a plain value in the payload and measurement="PowerPhase0Basement".
Maybe it´s a hint to solve the problem or to create a workaround
BR

[coolchip]

I've the same error. Using also Node-RED and InfluxDB as Docker container.
It runs for years but now i get tons of errors.

The log of InfluxDB and another docker container showing also strange TCP connection errors. So I thought it might be a docker network error. But I have no idea how to inspect that.

[tinooo]

Same issue here.
Using 0.7 on docker. influxdb 2.7.1, using flux.

I've can't nail down the issue. But I'm quite sure that even though the error is raised, the values are still being written to influxdb