Core uncaught exception stopping node-red?

General
1

I am using node-red with 4G modem. On a timely fashion (each day at 08:56 and 09:12) i get two consecutive events that might be related to ip lease renewal or similar by the network carrier.

Anyway, i get an uncaught exception ENETUNREACH at TCP.onStreamRead (internal/stream_base_commons.js:209:20), that ends with node-red exitting. Might it be a node-red core uncaught exception or a palette node issue...

may 01 09:12:25 Node-RED[3916]: 1 May 09:12:25 - [red] Uncaught Exception:
may 01 09:12:25 Node-RED[3916]: 1 May 09:12:25 - Error: read ENETUNREACH
may 01 09:12:25 Node-RED[3916]: at TCP.onStreamRead (internal/stream_base_commons.js:209:20)
may 01 09:12:25 systemd[1]: nodered.service: Main process exited, code=exited, status=1/FAILURE
may 01 09:12:25 systemd[1]: nodered.service: Failed with result 'exit-code'.
may 01 09:12:45 systemd[1]: nodered.service: Scheduled restart job, restart counter is at 3.
may 01 09:12:45 systemd[1]: Stopped Node-RED graphical event wiring tool.
may 01 09:12:45 systemd[1]: Started Node-RED graphical event wiring tool.

Surely I can live with that, I was trying to report a potential issue just to improve this fantastic too,l

Thank you all!

2

What version of node-red and nodejs are you running? You can see the node-red version at the bottom of the Menu dropdown and you can run
node -v to get the nodejs version.

Are you using the core TCP node or is it something else using TCP?

3

After some digging I've found out that the issue is in postgres module that uses the postgres node

Thank you!

4

It would be very good if you could raise an issue for that against the contrib node so the author has a chance to fix up the node& prevent crashing node-red.

5

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.