Node-RED is running in a Synology NAS docker Container for over a year now, no problems so far. Three days ago I did an update from 4.1 to 4.1.1, I also updated all Nodes that had a new version. I also installed Dashboard 2 and did some small diagrams with it.
Everything looked fine, but after some hours NR did no longer respond in the browser. Container manager statistics showed me that NR was using about 120% CPU power. I restarted the container but the next day the same problem appeared, CPU is again up at 120% and nothing is really working.
So today I once more did a restart, after about 5 hours or so NR is up at 120% CPU again.
I attach the log file to my question as I have no clue what is going on. How can I find out which Nodes are responsible for this strange behavior?
Have you added a chart that is updating rapidly and has a long time range configured so that you have thousands or tens of thousands of points across the chart?
I think its not that much, but yes, there is a measurement every few seconds for one of the diagrams. And as the diagram is for 7 days, well that can sum up to (3600 * 24 * 7) 604.800 measurements - well that is a lot!
I now disabled the Dashboard 2 flows, as it's (beside the update) the only thing that has changed, so I can verify if thats the problem.
Yes, it was my fault. No problems after disabling the heavy load measurement.
Note to myself: Dashboard 2 is not a replacement for Influx-DB and Grafana
