# Node red crashes caused of illegal operation

**URL:** <https://discourse.nodered.org/t/node-red-crashes-caused-of-illegal-operation/84218>\
**Category:** General\
**Created:** [2 January 2024 18:39 UTC](https://discourse.nodered.org/t/node-red-crashes-caused-of-illegal-operation/84218 "2024-01-02T18:39:26Z")\
**Posts on this page:** 12\
**Page:** 1

<div class="post-metadata">

**Author:** ![WernerM96](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/wernerm96/32/46471_2.png) [@WernerM96](https://discourse.nodered.org/u/WernerM96)\
**Post date:** [2 January 2024 18:39 UTC](https://discourse.nodered.org/t/node-red-crashes-caused-of-illegal-operation/84218/1 "2024-01-02T18:39:26Z")

</div>

Hey,

i get these message.

> 2 Jan 19:35:11 - [red] Uncaught Exception:  
> 2 Jan 19:35:11 - [error] Error: EISDIR: illegal operation on a directory, open '/home/pi/.node-red/node\_modules/node-persist/persist/persist'  
> nodered.service: Main process exited, code=exited, status=1/FAILURE  
> nodered.service: Failed with result 'exit-code'.  
> nodered.service: Consumed 1min 34.672s CPU time.

I tried to reinstall (upgrade) node-red but it doesnt work.  
Can anybody help me and knows whats to do? This program works a long time before so i didnt know what the problem is.

Best regards!

---

<div class="post-metadata">

**Author:** ![marcus-j-davies](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/marcus-j-davies/32/103435_2.png) [@marcus-j-davies](https://discourse.nodered.org/u/marcus-j-davies)\
**Post date:** [2 January 2024 18:58 UTC](https://discourse.nodered.org/t/node-red-crashes-caused-of-illegal-operation/84218/2 "2024-01-02T18:58:36Z")

</div>

It would seem a Node RED Node you're using, has an issue.

I am saying this, as the error is originating from the users directory (where your installed Nodes are located)

`/home/pi/.node-red`

Do you have any Node installed, that deals with persistent storage of values?  
what Nodes do you have installed, it would help us to identify the offending Node.

you can try starting Node Red in safe mode (`--safe`)

---

<div class="post-metadata">

**Author:** ![WernerM96](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/wernerm96/32/46471_2.png) [@WernerM96](https://discourse.nodered.org/u/WernerM96)\
**Post date:** [2 January 2024 19:02 UTC](https://discourse.nodered.org/t/node-red-crashes-caused-of-illegal-operation/84218/3 "2024-01-02T19:02:05Z")

</div>

i am storing some values in global/flow set/get. Thats some kind of persitent data. Maybe also some other nodes are using this kind of procedure.

With putty i have no access to this folder. Is this a normal behaviour?

---

<div class="post-metadata">

**Author:** ![marcus-j-davies](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/marcus-j-davies/32/103435_2.png) [@marcus-j-davies](https://discourse.nodered.org/u/marcus-j-davies)\
**Post date:** [2 January 2024 19:08 UTC](https://discourse.nodered.org/t/node-red-crashes-caused-of-illegal-operation/84218/4 "2024-01-02T19:08:05Z")

</div>

Can you share the contents of `/home/pi/.node-red/package.json`

run in terminal/putty  
`cat /home/pi/.node-red/package.json`

Or start Node RED in safe mode `--safe`

> [@WernerM96](#):
>
> With putty i have no access to this folder. Is this a normal behaviour?

its likely hidden

---

<div class="post-metadata">

**Author:** ![WernerM96](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/wernerm96/32/46471_2.png) [@WernerM96](https://discourse.nodered.org/u/WernerM96)\
**Post date:** [2 January 2024 19:10 UTC](https://discourse.nodered.org/t/node-red-crashes-caused-of-illegal-operation/84218/5 "2024-01-02T19:10:38Z")

</div>

--safe -\> in safemode the error also happens

`cat /home/pi/.node-red/package.json`

> {  
> "name": "node-red-project",  
> "description": "initially created for you by Node-RED 1.3.5 ",  
> "version": "0.0.1",  
> "private": true,  
> "dependencies": {  
> "node-red-contrib-alarm": "~1.4.0",  
> "node-red-contrib-boolean-logic-ultimate": "~1.1.1",  
> "node-red-contrib-buffer-parser": "^3.2.2",  
> "node-red-contrib-button-events": "~2.0.0",  
> "node-red-contrib-counter": "~0.1.6",  
> "node-red-contrib-cpu": "0.0.4",  
> "node-red-contrib-device-stats": "~1.1.2",  
> "node-red-contrib-doorbird-ultimate": "github:ihrigb/node-red-contrib-doorbi rd-ultimate",  
> "node-red-contrib-feedparser-extended": "0.0.2",  
> "node-red-contrib-fritz": "~1.4.5",  
> "node-red-contrib-fronius-solar": "~1.0.4",  
> "node-red-contrib-get-feeds": "~1.0.0",  
> "node-red-contrib-google": "~0.2.0",  
> "node-red-contrib-google-calendar": "~0.1.5",  
> "node-red-contrib-google-oauth-calendar": "~0.1.1",  
> "node-red-contrib-ical-events": "~2.2.5",  
> "node-red-contrib-image-tools": "~2.0.4",  
> "node-red-contrib-influxdb": "~0.6.1",  
> "node-red-contrib-journal": "~0.1.6",  
> "node-red-contrib-knx-ultimate": "~2.2.29",  
> "node-red-contrib-msg-resend": "~1.0.0",  
> "node-red-contrib-os": "~0.2.1",  
> "node-red-contrib-play-audio": "^2.5.0",  
> "node-red-contrib-power-monitor": "~1.2.1",  
> "node-red-contrib-presence-faker": "~1.8.8",  
> "node-red-contrib-remote": "~1.5.1",  
> "node-red-contrib-repeat": "0.0.27",  
> "node-red-contrib-telegrambot": "~15.1.7",  
> "node-red-contrib-timeouttrigger": "0.0.4",  
> "node-red-contrib-timerswitch": "~1.4.0",  
> "node-red-contrib-trashschedule": "~1.3.3",  
> "node-red-contrib-ui-artless-gauge": "~0.3.12",  
> "node-red-contrib-ui-led": "~0.4.11",  
> "node-red-contrib-ui-time-scheduler": "~1.17.2",  
> "node-red-contrib-vnc": "~0.1.5",  
> "node-red-contrib-watt2kwh": "~0.1.2",  
> "node-red-contrib-wled": "0.0.4",  
> "node-red-contrib-wled2": "~2.4.4",  
> "node-red-dashboard": "~3.6.1",  
> "node-red-node-base64": "~0.3.0",  
> "node-red-node-feedparser": "~0.3.0",  
> "node-red-node-pi-gpio": "^2.0.6",  
> "node-red-node-ping": "^0.3.3",  
> "node-red-node-random": "^0.4.1",  
> "node-red-node-serialport": "^2.0.2",  
> "node-red-node-smooth": "^0.1.2",  
> "node-red-node-sqlite": "~1.1.0",  
> "node-red-node-ui-iframe": "~0.2.1",  
> "node-red-node-ui-table": "~0.4.3"  
> }  
> }

---

<div class="post-metadata">

**Author:** ![marcus-j-davies](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/marcus-j-davies/32/103435_2.png) [@marcus-j-davies](https://discourse.nodered.org/u/marcus-j-davies)\
**Post date:** [2 January 2024 19:13 UTC](https://discourse.nodered.org/t/node-red-crashes-caused-of-illegal-operation/84218/6 "2024-01-02T19:13:56Z")

</div>

ok do this... (I was hoping for an obvious node 😅 )

```auto
cd /home/pi/.node-red
npm ls node-persist

```

---

<div class="post-metadata">

**Author:** ![WernerM96](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/wernerm96/32/46471_2.png) [@WernerM96](https://discourse.nodered.org/u/WernerM96)\
**Post date:** [2 January 2024 19:22 UTC](https://discourse.nodered.org/t/node-red-crashes-caused-of-illegal-operation/84218/7 "2024-01-02T19:22:10Z")

</div>

> [@marcus-j-davies](#):
>
> `npm ls node-persist`

I did it...but same.  
😃 Hopefully i have not to fully reinstall the pi.

---

<div class="post-metadata">

**Author:** ![marcus-j-davies](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/marcus-j-davies/32/103435_2.png) [@marcus-j-davies](https://discourse.nodered.org/u/marcus-j-davies)\
**Post date:** [2 January 2024 19:22 UTC](https://discourse.nodered.org/t/node-red-crashes-caused-of-illegal-operation/84218/8 "2024-01-02T19:22:41Z")

</div>

what does

```auto
cd /home/pi/.node-red
npm ls node-persist

```

output?

it will list what nodes depend on it

---

<div class="post-metadata">

**Author:** ![WernerM96](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/wernerm96/32/46471_2.png) [@WernerM96](https://discourse.nodered.org/u/WernerM96)\
**Post date:** [2 January 2024 19:24 UTC](https://discourse.nodered.org/t/node-red-crashes-caused-of-illegal-operation/84218/9 "2024-01-02T19:24:20Z")

</div>

node-red-project@0.0.1 /home/pi/.node-red  
└─┬ node-red-contrib-journal@0.1.6  
└── node-persist@0.0.2

i will reinstall the journal node....

---

<div class="post-metadata">

**Author:** ![marcus-j-davies](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/marcus-j-davies/32/103435_2.png) [@marcus-j-davies](https://discourse.nodered.org/u/marcus-j-davies)\
**Post date:** [2 January 2024 19:27 UTC](https://discourse.nodered.org/t/node-red-crashes-caused-of-illegal-operation/84218/10 "2024-01-02T19:27:25Z")

</div>

So there you go...

`node-red-contrib-journal` has caused an issue.

you can get back to your Node RED, by removing it...

```auto
cd /home/pi/.node-red
npm uninstall node-red-contrib-journal

```

then start Node RED again hopefully it will start

Since `--safe` does nothing in this instance.  
for a permanent fix, you may need to raise an issue with the author

---

<div class="post-metadata">

**Author:** ![WernerM96](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/wernerm96/32/46471_2.png) [@WernerM96](https://discourse.nodered.org/u/WernerM96)\
**Post date:** [2 January 2024 19:45 UTC](https://discourse.nodered.org/t/node-red-crashes-caused-of-illegal-operation/84218/11 "2024-01-02T19:45:08Z")

</div>

Thank you very much!

In the moment it looks very good.

---

<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:** [16 January 2024 19:46 UTC](https://discourse.nodered.org/t/node-red-crashes-caused-of-illegal-operation/84218/12 "2024-01-16T19:46:05Z")

</div>

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