Node red booting

Hei, can anyone look at the below start up log i get when i load node red? I have changed my ip for my tv but node red is still searching for old info! I'm not very techy but can try a little. Trying to stop last line tcp out :LG TV, i dont use this ip/ port anymore. Thanks

Last login: Tue Apr 30 05:31:39 on ttys001

Marks-iMac:~ Marcus$ node-red

30 Apr 18:37:08 - [info]

Welcome to Node-RED

===================

30 Apr 18:37:08 - [info] Node-RED version: v0.20.5

30 Apr 18:37:08 - [info] Node.js version: v10.15.3

30 Apr 18:37:08 - [info] Darwin 15.6.0 x64 LE

30 Apr 18:37:09 - [info] Loading palette nodes

30 Apr 18:37:10 - [warn] rpi-gpio : Raspberry Pi specific node set inactive

30 Apr 18:37:10 - [info] Settings file : /Users/Marcus/.node-red/settings.js

30 Apr 18:37:10 - [info] Context store : 'default' [module=memory]

30 Apr 18:37:10 - [info] User directory : /Users/Marcus/.node-red

30 Apr 18:37:10 - [warn] Projects disabled : editorTheme.projects.enabled=false

30 Apr 18:37:10 - [info] Flows file : /Users/Marcus/.node-red/flows_Marks-iMac.local.json

30 Apr 18:37:10 - [info] Starting flows

30 Apr 18:37:10 - [info] [tcp out:LG TV] connecting to 192.168.10.112:1272

30 Apr 18:37:10 - [info] Started flows

30 Apr 18:37:10 - [info] [tcp out:LG TV] error: Error: connect EHOSTDOWN 192.168.10.112:1272

check to see if you have an unused configuration node and delete them

thanks for reply, no node listed. I wonder if i installed the node directly to node red user file ? I might have dragged dropped it or installed it in the node red "running" directory ? Late nights with new things...
inshort, i installed lgtv node with an old ip/port and node red is still looking for this. The lgtv node has been removed and reinstalled with new ip/port.

here is terminal shot
30 Apr 18:54:50 - [info] [tcp out:LG TV] error: Error: connect EHOSTDOWN 192.168.10.112:1272 - Local (192.168.10.113:49826)

ehostdown info(192.168.10.112:1272) refers to old configuration
(192.168.10.113:49826) is the new config

Have you tried searching?

In the node-red editor CTRL-F and type 192.168.10.112 or LG see if it turns up.

You have a TCP Out node that is being told to use that address. That is what you need to change.

Thanks for all replies, appreciate your help, i finally found a problem. i have 2 nodes that turned up outside of viewer view. Erased them and rebooted , they turned up again in the same location, way off to the right. Any ideas ??
1 node is inject (payload with name) 2 node is old lgtv node with the problem ip and port. They keep coming back, is it possible that the nodes are somehow running from node red boot , i.e. in the node red boot application (not sure i am wording this correctly ) ? New to a lot of this , thanks

It's definitely in you flow as it comes after starting flows

Try searching TCP and open any/all TCP nodes. See if you can't find it.

And to be sure you are using node-red search (and not browser search) use the menu button (far top right looks like 3 horizontal bars e.g. Like this) & select search from there.

Alternatively you may have to dig into your flows.json file.

Thanks for all replies, appreciate your help, i finally found a problem. i have 2 nodes that turned up outside of viewer view. Erased them and rebooted , they turned up again in the same location, way off to the right. Any ideas ??
1 node is inject (payload with name) 2 node is old lgtv node with the problem ip and port. They keep coming back, is it possible that the nodes are somehow running from node red boot , i.e. in the node red boot application (not sure i am wording this correctly ) ? New to a lot of this , thanks

Obvious question but I have to ask. Did you deploy after deleting?

If you did then possibly a permissions issue? Perhaps node-red can't save the flow and is then reloaded after a reboot.

Embarrassed and happy to say this fixed the problem, can't believe i missed this. Little stressed and not thinking clear.
Thanks to all the replies. Thanks Steve-Mc

1 Like