Just used Manage Palette to upgrade 2 packages, tried to restart the Node-RED service and now getting a nothing error message:
17 Aug 16:40:35 - [info] Upgrading module: node-red-node-rbe to version: 0.2.5
17 Aug 16:41:24 - [info] Upgraded module: node-red-node-rbe. Restart Node-RED to use the new version
17 Aug 16:41:36 - [info] Upgrading module: node-red-node-tail to version: 0.0.3
17 Aug 16:41:53 - [info] Upgraded module: node-red-node-tail. Restart Node-RED to use the new version
Error loading settings file: /home/devuser/.node-red/settings.js
Error loading settings file: /home/devuser/.node-red/settings.js
Error loading settings file: /home/devuser/.node-red/settings.js
Error loading settings file: /home/devuser/.node-red/settings.js
Error loading settings file: /home/devuser/.node-red/settings.js
Error loading settings file: /home/devuser/.node-red/settings.js
Error loading settings file: /home/devuser/.node-red/settings.js
Error loading settings file: /home/devuser/.node-red/settings.js
Haven't changed the settings.js file recently and have restarted the service after the last change. node-red was installed globally with sudo but is run as non-admin, could this be the issue? If so, shouldn't it check for correct permissions first?
You can install a particular version of a node using (from the .node-red directory) npm install package-name@version-number
Though I am not convinced the update is the real cause of the problem. What version of node red, npm and nodejs are you using?
Probably my own inexperience with npm, but what is the proper way to automatically update out-of-date packages? I thought npm update with depth specified was supposed to take care of it.
devuser@freewave-ib:~$ node -v
v12.8.1
devuser@freewave-ib:~$ npm -v
6.10.3
devuser@freewave-ib:~$ cd .node-red/
devuser@freewave-ib:~/.node-red$ npm --depth 9999 update
devuser@freewave-ib:~/.node-red$ npm install node-red-node-rbe@latest
+ node-red-node-rbe@0.2.5
added 1 package from 1 contributor, removed 113 packages and audited 1 package in 37.734s
found 0 vulnerabilities
devuser@freewave-ib:~/.node-red$ npm install node-red-node-tail@latest
+ node-red-node-tail@0.0.3
added 2 packages from 4 contributors and audited 3 packages in 5.928s
found 0 vulnerabilities
devuser@freewave-ib:~/.node-red$
As per the docs the recommended version of nodejs for node-red is currently v8 or v10 not v12
Third party nodes will potentially have a problem with nodejs v12 until underlying libraries are updated.
Although your issue looks like permissions assuming you haven’t edited yourself
@knolleary There's nothing wrong with the settings file. Every time I start fresh with the same file, no errors. Plus, when there's a parse error it usually gives a particular error doesn't it? I've been starting "fresh" by removing everything in the .node-red folder except settings.js and the flow JSON file.
@ukmoose, was the correct way to update the packages in question non-admin as @Colin showed? That's what I did the 2nd time. Node-RED was installed with sudo npm -g --unsafe-perm install node-red as suggested in the docs.
@Colin: yes both times it was running before upgrading.
I have just tried installing node-red-node-rbe@latest (0.2.5) with node red 0.20.7 node 10.16.3 on Ubuntu 19.04 and it is ok.
It would be worth dropping back to node 10.x to see if the problem goes away (in which case it is an issue with the rbe node that will no doubt be addressed).
@Colin, will do, I misread somewhere that v12 support was here but not recommended yet, if it's not really here then I need to go back down to v10 anyway. Thanks for your help.
Anything that does not work with v12 should be submitted as an issue as it needs to be fixed. Your problem may not be that, but it must be ruled out (or in).
