# Deployed flow not updating (node-red-contrib-redis ignoring close event after flow deploy)

**URL:** <https://discourse.nodered.org/t/deployed-flow-not-updating-node-red-contrib-redis-ignoring-close-event-after-flow-deploy/731>\
**Category:** General\
**Created:** [11 June 2018 02:30 UTC](https://discourse.nodered.org/t/deployed-flow-not-updating-node-red-contrib-redis-ignoring-close-event-after-flow-deploy/731 "2018-06-11T02:30:14Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![adarsk](https://avatars.discourse-cdn.com/v4/letter/a/e495f1/32.png) [@adarsk](https://discourse.nodered.org/u/adarsk)\
**Post date:** [11 June 2018 02:30 UTC](https://discourse.nodered.org/t/deployed-flow-not-updating-node-red-contrib-redis-ignoring-close-event-after-flow-deploy/731/1 "2018-06-11T02:30:14Z")

</div>

Hi all,

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?

thanks

---

<div class="post-metadata">

**Author:** ![knolleary](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/knolleary/32/3_2.png) [@knolleary](https://discourse.nodered.org/u/knolleary)\
**Post date:** [11 June 2018 05:46 UTC](https://discourse.nodered.org/t/deployed-flow-not-updating-node-red-contrib-redis-ignoring-close-event-after-flow-deploy/731/2 "2018-06-11T05:46:53Z")

</div>

Which redis node module are you using? It sounds like the node isn’t listening for the close event that happens as part of a deploy and is continuing to try to reconnect. If that’s the case, it’s a bug with that node which needs fixing.

Nick

---

<div class="post-metadata">

**Author:** ![adarsk](https://avatars.discourse-cdn.com/v4/letter/a/e495f1/32.png) [@adarsk](https://discourse.nodered.org/u/adarsk)\
**Post date:** [11 June 2018 05:48 UTC](https://discourse.nodered.org/t/deployed-flow-not-updating-node-red-contrib-redis-ignoring-close-event-after-flow-deploy/731/3 "2018-06-11T05:48:56Z")

</div>

let’s see…

node-red-contrib-redis

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [11 June 2018 07:11 UTC](https://discourse.nodered.org/t/deployed-flow-not-updating-node-red-contrib-redis-ignoring-close-event-after-flow-deploy/731/4 "2018-06-11T07:11:53Z")

</div>

Does it recover if you restart node-red?

---

<div class="post-metadata">

**Author:** ![knolleary](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/knolleary/32/3_2.png) [@knolleary](https://discourse.nodered.org/u/knolleary)\
**Post date:** [11 June 2018 07:16 UTC](https://discourse.nodered.org/t/deployed-flow-not-updating-node-red-contrib-redis-ignoring-close-event-after-flow-deploy/731/5 "2018-06-11T07:16:37Z")

</div>

In which case, you may want to raise an issue against [node-red-contrib-redis](https://github.com/chameleonbr/node-red-contrib-redis). My guess is an issue with the node’s close handling - it doesn’t handle the case where the node has not successfully connected so the client object is left trying to continually reconnect with the original details.

---

<div class="post-metadata">

**Author:** ![adarsk](https://avatars.discourse-cdn.com/v4/letter/a/e495f1/32.png) [@adarsk](https://discourse.nodered.org/u/adarsk)\
**Post date:** [11 June 2018 07:17 UTC](https://discourse.nodered.org/t/deployed-flow-not-updating-node-red-contrib-redis-ignoring-close-event-after-flow-deploy/731/6 "2018-06-11T07:17:51Z")

</div>

restarting does force the issue to resolve, yes.

---

<div class="post-metadata">

**Author:** ![adarsk](https://avatars.discourse-cdn.com/v4/letter/a/e495f1/32.png) [@adarsk](https://discourse.nodered.org/u/adarsk)\
**Post date:** [11 June 2018 07:21 UTC](https://discourse.nodered.org/t/deployed-flow-not-updating-node-red-contrib-redis-ignoring-close-event-after-flow-deploy/731/7 "2018-06-11T07:21:57Z")

</div>

re: node-red-contrib-redis. Looking at the code, this appears to be the case. I’ll try to log defect.