The Industrial Raspberry Pi Forum

When trying to launch Node red through the revpi status screen I get the following message 'Node-RED service not ready yet ... please retry ...' I've power cycled the revpi connect multiple times and tried disabling and re-enabling Node red with no luck, can anyone point me in the right direction?

Hi beppe2672,

what is the status of the nodered server (systemctl status nodered)? Is there any error message in the logs (sudo journalctl -u nodered)?

Nicolai

Things seem to have got worse since yesterday, the device is no longer accesible via the browser, attempted to reflash the disk image today but RpiBoot isnt even detecting the device. PWR, REL and WD lights are illuminated on the front panel but thats all the device is doing at the moment.

Hello please have a look here:
RevolutionPi RPiBoot Checklist
Node-RED FAQ

Hello,

I have the same problem and here is the info



Aug 15 18:27:34 RevPi25478 systemd[1]: nodered.service: Main process exited, code=exited, status=216/GROUP
Aug 15 18:27:34 RevPi25478 systemd[1]: nodered.service: Failed with result 'exit-code'.
Aug 15 18:27:54 RevPi25478 systemd[1]: nodered.service: Scheduled restart job, restart counter is at 3.
Aug 15 18:27:54 RevPi25478 systemd[1]: Stopped Node-RED graphical event wiring tool.
Aug 15 18:27:54 RevPi25478 systemd[1]: Started Node-RED graphical event wiring tool.
Aug 15 18:27:54 RevPi25478 systemd[3485]: nodered.service: Failed to determine group credentials: No such process
Aug 15 18:27:54 RevPi25478 systemd[3485]: nodered.service: Failed at step GROUP spawning /usr/bin/env: No such process
Aug 15 18:27:54 RevPi25478 systemd[1]: nodered.service: Main process exited, code=exited, status=216/GROUP
Aug 15 18:27:54 RevPi25478 systemd[1]: nodered.service: Failed with result 'exit-code'.
Aug 15 18:28:14 RevPi25478 systemd[1]: nodered.service: Scheduled restart job, restart counter is at 4.
Aug 15 18:28:14 RevPi25478 systemd[1]: Stopped Node-RED graphical event wiring tool.
Aug 15 18:28:14 RevPi25478 systemd[1]: Started Node-RED graphical event wiring tool.
Aug 15 18:28:14 RevPi25478 systemd[3504]: nodered.service: Failed to determine group credentials: No such process
Aug 15 18:28:14 RevPi25478 systemd[3504]: nodered.service: Failed at step GROUP spawning /usr/bin/env: No such process
Aug 15 18:28:14 RevPi25478 systemd[1]: nodered.service: Main process exited, code=exited, status=216/GROUP
Aug 15 18:28:14 RevPi25478 systemd[1]: nodered.service: Failed with result 'exit-code'.
Aug 15 18:28:35 RevPi25478 systemd[1]: nodered.service: Scheduled restart job, restart counter is at 5.
Aug 15 18:28:35 RevPi25478 systemd[1]: Stopped Node-RED graphical event wiring tool.
Aug 15 18:28:35 RevPi25478 systemd[1]: Started Node-RED graphical event wiring tool.
Aug 15 18:28:35 RevPi25478 systemd[3507]: nodered.service: Failed to determine group credentials: No such process
Aug 15 18:28:35 RevPi25478 systemd[3507]: nodered.service: Failed at step GROUP spawning /usr/bin/env: No such process
Aug 15 18:28:35 RevPi25478 systemd[1]: nodered.service: Main process exited, code=exited, status=216/GROUP
Aug 15 18:28:35 RevPi25478 systemd[1]: nodered.service: Failed with result 'exit-code'.
~

Was this ever solved? I have the same issue on a brand-new unit out of the box.

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.

Hi DarylDominique, thank you for your positive feedback and the solution to the problem.

DarylDominique wrote: ↑26 Feb 2024, 23:32 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.

How did you edit the nodered.service file? It only has root permissions to write and I dont know how to change that. I'm also not able to locate it using the terminal only in the file manager in the GUI. Im beginner in this subject so it not working correctly out of the box is a big hurdle. Any help is appreciated.

So i figured out how to edit the nodered.service file in the terminal. Unfortunately i still have the same issue with the error message ;

Node-RED service not ready yet ... please retry ...

not sure what to do now