Restart loop after a mistyped IP address

General
1

I am not sure if this is known issue or not. I am integrating Gree AC units in NR and in the device configuration I accidently mistyped the ip to 192.1680.249. Missed the dot after 168.
This causes a reboot loop in Node-Red:

Welcome to Node-RED
===================
23 Mar 21:53:54 - [info] Node-RED version: v3.1.7
23 Mar 21:53:54 - [info] Node.js  version: v20.5.1
23 Mar 21:53:54 - [info] Linux 4.4.194 arm64 LE
23 Mar 21:53:56 - [info] Loading palette nodes
23 Mar 21:54:00 - [info] Settings file  : /home/admin/.node-red/settings.js
23 Mar 21:54:00 - [info] Context store  : 'default' [module=memory]
23 Mar 21:54:00 - [info] User directory : /home/admin/.node-red
23 Mar 21:54:00 - [warn] Projects disabled : editorTheme.projects.enabled=false
23 Mar 21:54:00 - [info] Flows file     : /home/admin/.node-red/flows.json
23 Mar 21:54:00 - [warn] Encrypted credentials not found
23 Mar 21:54:00 - [info] Server now running at http://127.0.0.1:1880/
23 Mar 21:54:00 - [info] Starting flows
23 Mar 21:54:00 - [info] Started flows
23 Mar 21:54:00 - [red] Uncaught Exception:
23 Mar 21:54:00 - [error] Error: getaddrinfo ENOTFOUND 192.1680.249
    at GetAddrInfoReqWrap.onlookup [as oncomplete] (node:dns:107:26)
nodered.service: Main process exited, code=exited, status=1/FAILURE
nodered.service: Failed with result 'exit-code'.

Fortunately it was a new installation and I was able to edit the IP addreass in flow.json.

I found a discussion from a few years ago on this and something like Safe mode, but I am not sure how this would apply to this case. Is it possible to start Node-Red without starting the flows to fix such issues?

2

Where did you mistype ? What were your exact steps? I am assuming this was a contrib node where you entered an invalid address and deployed?

3

Yes, use node-red --safe

4

Yes, it was the node-red-contrib-gree-hvac node, and it was in the configuration.

5

This is a bug in the node. Normally I'd ask you to report it but it seems others have encountered this bug and reported it: Wrong ip value causes node red to crash · Issue #8 · inwaar/node-red-contrib-gree-hvac · GitHub

6

ok thank. I thought if it would be a node error the log would be prefixed with the node name, but I guess if this is uncaught, it just bubbles up to the top level.

7

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