Help: Node red won't start

General
1

My Raspberry Pi hosts an instance of Node Red which runs my central heating system. It got quite cold in the house today and on checking the dashboard and finding it unreachable I thought I'd reboot the Pi and re-start node red. How ever it will not start and reports the following error:

Welcome to Node-RED

8 Mar 16:20:02 - [info] Node-RED version: v3.0.0
8 Mar 16:20:02 - [info] Node.js version: v14.21.3
8 Mar 16:20:02 - [info] Linux 5.15.84-v8+ arm64 LE
8 Mar 16:20:02 - [info] Loading palette nodes
8 Mar 16:20:05 - [info] Dashboard version 3.1.7 started at /ui
8 Mar 16:20:06 - [info] Settings file : /home/pi/.node-red/settings.js
8 Mar 16:20:06 - [info] Context store : 'default' [module=memory]
8 Mar 16:20:06 - [info] User directory : /home/pi/.node-red
8 Mar 16:20:06 - [warn] Projects disabled : editorTheme.projects.enabled=false
8 Mar 16:20:06 - [info] Flows file : /home/pi/.node-red/start
8 Mar 16:20:06 - [info] Creating new flow file
8 Mar 16:20:06 - [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.

8 Mar 16:20:06 - [warn] Encrypted credentials not found
8 Mar 16:20:06 - [error] Uncaught Exception:
8 Mar 16:20:06 - [error] Error: listen EADDRINUSE: address already in use 0.0.0.0:1880
at Server.setupListenHandle [as _listen2] (net.js:1331:16)
at listenInCluster (net.js:1379:12)
at doListen (net.js:1516:7)
at processTicksAndRejections (internal/process/task_queues.js:83:21)

Can anyone help and me get Node red working again. I tried deleting the flow file and setting decryption to false in the settings file but it has no effect. Will I have to wipe everything and start again? I hope not as it's going to take a while.

Thanks

2

That means that node-red is already running. This command should show the log for the running version
node-red-log

If you want to stop and restart it then run
node-red-stop
node-red-start

Edit
Looking carefully at your output above I think you ran node-red start instead of node-red-start

3

Panic over chaps. It seems to have started working properly. I dont think I gave everything enough time. Hey ho live and learn eh?

4

I see you are using node red 3.0.0. That was short lived as it had several significant bugs. I suggest you upgrade to the latest. You can do that easily by running the install script again.

5

Ok thanks for that Collin, may wait for better weather before updating as it's been pretty reliable up till today.

1 Like
6

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