Deleting ghost flows

Roger Hill

unread,

Aug 21, 2016, 6:16:09 AM8/21/16

to Node-RED

Hi,

I have deleted a flow in the editor, but it continues to run even after a restart of the Node-red host.

This was a user contributed flow that I was looking at for ideas. I mistakenly deployed the flow, but later deleted it in the editor. It can no longer be seen in the editor but continues to run. I can see it in the file "flows_hostname.json.

How can I get rid of it?

Thanks in advance.

Roger...

Larry Roy

unread,

Aug 31, 2016, 8:53:08 PM8/31/16

to Node-RED

Roger,

Maybe not the best solution, but what I have done recently is create a new tab, and then delete the tab that the old flow was on. It seemed to work.

Larry

Roger Hill

unread,

Sep 2, 2016, 6:14:53 AM9/2/16

to Node-RED

Hi Larry,

Thanks for that, I will try it.

Roger...

Julian Knight

unread,

Sep 2, 2016, 7:08:47 AM9/2/16

to Node-RED

What version of NR are you using? I think that was an issue fixed in the last release - or maybe one before?

Roger Hill

unread,

Sep 4, 2016, 5:49:02 AM9/4/16

to Node-RED

Hi Julian,

I am currently using NR Version 0.15.5 on Raspbian.

Thanks, Roger.

Julian Knight

unread,

Sep 4, 2016, 11:17:23 AM9/4/16

to Node-RED

I assume you mean v0.14.5? 0.14.6 is current, perhaps try updating to that and try again?

Nicholas O'Leary

unread,

Sep 4, 2016, 5:05:44 PM9/4/16

to Node-RED Mailing List

Roger, lets roll back a bit here.

If the flow file contains the flows then they must show up in the editor somewhere. We've not had an issue with flows being present in the flow file but not showing up in the editor.

Can you send me a copy of the flow file in that state?

Nick

--
http://nodered.org

Join us on Slack to continue the conversation: http://nodered.org/slack
---
You received this message because you are subscribed to the Google Groups "Node-RED" group.
To unsubscribe from this group and stop receiving emails from it, send an email to node-red+unsubscribe@googlegroups.com.
To post to this group, send email to node...@googlegroups.com.
Visit this group at https://groups.google.com/group/node-red.
For more options, visit https://groups.google.com/d/optout.

David Kohen

unread,

Sep 5, 2016, 6:29:36 PM9/5/16

to Node-RED

I've seen the same issue in 0.14.6 - mainly when I'm writing/modifying/testing a new node. I haven't got deeply into it and at the worst rebooting the server (I'm running NR on a PI) removes the old flow. Restarting NR doesn't always help.

David

Roger Hill

unread,

Sep 5, 2016, 11:09:02 PM9/5/16

to Node-RED

Hi Nick,

Flow file attached.

Many thanks for taking a look at this for me.

Roger...

On Monday, September 5, 2016 at 9:05:44 AM UTC+12, Nick O'Leary wrote:

Roger, lets roll back a bit here.

If the flow file contains the flows then they must show up in the editor somewhere. We've not had an issue with flows being present in the flow file but not showing up in the editor.

Can you send me a copy of the flow file in that state?

Nick

On 4 September 2016 at 16:17, Julian Knight <j.kni...@gmail.com> wrote:

I assume you mean v0.14.5? 0.14.6 is current, perhaps try updating to that and try again?

On Sunday, 4 September 2016 10:49:02 UTC+1, Roger Hill wrote:
Hi Julian,

I am currently using NR Version 0.15.5 on Raspbian.

Thanks, Roger.

--
http://nodered.org

Join us on Slack to continue the conversation: http://nodered.org/slack
---
You received this message because you are subscribed to the Google Groups "Node-RED" group.

To unsubscribe from this group and stop receiving emails from it, send an email to node-red+u...@googlegroups.com.

flows_raspbi.json

Roger Hill

unread,

Sep 5, 2016, 11:14:35 PM9/5/16

to Node-RED

Hi again Nick,

These are the ghost flows that I cannot find in the editor which are shown in the confirm deploy dialog when I deploy.

sensors/e1b47ae0/RFID-1/uid (mqtt in)

sensors/e1b47ae0/# (mqtt in)

iol/command (mqtt out)

trains/horizonexpress/motor (mqtt out)

sensors/e1b47ae0/RFID-1/validate/set (mqtt out)

RFID-1 State (ui_template)

RFID-1 Log (ui_template)

RFID-1 State (ui_template)

These were just from some user contrib's that I was looking at and then deleted the tab.

Thanks, Roger...

On Monday, September 5, 2016 at 9:05:44 AM UTC+12, Nick O'Leary wrote:

Roger, lets roll back a bit here.

If the flow file contains the flows then they must show up in the editor somewhere. We've not had an issue with flows being present in the flow file but not showing up in the editor.

Can you send me a copy of the flow file in that state?

Nick

On 4 September 2016 at 16:17, Julian Knight <j.kni...@gmail.com> wrote:

I assume you mean v0.14.5? 0.14.6 is current, perhaps try updating to that and try again?

On Sunday, 4 September 2016 10:49:02 UTC+1, Roger Hill wrote:
Hi Julian,

