# Core uncaught exception stopping node-red?

**URL:** <https://discourse.nodered.org/t/core-uncaught-exception-stopping-node-red/45013>\
**Category:** General\
**Created:** [1 May 2021 10:05 UTC](https://discourse.nodered.org/t/core-uncaught-exception-stopping-node-red/45013 "2021-05-01T10:05:59Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![bsense](https://avatars.discourse-cdn.com/v4/letter/b/cab0a1/32.png) [@bsense](https://discourse.nodered.org/u/bsense)\
**Post date:** [1 May 2021 10:05 UTC](https://discourse.nodered.org/t/core-uncaught-exception-stopping-node-red/45013/1 "2021-05-01T10:05:59Z")

</div>

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!

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [1 May 2021 10:23 UTC](https://discourse.nodered.org/t/core-uncaught-exception-stopping-node-red/45013/2 "2021-05-01T10:23:02Z")

</div>

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?

---

<div class="post-metadata">

**Author:** ![bsense](https://avatars.discourse-cdn.com/v4/letter/b/cab0a1/32.png) [@bsense](https://discourse.nodered.org/u/bsense)\
**Post date:** [2 May 2021 07:04 UTC](https://discourse.nodered.org/t/core-uncaught-exception-stopping-node-red/45013/3 "2021-05-02T07:04:09Z")

</div>

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

Thank you!

---

<div class="post-metadata">

**Author:** ![Steve-Mcl](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/steve-mcl/32/4826_2.png) [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)\
**Post date:** [2 May 2021 08:29 UTC](https://discourse.nodered.org/t/core-uncaught-exception-stopping-node-red/45013/4 "2021-05-02T08:29:46Z")

</div>

> [@bsense](#):
>
> I've found out that the issue is in postgres module

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.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/d073cd938eafa2e558d7c2cd59003b3ef4963033.png) [@system](https://discourse.nodered.org/u/system)\
**Post date:** [1 July 2021 08:30 UTC](https://discourse.nodered.org/t/core-uncaught-exception-stopping-node-red/45013/5 "2021-07-01T08:30:23Z")

</div>

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