Node-Red won't start now

General
1

This is what I'm seeing.

pi@TimePi:~/.node-red $ node-red --safe
28 Feb 21:24:00 - [info] 

Welcome to Node-RED
===================

28 Feb 21:24:00 - [info] Node-RED version: v3.0.2
28 Feb 21:24:00 - [info] Node.js  version: v14.19.0
28 Feb 21:24:00 - [info] Linux 5.10.63-v7+ arm LE
28 Feb 21:24:01 - [info] Loading palette nodes
28 Feb 21:24:08 - [info] Dashboard version 3.6.0 started at /ui
28 Feb 21:24:10 - [warn] ------------------------------------------------------
28 Feb 21:24:10 - [warn] [node-red-node-rbe/rbe] 'rbe' already registered by module node-red
28 Feb 21:24:10 - [warn] ------------------------------------------------------
28 Feb 21:24:10 - [info] Settings file  : /home/pi/.node-red/settings.js
28 Feb 21:24:10 - [info] HTTP Static    : /home/pi/.node-red/public > /
28 Feb 21:24:10 - [info] Context store  : 'default' [module=memory]
28 Feb 21:24:10 - [info] User directory : /home/pi/.node-red
28 Feb 21:24:10 - [warn] Projects disabled : set editorTheme.projects.enabled=true to enable
28 Feb 21:24:10 - [warn] Flows file name not set. Generating name using hostname.
28 Feb 21:24:10 - [info] Flows file     : /home/pi/.node-red/flows_TimePi.json
(node:6771) NOTE: We are formalizing our plans to enter AWS SDK for JavaScript (v2) into maintenance mode in 2023.

Please migrate your code to use AWS SDK for JavaScript (v3).
For more information, check the migration guide at https://a.co/7PzMCcy
(Use `node --trace-warnings ...` to show where the warning was created)
28 Feb 21:24:10 - [error] Uncaught Exception:
28 Feb 21:24:10 - [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)
pi@TimePi:~/.node-red $

This bit has me confused:

28 Feb 21:24:10 - [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)

Sorry, someone?

2

NR already running perhaps? Have you checked?

3

Thanks.

AFAIK, it isn't.

Alas - ITMT - I reloaded an older backup and it now seems to be working.

When I tried to view either the dashboard or edit screen I got a No connection message.

So I ssh to the machine and it kind of implied it had exited/failed/stopped.

Sorry.
As I have kind of fixed it, I'll close this thread.

Note:

I do NOT know what happened.
Only that rolling back to an older version of the flows seems to have resolved the problem.

4

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