Closed Kaldesh84 closed 1 year ago
Hi ...strange. Somehow npm sems to have messed up your package tree.
... you can try to stop the adapter, then delete "/opt/iobroker/node_modues/iobroker.node-red" completely with all subdirs and then start adapter again. Iobroker dfetect that it is missing and try to install anything needed. Maybe that fixes it?
For the downgrade error here should be a line more then you posted where he tells you what is "existing that should not be there" ... and then pot. follow https://forum.iobroker.net/topic/57337/fehler-25-bei-adapter-install-update-mit-npm8
Yes, I misread the error with the downgrade.
The problem was not that npm couldn't rename the folders to the temp version. The temp version with the same name was already existing. I expected that the suffix was random each time, but it's not. So npm tried using the already existing temp folder that was not cleaned up from the first 4.0.0 installation that seems to have gone completely wrong for whatever reason.
Once I deleted all of them, I tried reinstalling version 4.0.0 via the "Install specific version" option in Admin with 4.0.0 which was successful.
Thanks for your help
Hi,
after updating to 4.0.0, the node-red adapter is caught in a restart loop with this error message:
I installed the version manually and restarted adapter, iobroker and even the host to no effect. I also can't install the lower version now, it seems npm isn't allowed to rename any folders.
Node.js version: 16.17.0 js-controller version: 4.0.23