Issue with Starting Node-RED on RevPi Connect 4

[yuweichong]

Hello Kunbus Forum members, I am encountering a problem with starting Node-RED on my RevPi Connect 4, and I am seeking assistance to resolve the issue.

Error Description:
I am facing difficulties starting up Node-RED, and the system logs are indicating the following errors:
-- Journal begins at Thu 2022-12-22 19:55:42 +08, ends at Wed 2024-02-21 16:12:>
Feb 21 15:31:48 RevPi109301 systemd[1]: Started Node-RED graphical event wiring>
Feb 21 15:31:48 RevPi109301 systemd[4560]: nodered.service: Failed to determine>
Feb 21 15:31:48 RevPi109301 systemd[4560]: nodered.service: Failed at step GROU>
Feb 21 15:31:48 RevPi109301 systemd[1]: nodered.service: Main process exited, c>
Feb 21 15:31:48 RevPi109301 systemd[1]: nodered.service: Failed with result 'ex>
Feb 21 15:32:08 RevPi109301 systemd[1]: nodered.service: Scheduled restart job,>
Feb 21 15:32:08 RevPi109301 systemd[1]: Stopped Node-RED graphical event wiring>
Feb 21 15:32:08 RevPi109301 systemd[1]: Started Node-RED graphical event wiring>
Feb 21 15:32:08 RevPi109301 systemd[4936]: nodered.service: Failed to determine>
Feb 21 15:32:08 RevPi109301 systemd[4936]: nodered.service: Failed at step GROU>
Feb 21 15:32:08 RevPi109301 systemd[1]: nodered.service: Main process exited, c>
Feb 21 15:32:08 RevPi109301 systemd[1]: nodered.service: Failed with result 'ex>
Feb 21 15:32:28 RevPi109301 systemd[1]: nodered.service: Scheduled restart job,>
Feb 21 15:32:28 RevPi109301 systemd[1]: Stopped Node-RED graphical event wiring>
Feb 21 15:32:28 RevPi109301 systemd[1]: Started Node-RED graphical event wiring>
Feb 21 15:32:28 RevPi109301 systemd[5033]: nodered.service: Failed to determine>
Feb 21 15:32:28 RevPi109301 systemd[5033]: nodered.service: Failed at step GROU>
Feb 21 15:32:28 RevPi109301 systemd[1]: nodered.service: Main process exited, c>
Feb 21 15:32:28 RevPi109301 systemd[1]: nodered.service: Failed with result 'ex>
Feb 21 15:32:49 RevPi109301 systemd[1]: nodered.service: Scheduled restart job,>
Feb 21 15:32:49 RevPi109301 systemd[1]: Stopped Node-RED graphical event wiring>
Feb 21 15:32:49 RevPi109301 systemd[1]:

And also:
"Node-red service not ready yet... please retry....." When I click start the Nodered on RevPi website

Additional Information:
I have attempted multiple restarts without success, and the service seems to be reporting that it is not ready yet. If anyone has encountered a similar problem or has insights into troubleshooting Node-RED startup issues on the RevPi Connect 4, I would greatly appreciate your assistance.

Thank you for your time and expertise.

[dirk]

Hi yuweichong, are you using a lite image and which kernel do you have - can you run the following commands:

Code: Select all

pi@RevPi39627:~ $ cat /etc/revpi/image-release
2023-09-26-revpi-bullseye-armhf-lite.img
pi@RevPi39627:~ $ uname -a
Linux RevPi39627 6.1.46-rt13-v7 #1 SMP PREEMPT_RT Mon, 5 Feb 2024 15:02:39 +0100 armv7l GNU/Linux

You can use the following checklist to carry out the necessary steps to bring Node-RED up to date:
Node-RED Checklist

It's been a while, but since the first release of Bullseys in June 2023, Node-RED has been integrated differently than before. The changes are included in the release notes RevPi Bullseye / Bullseye Lite (06/2023) (ID: 6999).

[DarylDominique]

Hello Kunbus Forum members, I am encountering a problem with starting Node-RED on my RevPi Connect 4, and I am seeking assistance to resolve the issue.

