Hello,
As requested by support, a quick summary of an alleged small issue in the farmerbot. One of my farms has about 100 nodes, of which a good portion runs on farmerbot. I noticed that several weeks ago, about 75% of them had workloads (1-5 cores on each of these nodes). On feb 4th I got several violations for standby nodes. I am writing this from phone and can’t find where to add screenshots. But there were several cases of the violations occuring at the exact same time the wakeup signal was sent. Naturally, the nodes booted succesfully several minutes later.
I noticed the majority of the deployments were cancelled. This all makes sense, because many nodes included in the config file for farmerbot, were not included in the daily cycle because they had workloads, and when these were cancelled, the list of nodes in the daily wakeup cycles increased. As only 2-3 nodes are turned on each 5 minutes, this can push some of the standby nodes outside the 24hr window (i think).
If i am correct, an easy fix would be to revert back to the 25th hour days, just as we had before. Otherwise the order of the ‘new’ nodes might need to be programmed to come after the already standby nodes.
Thanks for considering
Marsh
Farm 244
Date 4-2-25
Some of the affected nodes: 6699 6726