InfluxDB out Node RequestTimedOutError on InfluxDB 2 online about node-red-contrib-influxdb HOT 9 CLOSED

I have the same situation. I get these annoyings errors.
In my case I write into influxdb every 1 second.
Any possible solution to fix it or how to debug it?

from node-red-contrib-influxdb.

I am writing every 5s and receiving thousands messages of this error.
Dose anyone have a solution?

from node-red-contrib-influxdb.

Since some weeks, I have the same problem with my communication between NodeRed and influxDB. NodeRed is running on a raspberryPi4 and influxDB in a docker container on my Synology. No one can help ? Best Regards

from node-red-contrib-influxdb.

having a very similar (or same) issue. After a few days, I'm receiving many errors.

However, the infuxDB is receiving and logging the values properly. So for me everything seems to work fine, aside from many errors triggering.

InfluxDB is running locally on the same machine. I've tried to decrease the amount of messages, but without changes in the behavior.

from node-red-contrib-influxdb.

Since this issue would be difficult to reproduce, requiring days of testing, and based on the report of a request timeout error, I decided to try adding a connection timeout feature (0.7.0) so that it's possible to increase the connection timeout. Have you tried the latest version 0.7.0 and increasing the timeout to see if this addresses the problem in your setup?

from node-red-contrib-influxdb.

Same as #134 assuming connection timeout feature fixes this unless I hear otherwise.

from node-red-contrib-influxdb.

Hi,
I've meanwhile tested the new feature, but it doesn't solve the issue. What I wan't to highlight, the data is being successfully written to the InfluxDB, no matter if I get the error or not.

And as mentioned, the error only starts to come after a few hours/days.

However what is new with 0.7.0: There is a new Error:

Both of these errors do come in bulk. And after some time, there is a bulk of the following errors:

Then it starts over.

Seems like the timeout does not have any effect. Please let me know if I can provide any further details or logs to help support you.

from node-red-contrib-influxdb.

Hmm. It's not clear to me this is a node/client problem, but if I have time I will try looking into it.

Can you characterize the load and tell me what sort of machine you are running InfluxDb on? i.e. how many writes, how much is written, what sorts of queries? Does the load change before this happens? What version of InfluxDb are you using (2.7.x)? Perhaps you just need more resources (CPU, Memory) for the db or an upgrade to a newer version?

from node-red-contrib-influxdb.

okay, so here some infos:

• influxDB v2.7.1
• NodeRed v3.0.2
• node-red-contrib-influxdb v0.7.0

Everything running on a Synology NAS (DS220+ (Intel Celeron J4025 2-Core 2,0 GHz, Turbo bis 2,9 GHz ; 6GB RAM))
Setup everything using Docker on the NAS.
Overall ressource consumption of the NAS itself is quite low.

Also as mentioned, the values seem to be received by InfluxDB. I don't find any values missing there.

My Requests are roughly:
~25 every 1 minute
~4 every 10 seconds
~30 every 15 seconds

So it is always a bulk that is triggered. e.g. with the 25 every minute, it roughly looks like this, and the result goes to the influxDb node.

The data per request is always similar. Some sensor data, with some tags. A typical message looks like this:
{
payload: [{
// _values here:
temp: msg.payload*msg.topic.faktor,
},
{ //Tags here:
prozesswert: msg.topic.name,
register: msg.topic.register,
einheit: msg.topic.einheit
}]
};

everything either strings with 5-15 characters or some temperature, voltage, etc. values.

However, I've also tried with a delay node to reduce message load to 5msg/second. without change.

thanks for your efforts. Let me know if I can be any more of a help.

from node-red-contrib-influxdb.