Hi there.
I got a problem with Nodered. Til 7 days ago everything works good. I installed Grafana on the same Pi and all good. Since yesterday Nodered is dead. I tried to reboot the pi, to stop the service and restart it. I stopped Grafana.service too but nothing.
Nodered is not starting but in background my flows are working but from my browser I can't reach my instance.
This is what happening when I type node-red
Welcome to Node-RED
28 Apr 19:48:54 - [info] Node-RED version: v2.2.2
28 Apr 19:48:54 - [info] Node.js version: v14.19.0
28 Apr 19:48:54 - [info] Linux 5.10.92-v8+ arm64 LE
28 Apr 19:48:54 - [info] Loading palette nodes
28 Apr 19:48:57 - [info] Dashboard version 3.1.6 started at /ui
28 Apr 19:48:58 - [info] Settings file : /home/pi/.node-red/settings.js
28 Apr 19:48:58 - [info] Context store : 'default' [module=memory]
28 Apr 19:48:58 - [info] User directory : /home/pi/.node-red
28 Apr 19:48:58 - [warn] Projects disabled : editorTheme.projects.enabled=false
28 Apr 19:48:58 - [info] Flows file : /home/pi/.node-red/flows.json
28 Apr 19:48:58 - [error] Uncaught Exception:
28 Apr 19:48:58 - [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)
What I see is the [error] Error: listen EADDRINUSE: address already in use 0.0.0.0:1880 but I can't figure it out how to fix it and if is this the problem that won't permit to open Nodered on my browser.
I did right now but nothing as changed.
The IP is still the same and I'm connected via SSH and it is connected the PI.
What I get with node-red is still the same.
I tried even to use the command sudo systemctl status nodered and what I get is this:
nodered.service - Node-RED graphical event wiring tool
Loaded: loaded (/lib/systemd/system/nodered.service; enabled; vendor preset: enabled)
Active: active (running) since Thu 2022-04-28 20:08:54 CEST; 53s ago
Docs: Redirecting…
Main PID: 4144 (node-red)
Tasks: 31 (limit: 8987)
CPU: 20.149s
CGroup: /system.slice/nodered.service
├─4144 node-red
├─4177 /bin/bash /home/pi/.node-red/node_modules/node-red-node-pi-gpio/nrgpio out 5 100
├─4179 python3 -u /home/pi/.node-red/node_modules/node-red-node-pi-gpio/nrgpio.py out 5 100
├─4180 /bin/bash /home/pi/.node-red/node_modules/node-red-node-pi-gpio/nrgpio out 18 100
├─4182 python3 -u /home/pi/.node-red/node_modules/node-red-node-pi-gpio/nrgpio.py out 18 100
├─4183 /bin/bash /home/pi/.node-red/node_modules/node-red-node-pi-gpio/nrgpio out 18 100
├─4185 python3 -u /home/pi/.node-red/node_modules/node-red-node-pi-gpio/nrgpio.py out 18 100
├─4186 /bin/bash /home/pi/.node-red/node_modules/node-red-node-pi-gpio/nrgpio out 13 100
├─4188 python3 -u /home/pi/.node-red/node_modules/node-red-node-pi-gpio/nrgpio.py out 13 100
├─4189 /bin/bash /home/pi/.node-red/node_modules/node-red-node-pi-gpio/nrgpio out 6 100
├─4191 python3 -u /home/pi/.node-red/node_modules/node-red-node-pi-gpio/nrgpio.py out 6 100
├─4192 /bin/bash /home/pi/.node-red/node_modules/node-red-node-pi-gpio/nrgpio out 12 100
├─4194 python3 -u /home/pi/.node-red/node_modules/node-red-node-pi-gpio/nrgpio.py out 12 100
├─4195 /bin/bash /home/pi/.node-red/node_modules/node-red-node-pi-gpio/nrgpio out 12 100
├─4197 python3 -u /home/pi/.node-red/node_modules/node-red-node-pi-gpio/nrgpio.py out 12 100
├─4198 /bin/bash /home/pi/.node-red/node_modules/node-red-node-pi-gpio/nrgpio out 26 100
├─4200 python3 -u /home/pi/.node-red/node_modules/node-red-node-pi-gpio/nrgpio.py out 26 100
├─4201 /bin/bash /home/pi/.node-red/node_modules/node-red-node-pi-gpio/nrgpio out 26 100
├─4203 python3 -u /home/pi/.node-red/node_modules/node-red-node-pi-gpio/nrgpio.py out 26 100
├─4205 /bin/bash /home/pi/.node-red/node_modules/node-red-node-pi-gpio/nrgpio out 26 100
└─4207 python3 -u /home/pi/.node-red/node_modules/node-red-node-pi-gpio/nrgpio.py out 26 100
Apr 28 20:08:59 pi-casa Node-RED[4144]: your settings file. Node-RED will then re-encrypt your credentials
Apr 28 20:08:59 pi-casa Node-RED[4144]: file using your chosen key the next time you deploy a change.
Apr 28 20:08:59 pi-casa Node-RED[4144]: ---------------------------------------------------------------------
Apr 28 20:08:59 pi-casa Node-RED[4144]: 28 Apr 20:08:59 - [info] Starting flows
Apr 28 20:09:00 pi-casa Node-RED[4144]: 28 Apr 20:09:00 - [error] [openhab2-in:0213439286e8efa5] TypeError: Cannot read property 'addListener' of null
Apr 28 20:09:00 pi-casa Node-RED[4144]: 28 Apr 20:09:00 - [info] Started flows
Apr 28 20:09:01 pi-casa Node-RED[4144]: 28 Apr 20:09:01 - [info] [mqtt-broker:Tasmota] Connected to broker: mqtt://192.168.1.121:1883
Apr 28 20:09:01 pi-casa Node-RED[4144]: 28 Apr 20:09:01 - [info] [alexa-remote-account:523a6fa2.e43cc8] intialising with the PROXY method and saved data...
Apr 28 20:09:03 pi-casa Node-RED[4144]: 28 Apr 20:09:03 - [info] [openhab2-controller2:Openhab] Opened connection to http://192.168.1.121:8080/rest/events?topics=openhab/items
Apr 28 20:09:04 pi-casa Node-RED[4144]: 28 Apr 20:09:04 - [info] [openhab2-controller2:Openhab] Connection established. Emitting 161 InitialEvents.
Nodered in background still working and for example via Openhab I can turn the light on and off but I can't access to the graphical typing on the browser my-ip:1880
I tried to open it from a different browser but nothing changed, still not opening the web interface in the meanwhile in background everything works.
On the Pi I installed a Raspbian lite and on it I installed Openhab, Nodered, Mosquitto and Grafana. So Nodered it doesn't work only for Openhab. They are different software over a same machine.
Of course I'm using the Pi's IP.
I can't understand what's going on and still facing this problem
