Node red crashes caused of illegal operation


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!

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)


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)

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?

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

its likely hidden

--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"

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

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

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

what does

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


it will list what nodes depend on it

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....

So there you go...

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

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

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

Thank you very much!

In the moment it looks very good.

1 Like

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