Node - Red stop running

General
1

Hi,

maybe someone can help me to find out, why node-red is stopping.
I see in the node-red log files, it shall be stopped, but I don't know why.

My Node Red is running on Raspbian

4 Jan 08:00:08 - [info] [yeelight-compat-hue-config:Lamp] Connecting to Yeelight 192.168.3.46:55443
Stopping Node-RED graphical event wiring tool...
4 Jan 08:00:09 - [info] Flows stoppen
4 Jan 08:00:09 - [info] [yeelight-compat-hue-config:Lamp] Closing connection
4 Jan 08:00:09 - [info] [openhab2-controller:openhab] close
4 Jan 08:00:09 - [info] [openhab2-in:Openhab] close
4 Jan 08:00:09 - [warn] [openhab2-controller:openhab] ERROR {"type":{"code":"ECO NNRESET"}}
4 Jan 08:00:09 - [info] [mqtt-broker:MQTT Server] Verbindung zum Broker node-re d@mqtt://192.168.3.37:1883 wurde beendet.
Error at 192.168.3.46:55443 { Error: connect EHOSTUNREACH 192.168.3.46:55443
at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1107:14)
errno: 'EHOSTUNREACH',
code: 'EHOSTUNREACH',
syscall: 'connect',
address: '192.168.3.46',
port: 55443 }
4 Jan 08:00:11 - [info] [yeelight-compat-hue-config:Lamp] Disconnected from 192. 168.3.46:55443
4 Jan 08:00:14 - [info] Flows gestoppt
nodered.service: Succeeded.
Stopped Node-RED graphical event wiring tool.
This text will be hidden

2

That is saying that something in your flow could not connect to 192.168.3.46, so I would start by fixing that. That should not cause node-red to stop, so it may be something else, but fix that and see what happens.
If you start node-red using
node-red --safe
it will start the editor without starting the flows so you can fix your flow and re-deploy.

3

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