Hi community,
have you got any problem with Node Red plugin?
I’m going to set a configuration but if I try to access into plugin it shows a white screen.
Have you got the same problem?
Hi @Salvatore_Scarantino
The white screen could be due to a number of problems. Mainly if the flows inside are too big for the browser to download (due to a slow connection for example) or the Node-RED service is crashing on load.
To analyze your problem, could you give us more details:
- Which version of Node-RED plugin are you using?
- Have you changed something recently and what? could this be the problem?
- You can check the logs for the Node-RED service in the plugin management section. Is there any error message?
Once we have this information we can look further into the problem.
Regards!
-
Which version of Node-RED plugin are you using?
“I’ve used version 1.1.0, after that I’ve updated the version in 1.4.0, but I have the same problem” -
Have you changed something recently and what? could this be the problem?
“In this morning I’ve set some MQTT connector, but in late morning Node RED stopped working.” -
You can check the logs for the Node-RED service in the plugin management section. Is there any error message?
9 Aug 09:47:53 - [error] [http request:345bc4720f22f5ab] no response from server
<— Last few GCs —>
[7:0x7f04e7cf03b0] 15105815 ms: Mark-sweep 239.5 (258.4) → 238.3 (258.7) MB, 1502.7 / 0.1 ms (average mu = 0.078, current mu = 0.018) allocation failure scavenge might not succeed
[7:0x7f04e7cf03b0] 15106725 ms: Mark-sweep 239.4 (258.7) → 238.3 (258.7) MB, 883.1 / 0.1 ms (average mu = 0.059, current mu = 0.030) allocation failure scavenge might not succeed
<— JS stacktrace —>
FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
./entrypoint.sh: line 14: 7 Aborted (core dumped) /usr/local/bin/node $NODEOPTIONS node_modules/node-red/red.js --userDir /data $FLOWS
*9 Aug 13:57:12 - [info] *
Welcome to Node-RED
===================
9 Aug 13:57:12 - [info] Node-RED version: v3.0.1
9 Aug 13:57:12 - [info] Node.js version: v16.16.0
9 Aug 13:57:12 - [info] Linux 4.15.0-1021-aws x64 LE
9 Aug 13:57:13 - [info] Loading palette nodes
9 Aug 13:57:15 - [info] Settings file : /data/settings.js
9 Aug 13:57:15 - [info] Context store : ‘default’ [module=memory]
9 Aug 13:57:15 - [info] User directory : /data
9 Aug 13:57:15 - [warn] Projects disabled : editorTheme.projects.enabled=false
9 Aug 13:57:15 - [info] Flows file : /data/flows.json
9 Aug 13:57:15 - [info] Server now running at http://127.0.0.1:1880/
*9 Aug 13:57:15 - [warn] *
---------------------------------------------------------------------
Your flow credentials file is encrypted using a system-generated key.
If the system-generated key is lost for any reason, your credentials
file will not be recoverable, you will have to delete it and re-enter
your credentials.
You should set your own key using the ‘credentialSecret’ option in
your settings file. Node-RED will then re-encrypt your credentials
file using your chosen key the next time you deploy a change.
---------------------------------------------------------------------
9 Aug 13:57:15 - [info] Starting flows
9 Aug 13:57:15 - [info] Started flows
9 Aug 13:57:15 - [info] [mqtt-broker:prova MQTT] Connected to broker: mqtt_cloud@mqtt://sc-tech.aws.thinger.io:1883
<— Last few GCs —>
*[7:0x7fe2e347a3b0] 257963 ms: Scavenge 239.6 (258.0) → 238.7 (258.0) MB, 4.5 / 0.0 ms (average mu = 0.146, current mu = 0.036) allocation failure *
*[7:0x7fe2e347a3b0] 257991 ms: Scavenge 239.6 (258.0) → 238.8 (258.2) MB, 10.7 / 0.0 ms (average mu = 0.146, current mu = 0.036) allocation failure *
[7:0x7fe2e347a3b0] 258827 ms: Mark-sweep 239.9 (258.2) → 238.8 (258.2) MB, 818.6 / 0.1 ms (average mu = 0.111, current mu = 0.082) allocation failure scavenge might not succeed
<— JS stacktrace —>
FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
./entrypoint.sh: line 14: 7 Aborted (core dumped) /usr/local/bin/node $NODEOPTIONS node_modules/node-red/red.js --userDir /data $FLOWS
*9 Aug 14:01:37 - [info] *
Welcome to Node-RED
===================
9 Aug 14:01:37 - [info] Node-RED version: v3.0.1
9 Aug 14:01:37 - [info] Node.js version: v16.16.0
9 Aug 14:01:37 - [info] Linux 4.15.0-1021-aws x64 LE
9 Aug 14:01:38 - [info] Loading palette nodes
9 Aug 14:01:40 - [info] Settings file : /data/settings.js
9 Aug 14:01:40 - [info] Context store : ‘default’ [module=memory]
9 Aug 14:01:40 - [info] User directory : /data
9 Aug 14:01:40 - [warn] Projects disabled : editorTheme.projects.enabled=false
9 Aug 14:01:40 - [info] Flows file : /data/flows.json
9 Aug 14:01:40 - [info] Server now running at http://127.0.0.1:1880/
*9 Aug 14:01:40 - [warn] *
---------------------------------------------------------------------
Your flow credentials file is encrypted using a system-generated key.
If the system-generated key is lost for any reason, your credentials
file will not be recoverable, you will have to delete it and re-enter
your credentials.
You should set your own key using the ‘credentialSecret’ option in
your settings file. Node-RED will then re-encrypt your credentials
file using your chosen key the next time you deploy a change.
---------------------------------------------------------------------
9 Aug 14:01:40 - [info] Starting flows
9 Aug 14:01:40 - [info] Started flows
9 Aug 14:01:41 - [info] [mqtt-broker:prova MQTT] Connected to broker: mqtt_cloud@mqtt://sc-tech.aws.thinger.io:1883
<— Last few GCs —>
[7:0x7f5dc56bc3b0] 176229 ms: Mark-sweep 240.0 (258.2) → 238.9 (258.0) MB, 2215.5 / 0.1 ms (average mu = 0.084, current mu = 0.022) allocation failure scavenge might not succeed
[7:0x7f5dc56bc3b0] 181716 ms: Mark-sweep 240.3 (258.2) → 239.0 (258.5) MB, 5426.8 / 0.1 ms (average mu = 0.028, current mu = 0.011) allocation failure scavenge might not succeed
<— JS stacktrace —>
FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
./entrypoint.sh: line 14: 7 Aborted (core dumped) /usr/local/bin/node $NODEOPTIONS node_modules/node-red/red.js --userDir /data $FLOWS
*9 Aug 14:04:47 - [info] *
Welcome to Node-RED
===================
9 Aug 14:04:47 - [info] Node-RED version: v3.0.1
9 Aug 14:04:47 - [info] Node.js version: v16.16.0
9 Aug 14:04:47 - [info] Linux 4.15.0-1021-aws x64 LE
9 Aug 14:04:48 - [info] Loading palette nodes
9 Aug 14:04:49 - [info] Settings file : /data/settings.js
9 Aug 14:04:49 - [info] Context store : ‘default’ [module=memory]
9 Aug 14:04:49 - [info] User directory : /data
9 Aug 14:04:49 - [warn] Projects disabled : editorTheme.projects.enabled=false
9 Aug 14:04:49 - [info] Flows file : /data/flows.json
9 Aug 14:04:49 - [info] Server now running at http://127.0.0.1:1880/
*9 Aug 14:04:49 - [warn] *
---------------------------------------------------------------------
Your flow credentials file is encrypted using a system-generated key.
If the system-generated key is lost for any reason, your credentials
file will not be recoverable, you will have to delete it and re-enter
your credentials.
You should set your own key using the ‘credentialSecret’ option in
your settings file. Node-RED will then re-encrypt your credentials
file using your chosen key the next time you deploy a change.
---------------------------------------------------------------------
9 Aug 14:04:49 - [info] Starting flows
9 Aug 14:04:49 - [info] Started flows
9 Aug 14:04:49 - [info] [mqtt-broker:prova MQTT] Connected to broker: mqtt_cloud@mqtt://sc-tech.aws.thinger.io:1883
9 Aug 14:06:34 - [error] [http request:345bc4720f22f5ab] RequestError: read ECONNRESET
9 Aug 14:06:34 - [error] [http request:345bc4720f22f5ab] RequestError: read ECONNRESET
<— Last few GCs —>
[7:0x7f87c26043b0] 128906 ms: Mark-sweep 239.2 (258.2) → 238.1 (258.2) MB, 662.4 / 0.1 ms (average mu = 0.156, current mu = 0.026) allocation failure scavenge might not succeed
[7:0x7f87c26043b0] 129609 ms: Mark-sweep 239.2 (258.2) → 238.1 (258.2) MB, 688.4 / 0.1 ms (average mu = 0.089, current mu = 0.020) allocation failure scavenge might not succeed
<— JS stacktrace —>
FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
./entrypoint.sh: line 14: 7 Aborted (core dumped) /usr/local/bin/node $NODEOPTIONS node_modules/node-red/red.js --userDir /data $FLOWS
*9 Aug 14:07:06 - [info] *
Welcome to Node-RED
===================
9 Aug 14:07:06 - [info] Node-RED version: v3.0.1
9 Aug 14:07:06 - [info] Node.js version: v16.16.0
9 Aug 14:07:06 - [info] Linux 4.15.0-1021-aws x64 LE
9 Aug 14:07:07 - [info] Loading palette nodes
9 Aug 14:07:09 - [info] Settings file : /data/settings.js
9 Aug 14:07:09 - [info] Context store : ‘default’ [module=memory]
9 Aug 14:07:09 - [info] User directory : /data
9 Aug 14:07:09 - [warn] Projects disabled : editorTheme.projects.enabled=false
9 Aug 14:07:09 - [info] Flows file : /data/flows.json
9 Aug 14:07:09 - [info] Server now running at http://127.0.0.1:1880/
*9 Aug 14:07:09 - [warn] *
---------------------------------------------------------------------
Your flow credentials file is encrypted using a system-generated key.
If the system-generated key is lost for any reason, your credentials
file will not be recoverable, you will have to delete it and re-enter
your credentials.
You should set your own key using the ‘credentialSecret’ option in
your settings file. Node-RED will then re-encrypt your credentials
file using your chosen key the next time you deploy a change.
---------------------------------------------------------------------
9 Aug 14:07:09 - [info] Starting flows
9 Aug 14:07:10 - [info] Started flows
9 Aug 14:07:11 - [info] [mqtt-broker:prova MQTT] Connected to broker: mqtt_cloud@mqtt://sc-tech.aws.thinger.io:1883
<— Last few GCs —>
[7:0x7fe6503af3b0] 91564 ms: Mark-sweep 240.1 (258.2) → 239.1 (258.5) MB, 622.7 / 0.1 ms (average mu = 0.196, current mu = 0.033) allocation failure scavenge might not succeed
[7:0x7fe6503af3b0] 92220 ms: Mark-sweep 240.3 (258.5) → 239.1 (258.5) MB, 630.5 / 0.1 ms (average mu = 0.131, current mu = 0.039) allocation failure scavenge might not succeed
<— JS stacktrace —>
FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
./entrypoint.sh: line 14: 7 Aborted (core dumped) /usr/local/bin/node $NODEOPTIONS node_modules/node-red/red.js --userDir /data $FLOWS
*9 Aug 14:08:42 - [info] *
Welcome to Node-RED
===================
9 Aug 14:08:42 - [info] Node-RED version: v3.0.1
9 Aug 14:08:42 - [info] Node.js version: v16.16.0
9 Aug 14:08:42 - [info] Linux 4.15.0-1021-aws x64 LE
9 Aug 14:08:43 - [info] Loading palette nodes
9 Aug 14:08:45 - [info] Settings file : /data/settings.js
9 Aug 14:08:45 - [info] Context store : ‘default’ [module=memory]
9 Aug 14:08:45 - [info] User directory : /data
9 Aug 14:08:45 - [warn] Projects disabled : editorTheme.projects.enabled=false
9 Aug 14:08:45 - [info] Flows file : /data/flows.json
9 Aug 14:08:45 - [info] Server now running at http://127.0.0.1:1880/
*9 Aug 14:08:45 - [warn] *
---------------------------------------------------------------------
Your flow credentials file is encrypted using a system-generated key.
If the system-generated key is lost for any reason, your credentials
file will not be recoverable, you will have to delete it and re-enter
your credentials.
You should set your own key using the ‘credentialSecret’ option in
your settings file. Node-RED will then re-encrypt your credentials
file using your chosen key the next time you deploy a change.
---------------------------------------------------------------------
9 Aug 14:08:45 - [info] Starting flows
9 Aug 14:08:45 - [info] Started flows
9 Aug 14:08:45 - [info] [mqtt-broker:prova MQTT] Connected to broker: mqtt_cloud@mqtt://sc-tech.aws.thinger.io:1883
<— Last few GCs —>
[7:0x7f722edf03b0] 81273 ms: Mark-sweep 242.6 (258.5) → 241.5 (258.5) MB, 628.3 / 0.1 ms (average mu = 0.152, current mu = 0.060) allocation failure scavenge might not succeed
[7:0x7f722edf03b0] 81932 ms: Mark-sweep 242.6 (258.5) → 241.5 (258.5) MB, 645.4 / 0.1 ms (average mu = 0.092, current mu = 0.021) allocation failure scavenge might not succeed
<— JS stacktrace —>
FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
./entrypoint.sh: line 14: 7 Aborted (core dumped) /usr/local/bin/node $NODEOPTIONS node_modules/node-red/red.js --userDir /data $FLOWS
*9 Aug 14:10:10 - [info] *
Welcome to Node-RED
===================
9 Aug 14:10:10 - [info] Node-RED version: v3.0.1
9 Aug 14:10:10 - [info] Node.js version: v16.16.0
9 Aug 14:10:10 - [info] Linux 4.15.0-1021-aws x64 LE
9 Aug 14:10:11 - [info] Loading palette nodes
9 Aug 14:10:12 - [info] Settings file : /data/settings.js
9 Aug 14:10:12 - [info] Context store : ‘default’ [module=memory]
9 Aug 14:10:12 - [info] User directory : /data
9 Aug 14:10:12 - [warn] Projects disabled : editorTheme.projects.enabled=false
9 Aug 14:10:12 - [info] Flows file : /data/flows.json
9 Aug 14:10:12 - [info] Server now running at http://127.0.0.1:1880/
*9 Aug 14:10:12 - [warn] *
---------------------------------------------------------------------
Your flow credentials file is encrypted using a system-generated key.
If the system-generated key is lost for any reason, your credentials
file will not be recoverable, you will have to delete it and re-enter
your credentials.
You should set your own key using the ‘credentialSecret’ option in
your settings file. Node-RED will then re-encrypt your credentials
file using your chosen key the next time you deploy a change.
---------------------------------------------------------------------
9 Aug 14:10:12 - [info] Starting flows
9 Aug 14:10:13 - [info] Started flows
9 Aug 14:10:13 - [info] [mqtt-broker:prova MQTT] Connected to broker: mqtt_cloud@mqtt://sc-tech.aws.thinger.io:1883
9 Aug 14:12:20 - [error] [http request:345bc4720f22f5ab] RequestError: read ECONNRESET
<— Last few GCs —>
[7:0x7fee32b423b0] 142074 ms: Mark-sweep 240.4 (258.2) → 239.3 (258.2) MB, 631.5 / 0.1 ms (average mu = 0.111, current mu = 0.037) allocation failure scavenge might not succeed
[7:0x7fee32b423b0] 142722 ms: Mark-sweep 240.4 (258.2) → 239.4 (258.5) MB, 623.4 / 0.1 ms (average mu = 0.076, current mu = 0.038) allocation failure scavenge might not succeed
<— JS stacktrace —>
FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
./entrypoint.sh: line 14: 7 Aborted (core dumped) /usr/local/bin/node $NODEOPTIONS node_modules/node-red/red.js --userDir /data $FLOWS
*9 Aug 14:12:38 - [info] *
Welcome to Node-RED
===================
9 Aug 14:12:38 - [info] Node-RED version: v3.0.1
9 Aug 14:12:38 - [info] Node.js version: v16.16.0
9 Aug 14:12:38 - [info] Linux 4.15.0-1021-aws x64 LE
9 Aug 14:12:39 - [info] Loading palette nodes
9 Aug 14:12:41 - [info] Settings file : /data/settings.js
9 Aug 14:12:41 - [info] Context store : ‘default’ [module=memory]
9 Aug 14:12:41 - [info] User directory : /data
9 Aug 14:12:41 - [warn] Projects disabled : editorTheme.projects.enabled=false
9 Aug 14:12:41 - [info] Flows file : /data/flows.json
9 Aug 14:12:41 - [info] Server now running at http://127.0.0.1:1880/
*9 Aug 14:12:41 - [warn] *
---------------------------------------------------------------------
Your flow credentials file is encrypted using a system-generated key.
If the system-generated key is lost for any reason, your credentials
file will not be recoverable, you will have to delete it and re-enter
your credentials.
You should set your own key using the ‘credentialSecret’ option in
your settings file. Node-RED will then re-encrypt your credentials
file using your chosen key the next time you deploy a change.
---------------------------------------------------------------------
9 Aug 14:12:41 - [info] Starting flows
9 Aug 14:12:41 - [info] Started flows
9 Aug 14:12:42 - [info] [mqtt-broker:prova MQTT] Connected to broker: mqtt_cloud@mqtt://sc-tech.aws.thinger.io:1883
<— Last few GCs —>
[7:0x7fefe7f363b0] 98488 ms: Mark-sweep 238.8 (258.5) → 237.8 (258.7) MB, 618.1 / 0.2 ms (average mu = 0.168, current mu = 0.034) allocation failure scavenge might not succeed
[7:0x7fefe7f363b0] 99124 ms: Mark-sweep 238.9 (258.7) → 237.8 (258.7) MB, 606.9 / 0.1 ms (average mu = 0.120, current mu = 0.046) allocation failure scavenge might not succeed
<— JS stacktrace —>
FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
./entrypoint.sh: line 14: 7 Aborted (core dumped) /usr/local/bin/node $NODEOPTIONS node_modules/node-red/red.js --userDir /data $FLOWS
*9 Aug 14:14:22 - [info] *
Welcome to Node-RED
===================
9 Aug 14:14:22 - [info] Node-RED version: v3.0.1
9 Aug 14:14:22 - [info] Node.js version: v16.16.0
9 Aug 14:14:22 - [info] Linux 4.15.0-1021-aws x64 LE
9 Aug 14:14:23 - [info] Loading palette nodes
9 Aug 14:14:25 - [info] Settings file : /data/settings.js
9 Aug 14:14:25 - [info] Context store : ‘default’ [module=memory]
9 Aug 14:14:25 - [info] User directory : /data
9 Aug 14:14:25 - [warn] Projects disabled : editorTheme.projects.enabled=false
9 Aug 14:14:25 - [info] Flows file : /data/flows.json
9 Aug 14:14:25 - [info] Server now running at http://127.0.0.1:1880/
*9 Aug 14:14:25 - [warn] *
---------------------------------------------------------------------
Your flow credentials file is encrypted using a system-generated key.
If the system-generated key is lost for any reason, your credentials
file will not be recoverable, you will have to delete it and re-enter
your credentials.
You should set your own key using the ‘credentialSecret’ option in
your settings file. Node-RED will then re-encrypt your credentials
file using your chosen key the next time you deploy a change.
---------------------------------------------------------------------
9 Aug 14:14:25 - [info] Starting flows
9 Aug 14:14:25 - [info] Started flows
9 Aug 14:14:25 - [info] [mqtt-broker:prova MQTT] Connected to broker: mqtt_cloud@mqtt://sc-tech.aws.thinger.io:1883
9 Aug 14:51:28 - [error] [http request:345bc4720f22f5ab] RequestError: read ECONNRESET
9 Aug 14:51:29 - [error] [http request:345bc4720f22f5ab] RequestError: read ECONNRESET
From my previous message to your response we have received a message from our server monitoring system that your server was on a state of high cpu load. After having taking a look at it the issue is crearly the Node-RED service.
Once we’ve restarted the service, the load of the server seems to remain stable for the time being. Please check if you have access to the Node-RED plugin.
If the issue did not happen before I would focus on this change. It seems that from the logs something needs more system memory than the server can handle, maybe the size of a message or a simultaneous operation over multiple messages.
Whenever you encounter the issue of not being able to load Node-RED try restarting it from the plugin management section (it might take a while if the server is busy) while checking the logs to see if the same error happens again.
From our side, we’ll keep an eye on the system to make sure you don’t lose service and to try to further understand the issue.
Please let us know if you are able to obtain more details or even fix the issue.
Regards!
I have found the issue: I’ve forgotten a MQTT publish interval on my ESP32, filling the memory.
Now the system work perfectly.
Thank you for your support.
1 Like