Node Red RequestTimedOutError

Hello All

I am using a local dockered node-red instance aquiring data from an azure IoT-Hub and pushing data into an influxDB 2 online instance. I am using the influxdb out node (from node-red-contrib-influxdb, version 0.6.1). After some days of running perfectly fine, the whole node-red instance stops working. In the logs i get the following errors:

WARN: Write to InfluxDB failed (attempt: 1). S [RequestTimedOutError]: Request timed out
    at ClientRequest.<anonymous> (/data/node_modules/@influxdata/influxdb-client/dist/index.js:16:4142)
    at ClientRequest.emit (events.js:400:28)
    at TLSSocket.emitRequestTimeout (_http_client.js:790:9)
    at Object.onceWrapper (events.js:519:28)
    at TLSSocket.emit (events.js:412:35)
    at TLSSocket.Socket._onTimeout (net.js:495:8)
    at listOnTimeout (internal/timers.js:557:17)
    at processTimers (internal/timers.js:500:7)
20 Jul 07:31:25 - [error] [influxdb out:Influx CtxGamma] RequestTimedOutError: Request timed out

This message is repeated (thousands of times) for every trigger event until the node-red stops trying. After i restart the node, it continues working for maybe 4-5 days. On the influxdb online portal there are no alarms, errors or what so ever. Has somebody encountered the same issue?

Hello @traceurSaimn,
Oof that’s so annoying, unfortunately I’m not sure. @Jay_Clifford any thoughts on how to debug this?

How often are you writing data to InfluxDB in Node-RED?

Every 0.5 s. Would you recommend writing batchwise?

Just to be clear, you are using the Influxdb out node, correct? Since no errors appear in the InfluxDB logs, I think you might want to post your errors (from your initial post) to the node author’s Github page.


1 Like

Yes, I do use the influxdb out node. But thank you so far @grant1. I will try to get more information on the github page.

FWIW, I use Node-RED and the same InfluxDB out node to write to Influx every 30 seconds, and it has not crashed or given me any errors in over 6 months. I think writing every 0.5 second should be possible.