It appears that node-red has gobbled up all the memory for some reason. Are you handling any large objects in memory, images or video possibly, or reading in large files?
You could use top or htop to monitor the memory usage over a period and see if it is increasing steadily. Another possibility is that occasionally something happens that ends up in some sort of loop grabbing hold of extra memory so that the memory requirement increases rapidly and causes the failure.
for each chart - (60/freq) * (60 * hours), then multiply by line count for total.
example: for every 10s, max 6h, 2 lines = (60 / 10) * (60 * 6) = 2160 data points per line, 4320 points total
What are the points per line & totals of your graphs?
If any of your charts have more points on a line than the screen can physically display, its a little bit pointless and wasteful & is often the cause of users memory issues - though to be fair, the numbers you are talking about here, I dont expect that to be a huge issue (unless there is a bug in the chart and data is simply accumulating for ever)
I´ve disabled the charts now, I think I remember two of them look strange sometimes.
when they get no data, they didn´t delete points after 2h.
since they are unimportant anyway, I'm going to test for a few weeks without them.
I'll get back
Not really addressing your question, but it might be interesting to see if the problem stays with the machine or travels with the SD/SSD if you swap the disks between these two Pies.
If you have static or reserved IPs for these two you may have to swap those too.
@jbudd the other Pi is located somewhere else entirely and does not belong to me (customer), and it is in productive use. I can just look in ssh.
model is the same, 3B+ both 16gb sd card.
@Colin I have to wait again ~12 days, yesterday I´ve updated & reboot. today (after 9h uptime) RAM use is 33%.
can I debug somewhere, why Node-Red takes to much Ram or what in Node-Red takes it?
my system use two modbus requests and gpios, the other not.
one modbus device makes some erros:
sudo journalctl --since "24 hour ago" | grep "Node"
Okt 12 21:15:55 openwb Node-RED[392]: 12 Oct 21:15:55 - [warn] [modbus-getter:1000 - 1003] Modbus Failure On State sending Get More About It By Logging
Okt 12 21:15:55 openwb Node-RED[392]: 12 Oct 21:15:55 - [error] [modbus-getter:1000 - 1003] Error: Timed out
Okt 12 23:34:56 openwb Node-RED[392]: 12 Oct 23:34:56 - [warn] [modbus-getter:1000 - 1003] Modbus Failure On State sending Get More About It By Logging
Okt 12 23:34:56 openwb Node-RED[392]: 12 Oct 23:34:56 - [error] [modbus-getter:1000 - 1003] Error: Timed out
Okt 12 23:35:46 openwb Node-RED[392]: 12 Oct 23:35:46 - [warn] [modbus-getter:1000 - 1003] Modbus Failure On State sending Get More About It By Logging
Okt 12 23:35:46 openwb Node-RED[392]: 12 Oct 23:35:46 - [error] [modbus-getter:1000 - 1003] Error: Timed out
Okt 13 00:22:56 openwb Node-RED[392]: 13 Oct 00:22:56 - [warn] [modbus-getter:1000 - 1003] Modbus Failure On State sending Get More About It By Logging
Okt 13 00:22:56 openwb Node-RED[392]: 13 Oct 00:22:56 - [error] [modbus-getter:1000 - 1003] Error: Timed out
Okt 13 00:49:46 openwb Node-RED[392]: 13 Oct 00:49:46 - [warn] [modbus-getter:1000 - 1003] Modbus Failure On State sending Get More About It By Logging
Okt 13 00:49:46 openwb Node-RED[392]: 13 Oct 00:49:46 - [error] [modbus-getter:1000 - 1003] Error: Timed out
Okt 13 01:01:26 openwb Node-RED[392]: 13 Oct 01:01:26 - [warn] [modbus-getter:1000 - 1003] Modbus Failure On State sending Get More About It By Logging
Okt 13 01:01:26 openwb Node-RED[392]: 13 Oct 01:01:26 - [error] [modbus-getter:1000 - 1003] Error: Timed out
Okt 13 05:52:57 openwb Node-RED[392]: 13 Oct 05:52:57 - [warn] [modbus-getter:1000 - 1003] Modbus Failure On State sending Get More About It By Logging
Okt 13 05:52:57 openwb Node-RED[392]: 13 Oct 05:52:57 - [error] [modbus-getter:1000 - 1003] Error: Timed out
Okt 13 07:32:38 openwb Node-RED[392]: 13 Oct 07:32:38 - [warn] [modbus-getter:1000 - 1003] Modbus Failure On State sending Get More About It By Logging
Okt 13 07:32:38 openwb Node-RED[392]: 13 Oct 07:32:38 - [error] [modbus-getter:1000 - 1003] Error: Timed out
Okt 13 08:02:18 openwb Node-RED[392]: 13 Oct 08:02:18 - [warn] [modbus-getter:1000 - 1003] Modbus Failure On State sending Get More About It By Logging
Okt 13 08:02:18 openwb Node-RED[392]: 13 Oct 08:02:18 - [error] [modbus-getter:1000 - 1003] Error: Timed out
Okt 13 08:14:48 openwb Node-RED[392]: 13 Oct 08:14:48 - [warn] [modbus-getter:1000 - 1003] Modbus Failure On State sending Get More About It By Logging
Okt 13 08:14:48 openwb Node-RED[392]: 13 Oct 08:14:48 - [error] [modbus-getter:1000 - 1003] Error: Timed out
Okt 13 08:33:38 openwb Node-RED[392]: 13 Oct 08:33:38 - [warn] [modbus-getter:1000 - 1003] Modbus Failure On State sending Get More About It By Logging
Okt 13 08:33:38 openwb Node-RED[392]: 13 Oct 08:33:38 - [error] [modbus-getter:1000 - 1003] Error: Timed out
Okt 13 08:36:28 openwb Node-RED[392]: 13 Oct 08:36:28 - [warn] [modbus-getter:1000 - 1003] Modbus Failure On State sending Get More About It By Logging
Okt 13 08:36:28 openwb Node-RED[392]: 13 Oct 08:36:28 - [error] [modbus-getter:1000 - 1003] Error: Timed out
Okt 13 09:02:28 openwb Node-RED[392]: 13 Oct 09:02:28 - [warn] [modbus-getter:1000 - 1003] Modbus Failure On State sending Get More About It By Logging
Okt 13 09:02:28 openwb Node-RED[392]: 13 Oct 09:02:28 - [error] [modbus-getter:1000 - 1003] Error: Timed out
Okt 13 16:31:02 openwb Node-RED[392]: 13 Oct 16:31:02 - [warn] [modbus-getter:1000 - 1003] Modbus Failure On State sending Get More About It By Logging
Okt 13 16:31:02 openwb Node-RED[392]: 13 Oct 16:31:02 - [error] [modbus-getter:1000 - 1003] Error: Timed out
Okt 13 17:11:22 openwb Node-RED[392]: 13 Oct 17:11:22 - [warn] [modbus-getter:1000 - 1003] Modbus Failure On State sending Get More About It By Logging
Okt 13 17:11:22 openwb Node-RED[392]: 13 Oct 17:11:22 - [error] [modbus-getter:1000 - 1003] Error: Timed out
Okt 13 17:16:42 openwb Node-RED[392]: 13 Oct 17:16:42 - [warn] [modbus-getter:1000 - 1003] Modbus Failure On State sending Get More About It By Logging
Okt 13 17:16:42 openwb Node-RED[392]: 13 Oct 17:16:42 - [error] [modbus-getter:1000 - 1003] Error: Timed out
Okt 13 17:58:42 openwb Node-RED[392]: 13 Oct 17:58:42 - [warn] [modbus-getter:1000 - 1003] Modbus Failure On State sending Get More About It By Logging
Okt 13 17:58:42 openwb Node-RED[392]: 13 Oct 17:58:42 - [error] [modbus-getter:1000 - 1003] Error: Timed out
Okt 13 19:09:12 openwb Node-RED[392]: 13 Oct 19:09:12 - [warn] [modbus-getter:1000 - 1003] Modbus Failure On State sending Get More About It By Logging
Okt 13 19:09:12 openwb Node-RED[392]: 13 Oct 19:09:12 - [error] [modbus-getter:1000 - 1003] Error: Timed out
Okt 13 19:26:52 openwb Node-RED[392]: 13 Oct 19:26:52 - [warn] [modbus-getter:1000 - 1003] Modbus Failure On State sending Get More About It By Logging
Okt 13 19:26:52 openwb Node-RED[392]: 13 Oct 19:26:52 - [error] [modbus-getter:1000 - 1003] Error: Timed out
Okt 13 20:05:03 openwb Node-RED[392]: 13 Oct 20:05:03 - [warn] [modbus-getter:1000 - 1003] Modbus Failure On State sending Get More About It By Logging
Okt 13 20:05:03 openwb Node-RED[392]: 13 Oct 20:05:03 - [error] [modbus-getter:1000 - 1003] Error: Timed out
(24h)
Do these errors cause the memory to increase so much?
There must be something significantly different in the flows on the system which leaks memory and those the don't.
Check the versions of node-red, all nodes, and nodejs.
Are there any extra nodes used in the failing one that are not used in the others?
