Help needed, Node-red crashed!

General
1

After more the a year of working with node-red. Now all over sudden, Node-red chrashed.

Can anyone help me with a solution??

:~ $ node-red
28 Jun 14:01:19 - [info]

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

28 Jun 14:01:19 - [info] Node-RED version: v2.2.0
28 Jun 14:01:19 - [info] Node.js  version: v15.14.0
28 Jun 14:01:19 - [info] Linux 5.10.63-v7+ arm LE
28 Jun 14:01:22 - [info] Loading palette nodes
28 Jun 14:1:26 - [s7comm-Error] - Installation of Module net-keepalive failed because we might be on the wrong OS. OS=linux
28 Jun 14:1:26 - [s7comm-Info] - Debug configuration for logLevelNodeS7:{"debug":0,"silent":true}
28 Jun 14:1:26 - [s7comm-Info] - Debug configuration for logLevelNodeRED:{"debug":2,"silent":true}
28 Jun 14:01:27 - [info] Dashboard up and running
28 Jun 14:01:29 - [info] Dashboard version 3.1.6 started at /ui
28 Jun 14:01:31 - [info] Settings file  : /home/pi/.node-red/settings.js
28 Jun 14:01:31 - [info] Context store  : 'default' [module=localfilesystem]
28 Jun 14:01:31 - [info] User directory : /home/pi/.node-red
28 Jun 14:01:31 - [warn] Projects disabled : editorTheme.projects.enabled=false
28 Jun 14:01:31 - [warn] Flows file name not set. Generating name using hostname.
28 Jun 14:01:31 - [info] Flows file     : /home/pi/.node-red/flows_pipi.json
28 Jun 14:01:31 - [info] Server now running at http://127.0.0.1:1880/
28 Jun 14:01:34 - [info] Starting flows
28 Jun 14:01:35 - [info] [cronplus:Midnight] createTask - index: 0, static: true, opt: {"name":"schedule1","topic":"topic1","payloadType":"date","payload":"","expressionType":"cron","expression":"00 59 23 * * *","location":"","offset":"0","solarType":"all","solarEvents":"sunrise,sunset"}
28 Jun 14:01:37 - [info] Started flows
28 Jun 14:01:41 - [red] Uncaught Exception:
28 Jun 14:01:41 - [error] Error: getaddrinfo ENOTFOUND 50:2c:c6:9d:7f:4e
    at GetAddrInfoReqWrap.onlookup [as oncomplete] (node:dns:69:26)
2

Are you certain that is the end of the log? There should be a stack trace at the end. That stack trace should point to the issue. Without it we are guessing.

3

@Steve-Mcl , I made a wrong configuration at ip address of GREE HVAC.

Welcome to Node-RED
===================
28 Jun 14:12:48 - [info] Node-RED version: v2.2.0
28 Jun 14:12:48 - [info] Node.js  version: v15.14.0
28 Jun 14:12:48 - [info] Linux 5.10.63-v7+ arm LE
28 Jun 14:12:51 - [info] Loading palette nodes
28 Jun 14:12:55 - [s7comm-Error] - Installation of Module net-keepalive failed because we might be on the wrong OS. OS=linux
28 Jun 14:12:55 - [s7comm-Info] - Debug configuration for logLevelNodeS7:{"debug":0,"silent":true}
28 Jun 14:12:55 - [s7comm-Info] - Debug configuration for logLevelNodeRED:{"debug":2,"silent":true}
28 Jun 14:12:56 - [info] Dashboard up and running
28 Jun 14:12:59 - [info] Dashboard version 3.1.6 started at /ui
28 Jun 14:13:00 - [info] Settings file  : /home/pi/.node-red/settings.js
28 Jun 14:13:00 - [info] Context store  : 'default' [module=localfilesystem]
28 Jun 14:13:00 - [info] User directory : /home/pi/.node-red
28 Jun 14:13:00 - [warn] Projects disabled : editorTheme.projects.enabled=false
28 Jun 14:13:00 - [warn] Flows file name not set. Generating name using hostname.
28 Jun 14:13:00 - [info] Flows file     : /home/pi/.node-red/flows_pipi.json
28 Jun 14:13:00 - [info] Server now running at http://127.0.0.1:1880/
28 Jun 14:13:03 - [info] Starting flows
28 Jun 14:13:05 - [info] [cronplus:Midnight] createTask - index: 0, static: true, opt: {"name":"schedule1","topic":"topic1","payloadType":"date","payload":"","expressionType":"cron","expression":"00 59 23 * * *","location":"","offset":"0","solarType":"all","solarEvents":"sunrise,sunset"}
28 Jun 14:13:07 - [info] Started flows
28 Jun 14:13:10 - [red] Uncaught Exception:
28 Jun 14:13:10 - [error] Error: getaddrinfo ENOTFOUND 50:2c:c6:9d:7f:4e
    at GetAddrInfoReqWrap.onlookup [as oncomplete] (node:dns:69:26)
nodered.service: Main process exited, code=exited, status=1/FAILURE
nodered.service: Failed with result 'exit-code'.
nodered.service: Service RestartSec=20s expired, scheduling restart.
nodered.service: Scheduled restart job, restart counter is at 50.
Stopped Node-RED graphical event wiring tool.
Started Node-RED graphical event wiring tool.
28 Jun 14:13:32 - [info]
4

Ok so 2 things...

  1. You can fix this by starting node red with the safe flag node-red --safe
  2. You should raise an issue on the gree node GitHub repository ( It is not handling internal errors correctly)
5

@Steve-Mcl , Thanks very much for your help. I was able now to correct the error in my flow and after deploy it started again.

I would like to do what you suggest, to raise the issue on the gree node GitHub repository. But I am not sure how to do that.....

6

@Steve-Mcl , Ok I think I found it. With report on "node-red-contrib-gree-hvac".

7

Hi @henkkas

I see you just submitted a report about the node on flows.nodered.org. That doesn't get sent to the maintainer of the node - just to me so we can check for content that should not be on the site.

To raise an issue against the node itself, you'll need to do that on GitHub here: Issues · inwaar/node-red-contrib-gree-hvac · GitHub

8

@knolleary , thanks for that. I have done so.

I saw that last year the issue was raised also, but no follow up occured I am sad to see.

9

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