Error : node not deployed

Dashboard
1

Suddenly Node-red gives a problem on deploying after even the smallest editing on a flow. Giving 'error: node not deployed' and the dashboard does not start (only the start screen with the Node Red logo).

On deploying a pop-up says : "the server is running a more recent set of flows. The changes include no conflicts and can be merged automatically.
and 3 buttons : review changes, merge, ignore deploy.

On review changes, I then try to merge.
another pop-up : The flows on the server have been updated.
then the 'error: node not deployed' pops up...

Even stopping and starting Node Red (even in safe mode) does not do anything. Only a system reboot wil load the dashboard again.

running on a raspberry pi, with recent update/upgrade

20 Feb 20:21:20 - [info] Node-RED version: v1.0.3
20 Feb 20:21:20 - [info] Node.js version: v10.19.0
20 Feb 20:21:20 - [info] Linux 4.19.80-v7+ arm LE
20 Feb 20:21:22 - [info] Loading palette nodes
20 Feb 20:21:36 - [info] Dashboard version 2.19.1 started at /ui
20 Feb 20:21:36 - [info] Settings file : /home/pi/.node-red/settings.js
20 Feb 20:21:36 - [info] Context store : 'storeInFile' [module=localfilesystem]
20 Feb 20:21:36 - [info] Context store : 'default' [module=memory]
20 Feb 20:21:36 - [info] User directory : /home/pi/.node-red
20 Feb 20:21:36 - [warn] Projects disabled : editorTheme.projects.enabled=false
20 Feb 20:21:36 - [info] Flows file : /home/pi/.node-red/flows_theone.json
20 Feb 20:21:37 - [error] Unable to listen on http://127.0.0.1:1880/
20 Feb 20:21:37 - [error] Error: port in use

anyone knows how to fix ?
Didier

2

You’re running node-red in another process on the same machine too. That’s why what you see in the browser wasn’t the actual flow deployed

3

I never had this before. How to fix ?

4

How are you stopping node red and how are you starting it? You should be using node-red-stop and node-red-start.

5

Fixed it

I have no idea why, but I think node-red got corrupted.
I deleted all node-red files and restoreded a backup.
Everything seems to work again now.

Didier

6

I had the same issue and there where two things. First when you starts nom use another starting port or you are using a soapserver node.

Solutions:
start with another portnumer for nom and/or the soapserver.
Regards
Ger

7

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.