# Deploy too long in a Raspberry device

**URL:** <https://discourse.nodered.org/t/deploy-too-long-in-a-raspberry-device/93798>\
**Category:** General\
**Created:** [9 December 2024 10:08 UTC](https://discourse.nodered.org/t/deploy-too-long-in-a-raspberry-device/93798 "2024-12-09T10:08:41Z")\
**Posts on this page:** 17\
**Page:** 1

<div class="post-metadata">

**Author:** ![bobfield](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/bobfield/32/83723_2.png) [@bobfield](https://discourse.nodered.org/u/bobfield)\
**Post date:** [9 December 2024 10:08 UTC](https://discourse.nodered.org/t/deploy-too-long-in-a-raspberry-device/93798/1 "2024-12-09T10:08:41Z")

</div>

Hi Dears,

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

Thanks,

Roberto

---

<div class="post-metadata">

**Author:** ![TotallyInformation](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/totallyinformation/32/31_2.png) [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)\
**Post date:** [9 December 2024 10:36 UTC](https://discourse.nodered.org/t/deploy-too-long-in-a-raspberry-device/93798/2 "2024-12-09T10:36:40Z")

</div>

Have you checked the Node-RED log for issues?

> [@bobfield](#):
>
> Node-Red Version: 1.2.9  
> Node.JS Version: 10.23.1

These are extremely old versions that should no longer be in use.

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [9 December 2024 10:52 UTC](https://discourse.nodered.org/t/deploy-too-long-in-a-raspberry-device/93798/3 "2024-12-09T10:52:32Z")

</div>

Also run `top` in a command window to see if anything is hogging the processor.

---

<div class="post-metadata">

**Author:** ![zenofmud](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/zenofmud/32/316_2.png) [@zenofmud](https://discourse.nodered.org/u/zenofmud)\
**Post date:** [9 December 2024 11:12 UTC](https://discourse.nodered.org/t/deploy-too-long-in-a-raspberry-device/93798/4 "2024-12-09T11:12:22Z")

</div>

What setting on the `Deploy` tab have you set?

 ![Screenshot 2024-12-09 at 6.10.21 AM](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/2/3/23a0ccf4f5a6c816b65e730ef2c506b30658876b.png)

If it is 'Full' try changing it to 'Modified Floos' and see if that makes a difference.

---

<div class="post-metadata">

**Author:** ![bobfield](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/bobfield/32/83723_2.png) [@bobfield](https://discourse.nodered.org/u/bobfield)\
**Post date:** [9 December 2024 17:46 UTC](https://discourse.nodered.org/t/deploy-too-long-in-a-raspberry-device/93798/5 "2024-12-09T17:46:47Z")

</div>

Thanks Julian,

I will update the version to the latest version.

---

<div class="post-metadata">

**Author:** ![bobfield](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/bobfield/32/83723_2.png) [@bobfield](https://discourse.nodered.org/u/bobfield)\
**Post date:** [9 December 2024 17:48 UTC](https://discourse.nodered.org/t/deploy-too-long-in-a-raspberry-device/93798/6 "2024-12-09T17:48:44Z")

</div>

Thanks Paul,

I was already using the 'Modified Flows' option. But the time was too long also with this option.

---

<div class="post-metadata">

**Author:** ![gerry](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/gerry/32/21604_2.png) [@gerry](https://discourse.nodered.org/u/gerry)\
**Post date:** [9 December 2024 17:58 UTC](https://discourse.nodered.org/t/deploy-too-long-in-a-raspberry-device/93798/7 "2024-12-09T17:58:18Z")

</div>

Have you ruled out network latency? I occasionally have the same issue with a device and figured out rebooting my router fixed it.

---

<div class="post-metadata">

**Author:** ![bobfield](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/bobfield/32/83723_2.png) [@bobfield](https://discourse.nodered.org/u/bobfield)\
**Post date:** [10 December 2024 09:28 UTC](https://discourse.nodered.org/t/deploy-too-long-in-a-raspberry-device/93798/8 "2024-12-10T09:28:07Z")

</div>

Thanks everyone. I installed version 4.05 of Node-Red and 18.20.5 of node.js on Raspberry and everything worked. Deployment time is now immediate.

Best Regards,

Roberto

---

<div class="post-metadata">

**Author:** ![bobfield](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/bobfield/32/83723_2.png) [@bobfield](https://discourse.nodered.org/u/bobfield)\
**Post date:** [10 December 2024 19:33 UTC](https://discourse.nodered.org/t/deploy-too-long-in-a-raspberry-device/93798/9 "2024-12-10T19:33:02Z")

</div>

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?

---

<div class="post-metadata">

**Author:** ![Steve-Mcl](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/steve-mcl/32/4826_2.png) [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)\
**Post date:** [10 December 2024 20:28 UTC](https://discourse.nodered.org/t/deploy-too-long-in-a-raspberry-device/93798/10 "2024-12-10T20:28:49Z")

</div>

Did you use the official installer script?

---

<div class="post-metadata">

**Author:** ![bobfield](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/bobfield/32/83723_2.png) [@bobfield](https://discourse.nodered.org/u/bobfield)\
**Post date:** [10 December 2024 21:22 UTC](https://discourse.nodered.org/t/deploy-too-long-in-a-raspberry-device/93798/11 "2024-12-10T21:22:09Z")

</div>

I think so. I used 'npm install -g --unsafe-perm node-red'

---

<div class="post-metadata">

**Author:** ![jbudd](https://avatars.discourse-cdn.com/v4/letter/j/5f8ce5/32.png) [@jbudd](https://discourse.nodered.org/u/jbudd)\
**Post date:** [10 December 2024 21:29 UTC](https://discourse.nodered.org/t/deploy-too-long-in-a-raspberry-device/93798/12 "2024-12-10T21:29:36Z")

</div>

That does not seem to be the official Raspberry Pi install script as described at [https://nodered.org/docs/getting-started/raspberrypi](https://nodered.org/docs/getting-started/raspberrypi)

---

<div class="post-metadata">

**Author:** ![bobfield](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/bobfield/32/83723_2.png) [@bobfield](https://discourse.nodered.org/u/bobfield)\
**Post date:** [10 December 2024 22:50 UTC](https://discourse.nodered.org/t/deploy-too-long-in-a-raspberry-device/93798/13 "2024-12-10T22:50:20Z")

</div>

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'

---

<div class="post-metadata">

**Author:** ![jbudd](https://avatars.discourse-cdn.com/v4/letter/j/5f8ce5/32.png) [@jbudd](https://discourse.nodered.org/u/jbudd)\
**Post date:** [10 December 2024 23:11 UTC](https://discourse.nodered.org/t/deploy-too-long-in-a-raspberry-device/93798/14 "2024-12-10T23:11:58Z")

</div>

> [@bobfield](#):
>
> 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.

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [11 December 2024 07:13 UTC](https://discourse.nodered.org/t/deploy-too-long-in-a-raspberry-device/93798/15 "2024-12-11T07:13:50Z")

</div>

> [@bobfield](#):
>
> when I run the script node-red-start it seems that it does not find the executable file

Post the log file that the installer should have created, `/var/log/nodered-install.log` or something similar, I am on my phone so can't check.

---

<div class="post-metadata">

**Author:** ![bobfield](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/bobfield/32/83723_2.png) [@bobfield](https://discourse.nodered.org/u/bobfield)\
**Post date:** [11 December 2024 08:25 UTC](https://discourse.nodered.org/t/deploy-too-long-in-a-raspberry-device/93798/16 "2024-12-11T08:25:36Z")

</div>

Dears,

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.

Thanks everyone,

Roberto

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/d073cd938eafa2e558d7c2cd59003b3ef4963033.png) [@system](https://discourse.nodered.org/u/system)\
**Post date:** [25 December 2024 08:26 UTC](https://discourse.nodered.org/t/deploy-too-long-in-a-raspberry-device/93798/17 "2024-12-25T08:26:07Z")

</div>

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.