# An issue after upgrading to 4.0 (Solved)

**URL:** <https://discourse.nodered.org/t/an-issue-after-upgrading-to-4-0-solved/89055>\
**Category:** General\
**Created:** [28 June 2024 17:04 UTC](https://discourse.nodered.org/t/an-issue-after-upgrading-to-4-0-solved/89055 "2024-06-28T17:04:24Z")\
**Posts on this page:** 11\
**Page:** 1

<div class="post-metadata">

**Author:** ![ebolisa](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/ebolisa/32/89203_2.png) [@ebolisa](https://discourse.nodered.org/u/ebolisa)\
**Post date:** [28 June 2024 17:04 UTC](https://discourse.nodered.org/t/an-issue-after-upgrading-to-4-0-solved/89055/1 "2024-06-28T17:04:24Z")

</div>

Hi,

I just updated node/nodejs from ver 18 to 20 and nodered to 4.0.

Via ssh, when I issue `sudo systemctl status nodered.service`, the system (rpi 4) reboots.

When I connect to the server, with a browser, via port 1880, I can see and manipulate my flows.

When I check `nodered -v`, I get:

> 28 Jun 18:44:52 - [info]
> 
> # Welcome to Node-RED
> 
> 28 Jun 18:44:52 - [info] Node-RED version: v4.0.1  
> 28 Jun 18:44:52 - [info] Node.js version: v20.15.0  
> 28 Jun 18:44:52 - [info] Linux 6.6.31+rpt-rpi-v8 arm64 LE  
> 28 Jun 18:44:53 - [info] Loading palette nodes  
> 28 Jun 18:44:55 - [info] Dashboard version 3.6.5 started at /ui  
> 28 Jun 18:44:57 - [info] Settings file : /home/pi/.node-red/settings.js  
> 28 Jun 18:44:57 - [info] Context store : 'default' [module=localfilesystem]  
> 28 Jun 18:44:57 - [info] User directory : /home/pi/.node-red  
> 28 Jun 18:44:57 - [warn] Projects disabled : editorTheme.projects.enabled=false  
> 28 Jun 18:44:57 - [info] Flows file : /home/pi/.node-red/flows.json  
> 28 Jun 18:44:57 - [error] Unable to listen on [http://127.0.0.1:1880/](http://127.0.0.1:1880/)  
> 28 Jun 18:44:57 - [error] Error: port in use

and when I check on the ports, I get:

> sudo netstat -tulpn | grep LISTEN  
> tcp 0 0 0.0.0.0:8080 0.0.0.0:\* LISTEN 1144/mjpg\_streamer  
> tcp 0 0 0.0.0.0:1883 0.0.0.0:\* LISTEN 824/mosquitto  
> tcp 0 0 0.0.0.0:1880 0.0.0.0:\* LISTEN 625/node-red  
> tcp 0 0 0.0.0.0:5900 0.0.0.0:\* LISTEN 850/vncserver-x11-c  
> tcp 0 0 0.0.0.0:22 0.0.0.0:\* LISTEN 927/sshd: /usr/sbin  
> tcp 0 0 0.0.0.0:5000 0.0.0.0:\* LISTEN 1150/python  
> tcp6 0 0 :::8080 :::\* LISTEN 1144/mjpg\_streamer  
> tcp6 0 0 :::1883 :::\* LISTEN 824/mosquitto  
> tcp6 0 0 :::5900 :::\* LISTEN 850/vncserver-x11-c  
> tcp6 0 0 :::80 :::\* LISTEN 1617/apache2  
> tcp6 0 0 :::22 :::\* LISTEN 927/sshd: /usr/sbin  
> tcp6 0 0 :::443 :::\* LISTEN 1617/apache2  
> tcp6 0 0 ::1:8888 :::\* LISTEN 661/pigpiod  
> tcp6 0 0 :::5000 :::\* LISTEN 1150/python

Having said that, what else should I check to see what's causing the reboot?

TIA

UPDATE

Issued a stop/start of the service and the "status" is reporting as designed without causing a reboot.

> pi@piserver:~ $ sudo systemctl disable nodered  
> Removed "/etc/systemd/system/multi-user.target.wants/nodered.service".  
> pi@piserver:~ $ sudo systemctl enable nodered  
> Created symlink /etc/systemd/system/multi-user.target.wants/nodered.service → /lib/systemd/system/nodered.service.

---

<div class="post-metadata">

**Author:** ![GogoVega](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/gogovega/32/71313_2.png) [@GogoVega](https://discourse.nodered.org/u/GogoVega)\
**Post date:** [28 June 2024 17:13 UTC](https://discourse.nodered.org/t/an-issue-after-upgrading-to-4-0-solved/89055/2 "2024-06-28T17:13:11Z")

</div>

Hi, it's `node-red --version`

---

<div class="post-metadata">

**Author:** ![ebolisa](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/ebolisa/32/89203_2.png) [@ebolisa](https://discourse.nodered.org/u/ebolisa)\
**Post date:** [28 June 2024 17:15 UTC](https://discourse.nodered.org/t/an-issue-after-upgrading-to-4-0-solved/89055/3 "2024-06-28T17:15:38Z")

</div>

Correct, thank you!

`node-red -version`

> Node-RED v4.0.1  
> Node.js v20.15.0  
> Linux 6.6.31+rpt-rpi-v8 arm64 LE

---

<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:** [28 June 2024 17:22 UTC](https://discourse.nodered.org/t/an-issue-after-upgrading-to-4-0-solved/89055/4 "2024-06-28T17:22:06Z")

</div>

> [@ebolisa](#):
>
> sudo systemctr status nodered.service

That should be `systemctl`

The port in use message is probably because node red is already running.

---

<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:** [28 June 2024 17:23 UTC](https://discourse.nodered.org/t/an-issue-after-upgrading-to-4-0-solved/89055/5 "2024-06-28T17:23:22Z")

</div>

> [@ebolisa](#):
>
> when I issue `sudo systemctr status nodered.service`, the system (rpi 4) reboots

The command is systemctl not systemctr.  
What happens if you run  
`systemctl status nodered` ? (ie no sudo, `.service` is unnecessary)

What does `which systemctr` show you?

---

<div class="post-metadata">

**Author:** ![ebolisa](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/ebolisa/32/89203_2.png) [@ebolisa](https://discourse.nodered.org/u/ebolisa)\
**Post date:** [28 June 2024 17:26 UTC](https://discourse.nodered.org/t/an-issue-after-upgrading-to-4-0-solved/89055/6 "2024-06-28T17:26:40Z")

</div>

It's a typo. Edited, thank you!

---

<div class="post-metadata">

**Author:** ![ebolisa](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/ebolisa/32/89203_2.png) [@ebolisa](https://discourse.nodered.org/u/ebolisa)\
**Post date:** [28 June 2024 17:28 UTC](https://discourse.nodered.org/t/an-issue-after-upgrading-to-4-0-solved/89055/7 "2024-06-28T17:28:49Z")

</div>

`systemctr` it's a typo.

`systemctl status nodered` reboots.

---

<div class="post-metadata">

**Author:** ![marcus-j-davies](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/marcus-j-davies/32/103435_2.png) [@marcus-j-davies](https://discourse.nodered.org/u/marcus-j-davies)\
**Post date:** [28 June 2024 17:36 UTC](https://discourse.nodered.org/t/an-issue-after-upgrading-to-4-0-solved/89055/8 "2024-06-28T17:36:31Z")

</div>

Anything GPIO related in your flows?

strange that a 'reboot' is happening when restarting Node RED  
Are you using a good Power Supply

---

<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:** [28 June 2024 17:37 UTC](https://discourse.nodered.org/t/an-issue-after-upgrading-to-4-0-solved/89055/9 "2024-06-28T17:37:52Z")

</div>

That is probably an operating system problem not related to Node-red.

What about a fictional service?

```auto
systemctl status nosuch

```

Check in the system log for clues (accessing the system log depends on your OS version. It used to be /var/log/syslog, now it's `journalctl`)

---

<div class="post-metadata">

**Author:** ![ebolisa](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/ebolisa/32/89203_2.png) [@ebolisa](https://discourse.nodered.org/u/ebolisa)\
**Post date:** [28 June 2024 17:39 UTC](https://discourse.nodered.org/t/an-issue-after-upgrading-to-4-0-solved/89055/10 "2024-06-28T17:39:02Z")

</div>

Yes, it comes from a UPS.

---

<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:** [26 September 2024 17:39 UTC](https://discourse.nodered.org/t/an-issue-after-upgrading-to-4-0-solved/89055/11 "2024-09-26T17:39:48Z")

</div>

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