Deploy button doesn't click

(Shouldn't you be asking @hazymat?)

Yes, I replied to the wrong message, sorry.

Sorright. I just wanted to check.

Don't use sudo with either of those commands.

2 Likes
  1. I have cleared the cache, but I've tried and problem occurs in Firefox and Edge as well
  2. I don't recall what the last thing I did was. Probably updating an InfluxDB node with a different measurement name.

Problem is, I can't go back and change any nodes, because ... I can't deploy changes!

Yep, node-red runs under user context, at least it does for me!

Well, that's not exactly true.

It won't deploy because something in some/one of the nodes is not working.
Changing it to the correct value/setting could/will allow it to deploy.

Wince you say you updated the influxDB node, this is my plan:
(no guarantees)

BACKUP your flows.

(this isn't too difficult.)

Make a directory (say ~/JUST_IN_CASE)

Copy all the .json files from the .node-red directory to this new one.

COPY

Go into the node-red editor.

delete all nodes associated to the influxDB.

See if that helps.

You may have to restart node-red.
(From .node-red folder in the CLI)
node-red-restart

If it doesn't, copy the files back. No harm. No fowl.

Do you see anything in the node-red log when you click deploy?
If you haven't already then try @Trying_to_learn 's suggestion of starting with --safe (without sudo). If that works (possibly only allowing a single deploy) then it does show it is something going wrong with the flow.
Another thing to try is move the flows file away and restart node-red. It should create an empty flows file. See if it is ok then.

if using SAFE mode

Just letting you know:
It has changed how it works - from my perspective.

Originally (I am sure) all you had to do was click on a debug node and turn it on/off.
Then you could deploy.

Now you have to actually move a new node into the edit area.
I'd pick a debug node and just put it anywhere.

Good luck.

Thanks all for your comments. They were very helpful. I didn't think this would be caused by something I had done in the front end, but I was wrong.

Luckily, I have a flow that automatically backs-up Node-RED configuration files to a zip file stored on Dropbox, every 3 hours. It was possible to pull out the flows_server.json file from a backup from a week ago, copy it over and restart node-red. Problem solved.

Now I just have to go through all the backups and home-in on the time that the deploy button stopped working, then compare with the previous backup to see exactly what caused it.

Please let me know if this is something you want to hear about @knolleary otherwise I will refrain from tagging you further :slight_smile:

I don't know about Nick. But I'm sure we would be interested in finding out what the problem was. Please consider adding to this thread when you find out, you never know when someone else might come across a similar problem.

I suggest re-trying with the latest just to make sure it still fails (you may have done this already of course).

I would very much like to hear what you discover. The editor should never hit an error like that, but until youve narrowed it down a bit, there is not much we can do.

Yes, tried that - and it does. So the problem is re-producable.

I've done a diff on the two .json files. I don't understand what has caused this, but here are the changes below.

Starting with the file that worked, the following changes were made that stopped it working:

Node removed:

		"id": "4fedbfaf.6bb98",
		"type": "tab",
		"label": "Flow 1",
		"disabled": false,
		"info": ""
	},
	{

Node removed:

  "id": "3d86e78e.17ff28",
  "type": "tab",
  "label": "Influx & Grafana",
  "disabled": false,
  "info": ""

},
{

Node removed:

		"id": "b0b4d384.fd376",
		"type": "debug",
		"z": "3d86e78e.17ff28",
		"name": "",
		"active": true,
		"tosidebar": true,
		"console": false,
		"tostatus": false,
		"complete": "true",
		"targetType": "full",
		"x": 310,
		"y": 160,
		"wires": []
	},
	{

Within this function node, the first wire was removed leaving only one wire:

	{
		"id": "dd66451b.0f8f88",
		"type": "function",
		"z": "3d86e78e.17ff28",
		"name": "",
		"func": "Sumplevel = msg.payload\nSump = msg.topic\n\nmsg.payload = {\n    level: Sumplevel,\n    sump: Sump\n    \n}\nreturn msg;",
		"outputs": 1,
		"noerr": 0,
		"x": 170,
		"y": 200,
		"wires": [
			[
				"b0b4d384.fd376",  **<----- REMOVED**
				"fd1c2137.60bb6"
			]
		]
	},

Within this node, the value of x was changed from 570 shown below to 410:

	{
		"id": "fd1c2137.60bb6",
		"type": "influxdb out",
		"z": "3d86e78e.17ff28",
		"influxdb": "9d9ad3f4.49ce7",
		"name": "",
		"measurement": "sump_levels",
		"precision": "",
		"retentionPolicy": "",
		"x": 570,
		"y": 200,
		"wires": []
	}

Finally, the following was added at the end of the .json file:

	},
	{
		"id": "33dcee83.60bd72",
		"type": "comment",
		"z": "3d86e78e.17ff28",
		"name": "Sump Levels",
		"info": "",
		"x": 90,
		"y": 160,
		"wires": []

I suspect this doesn't provide enough context to work out what caused the problem. Happy to send the whole .json file to a trusted person in private if required. @knolleary @TotallyInformation

For future reference if you post the code/flow segments using the technique detailed here then it will show them faithfully.

Thanks @Colin, I've updated my previous post!

No need, I found the problem ...

image

2 Likes

Should I mark that as the solution? :anguished:

1 Like

Please do send me the 'broken' flow as a direct message here. Will look at it in the morning

Would that be considered as a cat scan?

1 Like