Nodered restarts several times

Industrial
1

Good morning
I have a nodered in docker mainly working to communicate with SIEMENS PLC via S7 (node-red-contrib-s7) connected to influxdb 1.x and using some API for Grafana (to show ping results)
I have from time to time nodered container restarting and in the log I have the following :

[red] Uncaught Exception:
24 Feb 16:37:27 - [error] Error: read ECONNRESET
    at TCP.onStreamRead (node:internal/stream_base_commons:218:20)
24 Feb 16:37:28 - [info]

Same message can be seen 3 or 4 times and then nothing for a day.
I have a lot of error due to the S7 endpoints because we have some PLC that are shutdown so i was wondering if it could be due to that or something else.
Is there a way to investigate the kind of error causing the restart ?

Node-RED version: v4.1.4
2

What do you see in the log that causes the container restart?

3

I have a lot of errors due to S7 endpoint request timeout but I can have this for hours without any issue.

24 Feb 16:25:49 - [info] Starting flows
24 Feb 16:25:50 - [info] Started flows
24 Feb 16:25:50 - [error] [s7 endpoint:XXX - FAULT] Error: read ECONNRESET
24 Feb 16:25:50 - [error] [s7 endpoint:XXX - DATA] Error: read ECONNRESET
24 Feb 16:25:50 - [error] [s7 endpoint:YYY - RESET] Error: read ECONNRESET
24 Feb 16:25:50 - [error] [s7 endpoint:YYY-DATA] Error: read ECONNRESET
24 Feb 16:25:50 - [error] [s7 endpoint:YYY- FAULT] Error: read ECONNRESET
24 Feb 16:25:50 - [error] [s7 endpoint:YYY-INVERTERS] Error: read ECONNRESET
24 Feb 16:25:50 - [error] [s7 endpoint:TTT- DATA] Error: read ECONNRESET
24 Feb 16:25:50 - [error] [s7 endpoint:TTT- FAULT] Error: read ECONNRESET
24 Feb 16:25:55 - [error] [s7 endpoint:XXX- DATA] Error: read ECONNRESET
24 Feb 16:25:55 - [error] [s7 endpoint:YYY-DATA] Error: read ECONNRESET
24 Feb 16:25:55 - [error] [s7 endpoint:YYY- FAULT] Error: read ECONNRESET
24 Feb 16:25:55 - [error] [s7 endpoint:TTT- FAULT] Error: read ECONNRESET
24 Feb 16:26:00 - [error] [s7 endpoint:YYY-DATA] Error: read ECONNRESET
24 Feb 16:26:29 - [error] [s7 endpoint:ZZZ- FAULT] Error: Request timeout
24 Feb 16:26:29 - [error] [s7 endpoint:ZZZ- data] Error: Request timeout
24 Feb 16:26:30 - [error] [s7 endpoint:ZZZ- RESET] Error: Request timeout
24 Feb 16:26:39 - [error] [s7 endpoint:ZZZ- data] Error: Request timeout
24 Feb 16:26:54 - [error] [s7 endpoint:ZZZ - data] Error: Timeout connecting to the transport
24 Feb 16:26:57 - [error] [s7 endpoint:ZZZ - Totalizers] Error: Request timeout
24 Feb 16:27:09 - [error] [s7 endpoint:ZZZ - data] Error: Timeout connecting to the transport
24 Feb 16:27:19 - [error] [s7 endpoint:ZZZ - data] Error: Request timeout
24 Feb 16:36:28 - [error] [s7 endpoint:ZZZ- FAULT] Error: Request timeout
24 Feb 16:36:29 - [error] [s7 endpoint:ZZZ- data] Error: Request timeout
24 Feb 16:36:31 - [error] [s7 endpoint:ZZZ- RESET] Error: Request timeout
[red] Uncaught Exception:
24 Feb 16:36:34 - [error] Error: read ECONNRESET
    at TCP.onStreamRead (node:internal/stream_base_commons:218:20)
24 Feb 16:36:35 - [info] 
Welcome to Node-RED
===================
24 Feb 16:36:35 - [info] Node-RED version: v4.1.4
24 Feb 16:36:35 - [info] Node.js  version: v20.20.0
24 Feb 16:36:35 - [info] Linux 6.12.63+deb13-amd64 x64 LE
24 Feb 16:36:35 - [info] Loading palette nodes
24 Feb 16:36:36 - [info] Settings file  : /data/settings.js
24 Feb 16:36:36 - [info] Context store  : 'default' [module=memory]
24 Feb 16:36:36 - [info] User directory : /data
24 Feb 16:36:36 - [warn] Projects disabled : editorTheme.projects.enabled=false
24 Feb 16:36:36 - [info] Flows file     : /data/flows.json
24 Feb 16:36:36 - [info] Server now running at http://127.0.0.1:1880/

XXX YYY ZZZ TTT are replaced text but represents a production line

4

That looks like this issue Uncaught ECONNRESET causes Node-RED crash after LOGO! reconnect · Issue #143 · st-one-io/node-red-contrib-s7 · GitHub

If you follow the links through then it appears to have been fixed in the the package nodes7, but that does not seem to have been released to npmjs.com so the contrib node does not include the fix.

1 Like
5

Thank you for the feedback
I will wait for the official fix in the package
At least I know the origin

6

Looking at the dates on those issues I suspect nothing will happen unless you ask for an update there.

7

There is in fact a pull request since Nov 13, 2025 on Nodes7 file s7endpoint.js but not yet released