Updating Node Red on the iHost

eWeLink CUBE
1

Hi @SuiKa

Some time ago I posted here about some issues occurring when restarting the Node Red add-on, and although then it seemed for some time to get better, recently it was taking up to 12 hours to restart. Also sometimes it would open only in Edge, but not in the web UI nor Chrome, while the CPU is showing moments at 100%.
I tracked down on the logs that it was constantly crashing at one point, which I discovered was the event-state: on a Sonoff S60 plug.
I removed the device and its got much better but its still taking 30-45 minutes to load in the web UI, which is not logical, restarting several times, while showing this error -

2025-02-17T15:20:11 17 Feb 14:20:11 - [error] AxiosError: Request failed with status code 408

2025-02-17T15:20:11     at settle (/data/node_modules/node-red-contrib-ewelink-cube/node_modules/axios/dist/node/axios.cjs:2019:12)

2025-02-17T15:20:11     at IncomingMessage.handleStreamEnd (/data/node_modules/node-red-contrib-ewelink-cube/node_modules/axios/dist/node/axios.cjs:3135:11)

2025-02-17T15:20:11     at IncomingMessage.emit (node:events:530:35)

2025-02-17T15:20:11     at IncomingMessage.emit (node:domain:489:12)

2025-02-17T15:20:11     at endReadableNT (node:internal/streams/readable:1698:12)

2025-02-17T15:20:11     at process.processTicksAndRejections (node:internal/process/task_queues:82:21)

2025-02-17T15:20:11     at Axios.request (/data/node_modules/node-red-contrib-ewelink-cube/node_modules/axios/dist/node/axios.cjs:4287:41)

2025-02-17T15:20:11     at process.processTicksAndRejections (node:internal/process/task_queues:95:5)

I don´t understand this error message at all and have no idea where to start debugging this.
Complete logs ( not continuous ) are attached here but I would ask you please to take a look at them to see what is happening here. Thanks
newfile.txt (238.7 KB)

2

There are some question I’d like to ask.

12 hours to restart iHost?

The problem occured(the web UI) in where? iHost Web UI or Node-red add-on homepage?

3

EDIT Yes! to restart Node-red add-on.
After removing the guilty S60 we’re ‘down’ to 40 minutes or so. I’m referring always to when an NR update or a node update makes us restart.

Both, i.e. on the add-on list/Node-red Web UI and also when the link on the Info tab opens up the browser (Chrome)

4

So it’s the red light blink for 40+ mins or everything works normal but wait for 40+ mins to see the iHost dashboard/node-red homepage?

What’s that?

So is the web UI of node-red, not the iHost dashboard itself.

5

Correct, as seen on the add-on list.
When I refer to an update I refer to e.g. yesterday Node-red updated to v4.0.9,
or when a node is updated e.g. eWelink Cube when updated to v1.3.3. Approximately once every month or so, and NO, no red light on iHost. iHost continues running, with Filebrowser, Mosquitto etc all functioning. Virtual devices created by eWelink Cube are however not functioning, nor MQTT devices that run automations in Node-red.

6

Your log is from 2025-02-17T15:14:35 17 to 2025-02-17T15:33:21.
And during that time it did cause some error to reboot the node-red.
But everytime it reboot it was quick, can’t find any sign that block the rendering the node-red homepage.
As for the error, I’ll try to pinpoint it.
But if you have the full log would be more helpful.

1 Like