# Weird Node-Red errors when working project is running for about 30mins

**URL:** <https://discourse.nodered.org/t/weird-node-red-errors-when-working-project-is-running-for-about-30mins/93405>\
**Category:** General\
**Created:** [24 November 2024 14:42 UTC](https://discourse.nodered.org/t/weird-node-red-errors-when-working-project-is-running-for-about-30mins/93405 "2024-11-24T14:42:42Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![garynl](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/garynl/32/95490_2.png) [@garynl](https://discourse.nodered.org/u/garynl)\
**Post date:** [24 November 2024 14:42 UTC](https://discourse.nodered.org/t/weird-node-red-errors-when-working-project-is-running-for-about-30mins/93405/1 "2024-11-24T14:42:43Z")

</div>

I recently moved a project from a pi3 to a pi4. Everything seems fines for about 30 mins, then when I try to deploy I get the following; (hmm, I cant paste an image or include a graphic file)  
"Error: Cannot find module '..encodings'  
Require stack:

- /usr/lib/node\_modules/node-red/node\_modules/body-parser//node\_modules/iconv-lite/lib/index.js"  
and about 15 similar lines for read.js, json.js.index.js etc  
once this happens, logging to the log file stops. If I break out of node-red-log and do an ls, I get an error from bash to say the ls is not found. It doesn't recognise any shell command.  
The only way to get out of this is a hard reset of the pi.  
I have tried reinstalling node red with the bash script but it makes no difference.

I have absolutely no idea how to begin debugging this. I hope someone can point me in the right direction.  
gary

---

<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:** [24 November 2024 14:58 UTC](https://discourse.nodered.org/t/weird-node-red-errors-when-working-project-is-running-for-about-30mins/93405/2 "2024-11-24T14:58:26Z")

</div>

Reboot, then, in a command window run  
`sudo journalctl -f`  
do you see any obvious errors?

If not, leave that window open and operate the system normally and see what transpires. I suspect this is a hardware issue of some sort, not directly related to node-red. Most likely a problem with the SD card or PSU.

---

<div class="post-metadata">

**Author:** ![garynl](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/garynl/32/95490_2.png) [@garynl](https://discourse.nodered.org/u/garynl)\
**Post date:** [25 November 2024 15:36 UTC](https://discourse.nodered.org/t/weird-node-red-errors-when-working-project-is-running-for-about-30mins/93405/3 "2024-11-25T15:36:47Z")

</div>

The first error I came across in the journal was that the zigbee2mqtt herdsman wasn't starting. I put that rights and everything is running hunky dory. Thanks! journalctl will become a regular tool!

---

<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:** [9 December 2024 15:37 UTC](https://discourse.nodered.org/t/weird-node-red-errors-when-working-project-is-running-for-about-30mins/93405/4 "2024-12-09T15:37:02Z")

</div>

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