I am currently using NR Version 0.15.5 on Raspbian.

Thanks, Roger.

--
http://nodered.org

Join us on Slack to continue the conversation: http://nodered.org/slack
---
You received this message because you are subscribed to the Google Groups "Node-RED" group.

To unsubscribe from this group and stop receiving emails from it, send an email to node-red+u...@googlegroups.com.

Nicholas O'Leary

unread,

Sep 6, 2016, 8:52:11 AM9/6/16

to Node-RED Mailing List

Hi Roger,

You've hit the same issue that is being discussed in the 'Cannot click deploy button' thread. Whilst deleting a flow tab the dashboard sidebar has thrown an error that has got things into an inconsistent state.

I've edited your flow file to remove the orphaned nodes - see attached.

We'll be doing a new release of the dashboard later this week that should stop this happening in the future.

Nick

To unsubscribe from this group and stop receiving emails from it, send an email to node-red+unsubscribe@googlegroups.com.

flows_raspbi.json

Roger Hill

unread,

Sep 6, 2016, 10:48:19 PM9/6/16

to Node-RED

Hi Nick,

Thanks for editing the flows file for me, I will keep an eye out for the release notice,

Many Thanks, Roger...

Roger Hill

unread,

Sep 8, 2016, 5:23:16 AM9/8/16

to Node-RED

Hi Nick,

Hmm This gets interesting...When I installed the modified flow file that you sent me it introduces the "Cant deploy bug" when I revert back to my original flow file, I can deploy but obviously get back the Ghost flows?

Not panicking though, I will wait for the update due out soon.

Thanks, Roger...

Paul Reed

unread,

Sep 13, 2016, 4:29:05 PM9/13/16

to Node-RED

Just for info - I've just recovered from a ghost flow too.

Using npm installed v0.14.6 I added a flow this evening using a node-red-node-weather-underground (input node), a function node to parse the temperature, and a debug node to check the output. Unfortunately wasn't happy with the local weather station in chose, so deleted the 3 nodes & deployed.

However, the data kept arriving in the debug panel!

Tried a reboot, but still data arriving, and examining my flows file, I could see that the nodes were still there, despite not showing in the editor.

I replaced the flows file with last night's backup, and all OK again.

Posted in case it helps.

Paul

Roger Hill

unread,

Sep 13, 2016, 5:58:25 PM9/13/16

to Node-RED

Hi Paul,

Thanks for the sharing you experience with the ghost flows!

Unfortunately I did not have a backup to go to. Nick edited my flows file to remove the offending flows, but unfortunately I can't deploy with the modified file so I am back to using the original file complete with ghosts.

Hopefully Nick will have some suggestions for moving forward when he gets back from conference.

Thanks again!

Roger...

Nicholas O'Leary

unread,

Sep 13, 2016, 6:04:51 PM9/13/16

to Node-RED Mailing List

Hi Roger,

sorry, amongst everything I didn't spot you were still stuck. Please try the attached.

--

http://nodered.org

Join us on Slack to continue the conversation: http://nodered.org/slack
---
You received this message because you are subscribed to the Google Groups "Node-RED" group.

To unsubscribe from this group and stop receiving emails from it, send an email to node-red+unsubscribe@googlegroups.com.

flows_raspbi.json

Roger Hill

unread,

Sep 13, 2016, 6:19:24 PM9/13/16

to Node-RED

Hi Nick,

No worries, I posted about the continued problems in the dashboard 2.0.2 announcement, I should have posted in this topic, My Bad!

I will try the modified file later today.

Many thanks, Roger...

On Wednesday, September 14, 2016 at 10:04:51 AM UTC+12, Nick O'Leary wrote:

Hi Roger,

sorry, amongst everything I didn't spot you were still stuck. Please try the attached.

On 13 September 2016 at 22:58, Roger Hill <freigh...@gmail.com> wrote:

Hi Paul,

Thanks for the sharing you experience with the ghost flows!
Unfortunately I did not have a backup to go to. Nick edited my flows file to remove the offending flows, but unfortunately I can't deploy with the modified file so I am back to using the original file complete with ghosts.
Hopefully Nick will have some suggestions for moving forward when he gets back from conference.

Thanks again!

Roger...

On Wednesday, September 14, 2016 at 8:29:05 AM UTC+12, Paul Reed wrote:
Just for info - I've just recovered from a ghost flow too.
Using npm installed v0.14.6 I added a flow this evening using a node-red-node-weather-underground (input node), a function node to parse the temperature, and a debug node to check the output. Unfortunately wasn't happy with the local weather station in chose, so deleted the 3 nodes & deployed.
However, the data kept arriving in the debug panel!
Tried a reboot, but still data arriving, and examining my flows file, I could see that the nodes were still there, despite not showing in the editor.
I replaced the flows file with last night's backup, and all OK again.

Posted in case it helps.

Paul

--
http://nodered.org

Join us on Slack to continue the conversation: http://nodered.org/slack
---
You received this message because you are subscribed to the Google Groups "Node-RED" group.

To unsubscribe from this group and stop receiving emails from it, send an email to node-red+u...@googlegroups.com.

Reply all

Reply to author

Forward