Dashboard unreachable from time to time

Good morning everyone,

I am experiencing some downtimes of node-red for quite a while now. It seems that node-red is "busy" for a few Minutes from time to time. In this period I can't access the Dashboard. Alexa commands that trigger the Dashboard don't get a response either. A few minutes later everything works fine again. Rebooting does not solve the Problem (it does in the special situation, but the issue comes up again)

Logs do not show any hint what could be up.
Logging in to the pi shows (with htop) that the CPU is fine aswell in these situations.

RAM also seems to be fine in general:
pi@raspberrypi:~ $ free -m
total used free shared buff/cache available
Mem: 7898 1748 4974 26 1176 6206

Ram usage of the Node-Red instance as iobroker shows is ~60mb.

As the system usually runs fine I am a little bit confused where to improve. Has anybody got a hint?
I am thinking about setting up the host completely from scratch but...
You know.

In general I think finding the issue would be the better way.

As mentioned above, system is a Raspberry PI, Node-Red installed as Instance in iobroker.

Best regards

What is the cpu usage when it locks up?

When it is locked, close all browser tabs accessing the dashboard, and see if you are able to access the editor (not the dashboard).

Hi Colin,

CPU usage is about 20% on each core. That looks fine for me.

Best regards

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