Farmerbot Managed Nodes experiencing delayed boot-ups due to depleted Always on Node 4465 twin balance.

yadalamy commented

2025-12-19 13:24:17 +00:00

Member

Node ID: 4465 (Always On Node)

Summary:
Node 4465, which is configured as an Always On Node, stopped reporting uptime and remained offline until 1 TFT was sent. After the transfer, the node immediately came back online. During this period, multiple standby nodes experienced repeated delayed boot-ups.

Timeline: Node : 4465

Last uptime reported: Fri, Dec 05, 2025 at 11:01 GMT

Node back online: Fri, Dec 19, 2025 at 11:21 GMT (after sending 1 TFT)

Observed Impact on stand by Nodes:
The following nodes under Node 4465 experienced three delayed boot-ups each on Dec 16, 17, and 18, 2025:

Node 4222

Node 4408

Node 4466

Node 5170

Observation:
The recovery of Node 4465 immediately after transferring 1 TFT strongly suggests that the issue may be related to a depleted twin balance, despite the node being marked as Always On.

Concern / Question:
If the outage and delayed boot-ups were caused by a depleted twin balance, clarification is needed on:

Whether this behavior is expected for an Always On Node

Who holds responsibility for monitoring and maintaining the twin balance in this scenario

Also, as reviewed the mon.grid.tf there are multiple errors of "error sending uptime failed error="failed to report uptime: failed to update node uptime: failed to submit extrinsic: Transaction is temporarily banned" are visible.

Kindly share your insights. Thank you.

Node ID: 4465 (Always On Node) Summary: Node 4465, which is configured as an Always On Node, stopped reporting uptime and remained offline until 1 TFT was sent. After the transfer, the node immediately came back online. During this period, multiple standby nodes experienced repeated delayed boot-ups. **Timeline: Node : 4465** Last uptime reported: Fri, Dec 05, 2025 at 11:01 GMT Node back online: Fri, Dec 19, 2025 at 11:21 GMT (after sending 1 TFT) **Observed Impact on stand by Nodes:** The following nodes under Node 4465 experienced three delayed boot-ups each on Dec 16, 17, and 18, 2025: Node 4222 Node 4408 Node 4466 Node 5170 Observation: The recovery of Node 4465 immediately after transferring 1 TFT strongly suggests that the issue may be related to a depleted twin balance, despite the node being marked as Always On. Concern / Question: If the outage and delayed boot-ups were caused by a depleted twin balance, clarification is needed on: Whether this behavior is expected for an Always On Node Who holds responsibility for monitoring and maintaining the twin balance in this scenario Also, as reviewed the mon.grid.tf there are multiple errors of _"error sending uptime failed error="failed to report uptime: failed to update node uptime: failed to submit extrinsic: Transaction is temporarily banned"_ are visible. ![image](/attachments/6ce9d6f3-7cec-40bc-b203-8a399b4ef0c5) ![image](/attachments/d5e9ded2-0b21-4e5d-a621-cc163b4852a8) Kindly share your insights. Thank you.

image.png

1.1 MiB

image.png

308 KiB