Error rc217 or 247. When installing, deleting, updating nodes

General
21

Erorr when install nev node:

2025-03-12T11:28:40.150Z npm install --no-audit --no-update-notifier --no-fund --save --save-prefix=~ --omit=dev --engine-strict node-red-contrib-miio-humidifier@0.9.5
2025-03-12T11:28:51.654Z [err] npm error code ENOTEMPTY
2025-03-12T11:28:51.654Z [err] npm error syscall rename
2025-03-12T11:28:51.654Z [err] npm error path /home/alex/.node-red/node_modules/cronstrue
2025-03-12T11:28:51.654Z [err] npm error dest /home/alex/.node-red/node_modules/.cronstrue-xHrvmzs1
2025-03-12T11:28:51.654Z [err] npm error errno -39
2025-03-12T11:28:51.655Z [err] npm error ENOTEMPTY: directory not empty, rename '/home/alex/.node-red/node_modules/cronstrue' -> '/home/alex/.node-red/node_modules/.cronstrue-xHrvmzs1'
2025-03-12T11:28:51.659Z [err] npm error A complete log of this run can be found in: /home/alex/.npm/_logs/2025-03-12T11_28_40_413Z-debug-0.log
2025-03-12T11:28:51.692Z rc=217
22

That is a different error. It is probably a hangover from the previous issue. Delete the folder /home/alex/.node-red/node_modules/.cronstrue-xHrvmzs1 and any other similarly named folders in node_modules, with the random chars on the end.

[edit] There is something else still wrong though, what do the commands
which node
and
which npm
show?

23 
/usr/local/bin/node
/usr/local/bin/npm
24

Check the timestamps on those. If they were created by the install script then post the node red install log (/var/log/nodered-install.log or something similar). If they are older then delete them, make sure that node -v and npm -v show they are not installed, and run the script again.

What hardware are you running on? Is it an old Arm device?

25 
Started : Срд 12 сак 2025 14:01:28 +03
Running for user alex at /home/alex
Found global nodes:   :

WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

Чтение списков пакетов…
Построение дерева зависимостей…
Чтение информации о состоянии…
E: Невозможно найти пакет nodered
Using n
  installing : node-v20.18.3
       mkdir : /usr/local/n/versions/node/20.18.3
       fetch : https://nodejs.org/dist/v20.18.3/node-v20.18.3-linux-x64.tar.xz
     copying : node/20.18.3
   installed : v20.18.3 (with npm 10.8.2)

Versions: node:v20.18.3 npm:10.8.2
npm warn using --force Recommended protections disabled.
Now install Node-RED 

added 311 packages in 3m
4.0.9
Now create basic package.json for the user and move any global nodes
Running npm rebuild
rebuilt dependencies successfully
Now add the shortcut and start/stop/log scripts to the menu
Now add systemd script and configure it for alex:alex @ /home/alex
ln: не удалось создать символьную ссылку '/usr/bin/python': Файл существует
Now add launcher to top bar, add cpu temp example, make sure ping works
Allow binding to low ports : n
Memory  : 
Started :  Срд 12 сак 2025 14:01:28 +03 
Finished:  Срд 12 сак 2025 14:04:29 +03
26 
HP t630
27

So not only had you used npm to install nodejs, but also n. Seeing that, the script has used n to install nodejs, so that may be ok.

Did deleting the strange named folder fix the install problem?

28

The files were deleted. After the first reboot, everything remained as before. Then there was a forced second reboot and everything worked: installation, removal, updating of nodes. Thanks for the help :handshake: