# Having to reboot RPi after node update

**URL:** <https://discourse.nodered.org/t/having-to-reboot-rpi-after-node-update/62461>\
**Category:** General\
**Created:** [10 May 2022 15:35 UTC](https://discourse.nodered.org/t/having-to-reboot-rpi-after-node-update/62461 "2022-05-10T15:35:20Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![k5map](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/k5map/32/47681_2.png) [@k5map](https://discourse.nodered.org/u/k5map)\
**Post date:** [10 May 2022 15:35 UTC](https://discourse.nodered.org/t/having-to-reboot-rpi-after-node-update/62461/1 "2022-05-10T15:35:20Z")

</div>

When I update any of my installed nodes, I get the message I must restart Node-Red in order for the update to take effort. Ok, no problem so I got and issue "node-red restart" (or do stop then start) but it does not matter because the node-red console still displays the message I need to restart NR. The only way I've been able to clear this message is to reboot the RPi. Do I need to do something different or is message incorrect and I must do a reboot?

---

<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 May 2022 15:45 UTC](https://discourse.nodered.org/t/having-to-reboot-rpi-after-node-update/62461/2 "2022-05-10T15:45:53Z")

</div>

I always use sudo systemctl restart nodered, which I guess is the same.  
The warning goes away when I refresh the browser page.

---

<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:** [10 May 2022 15:49 UTC](https://discourse.nodered.org/t/having-to-reboot-rpi-after-node-update/62461/3 "2022-05-10T15:49:36Z")

</div>

> [@k5map](#):
>
> node-red restart

... will start node-red with a flow called restart which is not what you want... try node-red-reload (or node-red-stop && node-red-start )

---

<div class="post-metadata">

**Author:** ![k5map](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/k5map/32/47681_2.png) [@k5map](https://discourse.nodered.org/u/k5map)\
**Post date:** [10 May 2022 19:19 UTC](https://discourse.nodered.org/t/having-to-reboot-rpi-after-node-update/62461/4 "2022-05-10T19:19:35Z")

</div>

@dceejay ... I did try node-red-stop && node-red-start but that did not result in the message going away.

BUT, when I issued the node-red-restart command, that did the trick! Much thanks.

---

<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:** [9 July 2022 19:20 UTC](https://discourse.nodered.org/t/having-to-reboot-rpi-after-node-update/62461/5 "2022-07-09T19:20:11Z")

</div>

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