I have a node-red application running successfully on a Raspbian in a Raspberry PI 4. The problem is that when I make any change to a flow or subflow it takes a long time to complete the deployment (15 minutes). Running on my notebook, the deployment is immediate. Any suggestions? Below some information about.
Device: Raspberry PI-4
Memory: 6.42GB Free: 2.71GB
SD Card: 53GB Used: 3.6GB
Other tasks:None
Node-Red Version: 1.2.9
Node.JS Version: 10.23.1
Flows: Read data from PLC and insert into MS-SQL-Server Tables
Deploy Type Used: Modified Nodes
In my previous installation I had node-red starting automatically with the raspberry boot. In this new installation, even repeating the same commands I can't get it to execute. It gives the following error: 'Process: 572 ExecStart=/usr/bin/env node-red-pi (code=exited, status=127)'. Any suggestions?
I reinstalled node-red with this oficial script, but when I run the script node-red-start it seems that it does not find the executable file. Shows the message '/usr/bin/env: ‘node-red’: No such file or directory'
There are several possible ways that Node-red can be started: /etc/systemd/system/multi-user.target.wants/nodered.service executes /usr/bin/env node-red-pi /usr/bin/node-red-start executes node-red-pi /usr/bin/node-red-pi executes /usr/bin/env node <some jiggery-pokery with the path>/red.js
and node-red is interpreted by node and seems to do <some (different) jiggerypokery>/red.js
I can't see where the message you report comes from.
I discovered the problem. I had installed NVM. And in one of the error logs there was a message saying that start at boot does not work with NVM. I reinstalled Node-Red without NVM and it worked.