Raspberry pi 3 with node-red

General
1

hi everyone, i am using raspberry pi 3 to use node red, but when i start node red the console shows these errors:

node-red.service: Failed to determine user credentials: No such process
node-red.service: Failed at step USER spawning/usr/bin/env: No such process

Thanks for your help

2

Hi Bomber,

Welcome to the Nodered forum.
How did you installed nr on your pi?
Did you used the installation script as mentioned on this page.

3

Hello,

yes, but it doesn't work

thank you

4

In a terminal run
node-red-stop
node-red-start (note: not node-red start)
and copy/paste the full output here please. Copy/paste, not a screenshot. Use the </> button at the top of the forum entry window when pasting it.

5

Also, have you changed the user name on the pi since you installed node-red? If so then run the script again when logged in as the new user name.

6

Hi Colin,

unfortunately out of desperation I installed everything,
and the errors never come out.
the problem is that I can't connect to the network to nod red,
i saw that there is a npm WARN config global --global, --local are deprecated. Use --location=global instead. nodes to local could that be the problem?
how can i solve?
thank you

 This can take 20-30 minutes on the slower Pi versions - please wait.

Stop Node-RED ✔
Remove old version of Node-RED ✔
Node option not specified : --node14, --node16, or --node18
Leave existing Node.js : v16.16.0 Npm 8.11.0
Clean npm cache -
npm WARN config global `--global`, `--local` are deprecated. Use `--location=global` instead. nodes to local
Install Node-RED core ✔ 3.0.0
Move global nodes to local -
Leave existing nodes -
Install extra Pi nodes ✔
Add shortcut commands ✔
Update systemd script ✔
Any errors will be logged to /var/log/nodered-install.log


All done.
You can now start Node-RED with the command node-red-start
or using the icon under Menu / Programming / Node-RED
Then point your browser to localhost:1880 or http://{your_pi_ip-address}:1880

Started : mer 20 lug 2022, 10:07:59, CEST
Finished: mer 20 lug 2022, 10:09:53, CEST


Start Node-RED

Once Node-RED has started, point a browser at http://192.168.1.16:1880
On Pi Node-RED works better with the Firefox or Chrome browser

Use node-red-stop to stop Node-RED
Use node-red-start to start Node-RED again
Use node-red-log to view the recent log output
Use sudo systemctl enable nodered.service to autostart Node-RED at every boot
Use sudo systemctl disable nodered.service to disable autostart on boot

To find more nodes and example flows - go to http://flows.nodered.org

Starting as a systemd service.
20 Jul 10:16:10 - [info]
Welcome to Node-RED
===================
20 Jul 10:16:10 - [info] Node-RED version: v3.0.0
20 Jul 10:16:10 - [info] Node.js version: v16.16.0
20 Jul 10:16:10 - [info] Linux 5.15.32-v8+ arm64 LE
20 Jul 10:16:13 - [info] Loading palette nodes
20 Jul 10:16:18 - [info] Settings file : /home/simo/.node-red/settings.js
20 Jul 10:16:18 - [info] Context store : 'default' [module=memory]
20 Jul 10:16:18 - [info] User directory : /home/simo/.node-red
20 Jul 10:16:18 - [warn] Projects disabled : editorTheme.projects.enabled=false
20 Jul 10:16:18 - [info] Flows file : /home/simo/.node-red/flows.json
20 Jul 10:16:18 - [info] Creating new flow file
20 Jul 10:16:18 - [warn]
---------------------------------------------------------------------
Your flow credentials file is encrypted using a system-generated key.
If the system-generated key is lost for any reason, your credentials
file will not be recoverable, you will have to delete it and re-enter
your credentials.
You should set your own key using the 'credentialSecret' option in
your settings file. Node-RED will then re-encrypt your credentials
file using your chosen key the next time you deploy a change.
---------------------------------------------------------------------
20 Jul 10:16:18 - [warn] Encrypted credentials not found
20 Jul 10:16:18 - [info] Starting flows
20 Jul 10:16:18 - [info] Started flows
20 Jul 10:16:18 - [info] Server now running at http://127.0.0.1:1880/
7

That is just a warning and can be ignored.

8

ok solved, i was wrong ip address
excuse me
thanks for everything

9

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