at Socket.Readable.push (internal/streams/readable.js:206:10)
at TCP.onStreamRead (internal/stream_base_commons.js:188:23)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! node-red-docker@2.1.4 start: node $NODE_OPTIONS node_modules/node-red/red.js $FLOWS "--userDir" "/data"
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the node-red-docker@2.1.4 start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /data/.npm/_logs/2022-11-01T02_11_05_924Z-debug.log
at addChunk (internal/streams/readable.js:293:12)
at readableAddChunk (internal/streams/readable.js:267:9)
at Socket.Readable.push (internal/streams/readable.js:206:10)
at TCP.onStreamRead (internal/stream_base_commons.js:188:23)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! node-red-docker@2.1.4 start: node $NODE_OPTIONS node_modules/node-red/red.js $FLOWS "--userDir" "/data"
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the node-red-docker@2.1.4 start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /data/.npm/_logs/2022-11-01T02_50_01_874Z-debug.log
app.min.js:530 Rendered http://192.168.3.224:1880/ui/css/app.min.less successfully.
app.min.js:530 CSS for http://192.168.3.224:1880/ui/css/app.min.less generated in 54ms
app.min.js:530 Less has finished. CSS generated in 54ms
:1880/ui/socket.io/?EIO=4&transport=polling&t=OGphRn-:1 Failed to load resource: net::ERR_CONNECTION_TIMED_OUT
:1880/ui/socket.io/?EIO=4&transport=polling&t=OGphUVE:1 Failed to load resource: net::ERR_CONNECTION_REFUSED
Thank you very much, Mr. Colin. My nodered dashboard crashed every time it refreshed the ui page, and I updated the container version, which had the same problem. Many hidden node streams were removed in the background, and the night market did not help. (The current prop arm64 v8 2G), I'm going to upgrade my hardware configuration, I don't know if there is any superior configuration for my reference, thanks again! (Here are some logs for your reference.)
After refreshing the ui webpage:
2 Nov 08:19:03 - [red] Uncaught Exception:
2 Nov 08:19:03 - [error] TypeError: bufferUtil.unmask is not a function
at unmask (/data/node_modules/node-red-dashboard/node_modules/ws/lib/buffer-util.js:115:23)
at Receiver.getData (/data/node_modules/node-red-dashboard/node_modules/ws/lib/receiver.js:420:25)
at Receiver.startLoop (/data/node_modules/node-red-dashboard/node_modules/ws/lib/receiver.js:148:22)
at Receiver._write (/data/node_modules/node-red-dashboard/node_modules/ws/lib/receiver.js:83:10)
at writeOrBuffer (internal/streams/writable.js:358:12)
at Receiver.Writable.write (internal/streams/writable.js:303:10)
at Socket.socketOnData (/data/node_modules/node-red-dashboard/node_modules/ws/lib/websocket.js:1116:35)
at Socket.emit (events.js:400:28)
at Socket.emit (domain.js:475:12)
at addChunk (internal/streams/readable.js:293:12)
at readableAddChunk (internal/streams/readable.js:267:9)
at Socket.Readable.push (internal/streams/readable.js:206:10)
at TCP.onStreamRead (internal/stream_base_commons.js:188:23)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! node-red-docker@2.2.3 start: node $NODE_OPTIONS node_modules/node-red/red.js $FLOWS "--userDir" "/data"
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the node-red-docker@2.2.3 start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /data/.npm/_logs/2022-11-02T08_19_03_473Z-debug.log
Mr. Colin, I would like to refer to your hardware configuration and installation scheme. Could you please give me a list? You are the most enthusiastic playmate I have ever met. I am so lucky to meet you. (Maybe bare installation should be more stable, thanks lot!)
You can force an install of node 14, 16 or 18 by using the --node14, --node16 or --node18 parameter.
However doing so may break some nodes that may need re-installing manually.
Generally it is recommended to update all nodes to their latest versions before upgrading.
If you wish to stay on nodejs 10 you can update to the latest Node-RED 1.x or 2.x version by adding
--nodered-version="1.3.7" or --nodered-version="2.2.2" to that install command. If in doubt this is the safer option.
Please backup your installation and flows before upgrading.
Note: not all embedded hardware can be updated via this method - please check before proceeding.
Are you asking a question? It is telling you that you need to upgrade nodejs, which you can do by adding, for example, --node16 on the end of the command (after a space). I recommend using 16 at the moment, 18 is still quite new.
