I have imported a template node from a website using the import function. If I now want to change or delete this node, the deploy button does not respond.
Is that the case if you add any flow, or is it a particular node or set of nodes that gives the problem?
If you can't do anything then is this new and if so have you updated something or installed new nodes or anything?
Start node-red in a terminal and post the startup log here please. Copy/paste it when pasting use the </> button at the top of the forum text window and paste it in.
Is that the case if you add any flow, or is it a particular node or set of nodes that gives the problem?
I got this problem after importing a script with a JSON file from the internet. After importing it, I got a new flow with a template node in it. After that, I tried a few things and suddenly I could not deploy after changing anything in that flow. Adding and removing new flows worked perfectly. Then I removed the "problem flow" manually out of the JSON file. First I thought it worked perfectly but then if I added a new empty flow, I got the same old problem. I could not deploy. So I restored the old version with the "problem flow" again.
After restoring the old version with the "problem flow" I can add and remove flows except for the "problem flow"
12 Nov 14:09:34 - [info]
Willkommen bei Node-RED!
===================
12 Nov 14:09:34 - [info] Node-RED Version: v1.2.3
12 Nov 14:09:34 - [info] Node.js Version: v10.15.2
12 Nov 14:09:34 - [info] Linux 4.19.75-v7l+ arm LE
12 Nov 14:09:36 - [info] Paletten-Nodes werden geladen
12 Nov 14:09:41 - [info] Dashboard version 2.23.4 started at /ui
12 Nov 14:09:42 - [info] Einstellungsdatei: /home/pi/.node-red/settings.js
12 Nov 14:09:42 - [info] Kontextspeicher: 'default' [ module=memory]
12 Nov 14:09:42 - [info] Benutzerverzeichnis: /home/pi/.node-red
12 Nov 14:09:42 - [warn] Projekte inaktiviert: editorTheme.projects.enabled=false
12 Nov 14:09:42 - [info] Flow-Datei: /home/pi/.node-red/flows_raspberrypi.json
12 Nov 14:09:42 - [info] Server wird jetzt auf http://127.0.0.1:1880/ ausgeführt.
12 Nov 14:09:42 - [warn]
---------------------------------------------------------------------
Die Datei mit den Datenflowberechtigungsnachweisen wird mit einem vom System generierten Schlüssel verschlüsselt.
Wenn der vom System generierte Schlüssel aus irgendeinem Grund verloren geht, werden Ihre Berechtigungsnachweise
Die Datei kann nicht wiederhergestellt werden. Sie müssen sie löschen und erneut eingeben.
Ihre Berechtigungsnachweise.
Sie sollten Ihren eigenen Schlüssel mit Hilfe der Option 'credentialSecret' in
Ihre Einstellungsdatei. Node-RED wird dann Ihre Berechtigungsnachweise erneut verschlüsseln.
Datei mit dem ausgewählten Schlüssel beim nächsten Deployen einer Änderung verwenden.
---------------------------------------------------------------------
12 Nov 14:09:43 - [info] Flows starten
12 Nov 14:09:59 - [info] Flows gestartet
12 Nov 14:09:59 - [info] [mqtt-broker:Broker] Verbindung zum Broker mqtt://127.0.0.1:1883 hergestellt.
The only problem I can see with the log is that you are using a two year old version of nodejs which has had numerous fixes since then. The latest release of 10.x was 10.23 a few weeks ago. I suggest upgrading that to the latest 10.x or even better to 12.x.
What OS are you running on and how did you install node-red/nodejs to get such an old version?
All you should need to do is what I guess you didn't do initially which is to run the install/upgrade script from the node-red docs. Running on Raspberry Pi : Node-RED
12 Nov 17:17:11 - [info] Node-RED Version: v1.2.3
12 Nov 17:17:11 - [info] Node.js Version: v14.15.0
12 Nov 17:17:11 - [info] Linux 4.19.75-v7l+ arm LE
But sadly this did not fix my problem
All you should need to do is what I guess you didn't do initially which is to run the install/upgrade script from the node-red docs. Running on Raspberry Pi : Node-RED
Node-red was running more than a year perfectly so I think it was everything right.
I don't think the hangup is anything to do with that flow.
If you start node-red in a terminal so you see the log you posted earlier, and then make it lockup what do you see in the terminal?
Also try opening a terminal and running top and then make it lockup. What do you see there? Is anything hogging the processor for example?