I created a flow that reads from a redis list using BLPOP. I configured it to read from localhost:6379. It came up with ETIMEOUT because I don’t have a server on the same machine. I then corrected the server address, eg 192.168.1.7:6379 and redeployed. An equivalent python script running at the command line on the same machine as node-red is able to contact the redis server and do what is necessary.
The debug panel still shows repeated errors as the flow attempts to connect to old server config. I can’t get node red to refresh the flow. I tried disabling the flow.
The old version of the flow is still running and I can’t stop it.
How do I actually control nodered? How do I debug this? Why can’t I stop the running flow after deploying a new version of it? Why does the running flow ignore the flow state “disabled”?
I’m at a loss. What am I missing? Is this normal behavior?