# Node-red-start on raspberry pi not working

**URL:** <https://discourse.nodered.org/t/node-red-start-on-raspberry-pi-not-working/185>\
**Category:** General\
**Created:** [15 May 2018 16:40 UTC](https://discourse.nodered.org/t/node-red-start-on-raspberry-pi-not-working/185 "2018-05-15T16:40:28Z")\
**Posts on this page:** 12\
**Page:** 2

<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:** [23 December 2018 16:28 UTC](https://discourse.nodered.org/t/node-red-start-on-raspberry-pi-not-working/185/21 "2018-12-23T16:28:12Z")

</div>

> [@StrongTown](#):
>
> I wonder now why it says 'nodered' not installed?

It says the _package_ nodered is not installed. That is the apt package, so that is correct.

If you are not using nodejs for anything other than node red then try @cymplecy's suggestion. If you are using nodejs for something else then, as @knolleary says, that will remove all your globally installed nodes so you might not want to do that.

---

<div class="post-metadata">

**Author:** ![StrongTown](https://avatars.discourse-cdn.com/v4/letter/s/4bbf92/32.png) [@StrongTown](https://discourse.nodered.org/u/StrongTown)\
**Post date:** [23 December 2018 17:42 UTC](https://discourse.nodered.org/t/node-red-start-on-raspberry-pi-not-working/185/22 "2018-12-23T17:42:17Z")

</div>

I have tried the `sudo rm -rf /usr/*` and it did not help.

Is there a way to just completely remove NR, npm and nvm and install the latest version(s) from scratch (in the most ideal filing arrangement)? (tho 'nvm' has yet to do much for me).

Also, each time I try an upgrade the .bashrc file gets sooo big, it interferes with NR operation because I use exec nodes to call Cepstral `swift` for voice a lot (or omxplayer) and when there are many calls (like a verbal countdown to turn off the alarm upon re-entry) a large .bashrc file causes the ram to fill til the system crashes. So I often must restore a default .bashrc using `cp /etc/skel/.bashrc ~/`

I can tell it's too large when I launch LXTerminal and it takes 4 or 5 seconds to get a prompt.  
st

---

<div class="post-metadata">

**Author:** ![ukmoose](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/ukmoose/32/13_2.png) [@ukmoose](https://discourse.nodered.org/u/ukmoose)\
**Post date:** [23 December 2018 18:01 UTC](https://discourse.nodered.org/t/node-red-start-on-raspberry-pi-not-working/185/23 "2018-12-23T18:01:26Z")

</div>

The command you ran

> [@StrongTown](#):
>
> sudo rm -rf /usr/\*

wasn’t what anyone in this thread suggested. Did you check whatelse you were deleting prior to running it?

---

<div class="post-metadata">

**Author:** ![dceejay](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/dceejay/32/38_2.png) [@dceejay](https://discourse.nodered.org/u/dceejay)\
**Post date:** [23 December 2018 18:21 UTC](https://discourse.nodered.org/t/node-red-start-on-raspberry-pi-not-working/185/24 "2018-12-23T18:21:57Z")

</div>

hmm- indeed - if you really did delete everything in /usr - you may indeed be in a world of pain any sec... (ie start over completely territory)... but fingers crossed you didn't.

So - the best thing (imho) from where you are now would be to remove nvm - and then just use the system nodejs... and then run the Node-RED upgrade script as per the Raspberry Pi docs - that will get you to nodejs 10 anyway and latest Node-RED that should then start and stop as required.

---

<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:** [23 December 2018 20:14 UTC](https://discourse.nodered.org/t/node-red-start-on-raspberry-pi-not-working/185/25 "2018-12-23T20:14:41Z")

</div>

> [@StrongTown](#):
>
> Also, each time I try an upgrade the .bashrc file gets sooo big,

Do you mean that running the pi upgrade script makes .bashrc grow? That should not happen. What do you end up with in it?

---

<div class="post-metadata">

**Author:** ![StrongTown](https://avatars.discourse-cdn.com/v4/letter/s/4bbf92/32.png) [@StrongTown](https://discourse.nodered.org/u/StrongTown)\
**Post date:** [23 December 2018 20:46 UTC](https://discourse.nodered.org/t/node-red-start-on-raspberry-pi-not-working/185/26 "2018-12-23T20:46:59Z")

</div>

If it happens again I'll post a copy of it. Unfortunately I don't have a 'bad' .bashrc example just now.

dceejay I only used the asterik to just (poorly) indicate I used both the commands, not that I used that exact command. My bad in miss leading you, sorry.

---

<div class="post-metadata">

**Author:** ![dceejay](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/dceejay/32/38_2.png) [@dceejay](https://discourse.nodered.org/u/dceejay)\
**Post date:** [23 December 2018 22:09 UTC](https://discourse.nodered.org/t/node-red-start-on-raspberry-pi-not-working/185/27 "2018-12-23T22:09:36Z")

</div>

phew ! I think you'll find it is nvm that adds to .bashrc

---

<div class="post-metadata">

**Author:** ![StrongTown](https://avatars.discourse-cdn.com/v4/letter/s/4bbf92/32.png) [@StrongTown](https://discourse.nodered.org/u/StrongTown)\
**Post date:** [23 December 2018 22:30 UTC](https://discourse.nodered.org/t/node-red-start-on-raspberry-pi-not-working/185/28 "2018-12-23T22:30:28Z")

</div>

As usual, you are correct as I just reinstalled nvm and the delay is back.

---

<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:** [24 December 2018 07:02 UTC](https://discourse.nodered.org/t/node-red-start-on-raspberry-pi-not-working/185/29 "2018-12-24T07:02:13Z")

</div>

Why do you need nvm? it seems likely that it is the cause of many of your problems.

---

<div class="post-metadata">

**Author:** ![StrongTown](https://avatars.discourse-cdn.com/v4/letter/s/4bbf92/32.png) [@StrongTown](https://discourse.nodered.org/u/StrongTown)\
**Post date:** [24 December 2018 14:22 UTC](https://discourse.nodered.org/t/node-red-start-on-raspberry-pi-not-working/185/30 "2018-12-24T14:22:50Z")

</div>

I think you're right Colin. I think I'll use npm and the pallet manager from here on in and delete nvm. I started using it because I read it would make managing NR "easier".  
st

---

<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:** [24 December 2018 15:28 UTC](https://discourse.nodered.org/t/node-red-start-on-raspberry-pi-not-working/185/31 "2018-12-24T15:28:10Z")

</div>

> [@StrongTown](#):
>
> I read it would make managing NR "easier".

Apparently some strange new use of the word 'easier' with which I am not familiar.

---

<div class="post-metadata">

**Author:** ![StrongTown](https://avatars.discourse-cdn.com/v4/letter/s/4bbf92/32.png) [@StrongTown](https://discourse.nodered.org/u/StrongTown)\
**Post date:** [24 December 2018 16:28 UTC](https://discourse.nodered.org/t/node-red-start-on-raspberry-pi-not-working/185/32 "2018-12-24T16:28:15Z")

</div>

I took the statement to mean nvm makes life easier to manage upgrading as new (stable) node.js (and npm) versions are released and older v's reach eol. As I get more familiar with NR, I now believe their statement meant to manage versions of node.js on a given machine, to "hop" from one version to another, perhaps to test a new node or app across various (earlier) releases (but just my guess). They should however be more clear that it is not of value for the average Joe.

[Previous page](https://discourse.nodered.org/t/node-red-start-on-raspberry-pi-not-working/185.md?page=1)