yes did not see it under Top, but found it under ps
root 1120 1 0 12:06 ? 00:00:00 /bin/sh /snap/node-red/503/bin/startNR
pieter@pieter-Lenovo-YOGA-730-15IKB:~$ sudo systemctl status nodered
[sudo] password for pieter:
Unit nodered.service could not be found.
pieter@pieter-Lenovo-YOGA-730-15IKB:~$ sudo systemctl status node-red
Unit node-red.service could not be found.
YES and did find it.
root 1231 1120 0 12:06 ? 00:00:10 node-red
Could not find the commands even after doing a search.
Start and stop node-red
" ```
node-red-stop
node-red-start
Blockquote
pieter@pieter-Lenovo-YOGA-730-15IKB:~$ sudo systemctl start node-red
Failed to start node-red.service: Unit node-red.service not found.
pieter@pieter-Lenovo-YOGA-730-15IKB:~$ sudo systemctl start nodered
Failed to start nodered.service: Unit nodered.service not found.
Blockquote
In that case I have no idea how the snap install runs it. I don't install like that, I use the Pi install which also works well for Ubuntu. So in your situation I would uninstall the existing node-red the run the install script from this link. Then we will all know how it should work.
https://nodered.org/docs/getting-started/raspberrypi
[Edit] If you do that then I suggest removing your .node-red folder before you run the script, in case node-red running as root has messed up the file permissions in that folder, which I think quite likely.
Thanks looks like the only option left
Ok Solved. It seems like installing from the cmd prompt via the link above solved the file access issues. File content can now be read without any changes.
ah - right (sorry to be late to the party) - when running as a snap - it runs in a protected container - so does not have access to the general filing system. You can relax this by running it in --classic mode. (but that is kind of not what snaps are about... but hey)