Error Description:
I am facing difficulties starting up Node-RED, and the system logs are indicating the following errors:
-- Journal begins at Thu 2022-12-22 19:55:42 +08, ends at Wed 2024-02-21 16:12:>
Feb 21 15:31:48 RevPi109301 systemd[1]: Started Node-RED graphical event wiring>
Feb 21 15:31:48 RevPi109301 systemd[4560]: nodered.service: Failed to determine>
Feb 21 15:31:48 RevPi109301 systemd[4560]: nodered.service: Failed at step GROU>
Feb 21 15:31:48 RevPi109301 systemd[1]: nodered.service: Main process exited, c>
Feb 21 15:31:48 RevPi109301 systemd[1]: nodered.service: Failed with result 'ex>
Feb 21 15:32:08 RevPi109301 systemd[1]: nodered.service: Scheduled restart job,>
Feb 21 15:32:08 RevPi109301 systemd[1]: Stopped Node-RED graphical event wiring>
Feb 21 15:32:08 RevPi109301 systemd[1]: Started Node-RED graphical event wiring>
Feb 21 15:32:08 RevPi109301 systemd[4936]: nodered.service: Failed to determine>
Feb 21 15:32:08 RevPi109301 systemd[4936]: nodered.service: Failed at step GROU>
Feb 21 15:32:08 RevPi109301 systemd[1]: nodered.service: Main process exited, c>
Feb 21 15:32:08 RevPi109301 systemd[1]: nodered.service: Failed with result 'ex>
Feb 21 15:32:28 RevPi109301 systemd[1]: nodered.service: Scheduled restart job,>
Feb 21 15:32:28 RevPi109301 systemd[1]: Stopped Node-RED graphical event wiring>
Feb 21 15:32:28 RevPi109301 systemd[1]: Started Node-RED graphical event wiring>
Feb 21 15:32:28 RevPi109301 systemd[5033]: nodered.service: Failed to determine>
Feb 21 15:32:28 RevPi109301 systemd[5033]: nodered.service: Failed at step GROU>
Feb 21 15:32:28 RevPi109301 systemd[1]: nodered.service: Main process exited, c>
Feb 21 15:32:28 RevPi109301 systemd[1]: nodered.service: Failed with result 'ex>
Feb 21 15:32:49 RevPi109301 systemd[1]: nodered.service: Scheduled restart job,>
Feb 21 15:32:49 RevPi109301 systemd[1]: Stopped Node-RED graphical event wiring>
Feb 21 15:32:49 RevPi109301 systemd[1]:

And also:
"Node-red service not ready yet... please retry....." When I click start the Nodered on RevPi website

Additional Information:
I have attempted multiple restarts without success, and the service seems to be reporting that it is not ready yet. If anyone has encountered a similar problem or has insights into troubleshooting Node-RED startup issues on the RevPi Connect 4, I would greatly appreciate your assistance.

Thank you for your time and expertise.

I had this issue on two Revolution Pi Connect 4s recently and was able to resolve it on both with the same method thankfully. Like you, trying to enable Node-Red in the browser based GUI did not function, and the system reported "Service is not ready. Please wait" on any attempt to launch Node-Red after enabling the services, including after a number of reboots.

I dove into the corresponding journalctl file and found that the service status showed an exit code with a 216/GROUP error resulting in a constant activating loop. Adjusting the nodered.service file at /lib/systemd/system/nodered.service and removing the "Group=pi" line resolved the issue.

Node-Red has now been working reliably on the RevPi Connect 4 and without any further issues.

Let me know if that helps!

[yuweichong]

Hi Daryl, may I know are you able to save the file after you removed the Group=pi line? I am having a permission denied problem.

[yuweichong]

Hi yuweichong, are you using a lite image and which kernel do you have - can you run the following commands:

Code: Select all

pi@RevPi39627:~ $ cat /etc/revpi/image-release
2023-09-26-revpi-bullseye-armhf-lite.img
pi@RevPi39627:~ $ uname -a
Linux RevPi39627 6.1.46-rt13-v7 #1 SMP PREEMPT_RT Mon, 5 Feb 2024 15:02:39 +0100 armv7l GNU/Linux

You can use the following checklist to carry out the necessary steps to bring Node-RED up to date:
Node-RED Checklist

It's been a while, but since the first release of Bullseys in June 2023, Node-RED has been integrated differently than before. The changes are included in the release notes RevPi Bullseye / Bullseye Lite (06/2023) (ID: 6999).

Hi Dirk, thank you for your reply.
pi@RevPi109301:~ $ cat /etc/revpi/image-release
2023-07-28-revpi-bullseye-arm64.img
pi@RevPi109301:~ $ uname -a
Linux RevPi109301 6.1.46-rt13-v8 #1 SMP PREEMPT_RT Mon, 5 Feb 2024 15:02:39 +0100 aarch64 GNU/Linux

This is what I observed after I run the code you suggested. May I know arm64 is lite image or full image?

[DarylDominique]

Hi Daryl, may I know are you able to save the file after you removed the Group=pi line? I am having a permission denied problem.

It does require elevated permissions to edit the file. I did the following:

• Sign into the pi command line (Via SSH or on the pi itself, whatever you're using)
• type

  Code: Select all

  sudo nano /lib/systemd/system/nodered.service

  and hit "Enter". It may prompt you to re-enter your password.
• Find and remove the "Group=pi" line.
• CTRL+X to Save and Close. It will prompt you Y or N to save the buffer, hit Y. It will then list the file name to write, just hit "Enter" to overwrite the file with your edits.
• Reboot the pi and you should be able to use Node-Red as expected.