Node-red editor does not load


... after deploying Node-Red it has stopped running and i´ve got a " red level " code as you can see below. How to recover from this situation ?

24 Apr 19:53:17 - [info] Node-RED version: v0.20.5
24 Apr 19:53:17 - [info] Node.js version: v10.15.3
24 Apr 19:53:17 - [info] Linux 4.14.98-v7+ arm LE
24 Apr 19:53:18 - [info] Loading palette nodes
^A24 Apr 19:53:22 - [info] Dashboard version 2.13.2 started at /ui
24 Apr 19:53:23 - [info] Settings file : /home/pi/.node-red/settings.js
24 Apr 19:53:23 - [info] Context store : 'default' [module=memory]
24 Apr 19:53:23 - [info] User directory : /home/pi/.node-red
24 Apr 19:53:23 - [info] Server now running at
24 Apr 19:53:23 - [info] Active project : HomeAmorim
24 Apr 19:53:23 - [info] Flows file : /home/pi/.node-red/projects/HomeAmorim/flows_localhost.json
24 Apr 19:53:23 - [info] Starting flows
24 Apr 19:53:23 - [info] [mosca in:2f73359.33167ca] Binding mosca mqtt server on port: 1883
2019-04-24 18:53:24: Connecting to modbustcp slave at unit_id: 1
2019-04-24 18:53:24: Connecting to modbustcp slave at unit_id: 1
24 Apr 19:53:24 - [info] Started flows
24 Apr 19:53:24 - [info] [mqtt-broker:80a21c84.84208] Connection failed to broker: mqtt://
24 Apr 19:53:24 - [red] Uncaught Exception:
24 Apr 19:53:24 - RangeError [ERR_OUT_OF_RANGE]: The value of "value" is out of range. It must be >= 0 and <= 4294967295. Received 1556132004270
at checkInt (internal/buffer.js:35:11)
at writeU_Int32BE (internal/buffer.js:619:3)
nodered.service: Main process exited, code=exited, status=1/FAILURE
nodered.service: Unit entered failed state.
nodered.service: Failed with result 'exit-code'.
nodered.service: Service hold-off time over, scheduling restart.
Stopped Node-RED graphical event wiring tool.
Started Node-RED graphical event wiring tool.



I found the solution for my problem.




For the benefit of anyone else reading this, what was the solution?


First, i knew that the error was related with a wrong value i have manually injected to simulate a function. So i decided to open/edit flow file > flows_localhost.json ... and i could disabled the tab where the problematic node was. I could than restart Node-Red without issues.
Final step, i edit the node that was creating the problem. I reenabled the tab and deployed. Node-Red was running well again.

PS: It´s a honor to chat with you. I ´m a very very basic node-red user ...and contributing for this amazing tool that is Node-Red ... uauu :grinning:



1 Like