Discrepancy in Active Node Contracts: User- SwissFold #66

Open
opened 2025-12-15 21:15:33 +00:00 by Cameron · 3 comments
Cameron commented 2025-12-15 21:15:33 +00:00 (Migrated from git.ourworld.tf)

It appears that the report may not accurately reflect the active node contracts.

  1. Node IDs 6517 & 6518

• Each shows 1 VM / 1 Network contract, which aligns with expectations.

  1. Node IDs 6243 & 6248

• The report indicates active contracts:
• 6243: ActiveNodeContracts = 1
• 6248: ActiveNodeContracts = 2

However, we were unable to retrieve any corresponding contracts for these Node IDs in GQL.

Furthermore, under the active nodes contract, there are some on standby nodes and 0 on rented nodes

image.png

It appears that the report may not accurately reflect the active node contracts. 1. Node IDs 6517 & 6518 • Each shows 1 VM / 1 Network contract, which aligns with expectations. 2. Node IDs 6243 & 6248 • The report indicates active contracts: • 6243: ActiveNodeContracts = 1 • 6248: ActiveNodeContracts = 2 However, we were unable to retrieve any corresponding contracts for these Node IDs in GQL. Furthermore, under the active nodes contract, there are some on standby nodes and 0 on rented nodes ![image.png](/attachments/6a775f2b-4a0f-4350-addf-04ab437a852d)
Member
Repo : https://github.com/threefoldtech/tfgrid-sdk-ts/issues/4496

Hi @Cameron, I can't move forward with this investigation because the contracts on these nodes no longer exist. They aren't showing up in GQL or the Grid Proxy, and the nodes have reverted to a 'rentable' state. Do we have any logs from before the deletion?

image

image

image

image

image

Hi @Cameron, I can't move forward with this investigation because the contracts on these nodes no longer exist. They aren't showing up in GQL or the Grid Proxy, and the nodes have reverted to a 'rentable' state. Do we have any logs from before the deletion? ![image](/attachments/cc30a996-d091-4545-9878-91a078a93fd0) ![image](/attachments/843ba658-7cac-4553-a0a5-087c972beffb) ![image](/attachments/13a40821-afa3-41fb-a47e-3023ce82651d) ![image](/attachments/9da2018d-5168-4e8f-ba8a-654b01d83e6f) ![image](/attachments/798ba8ff-29e2-4024-be30-b2e5fd20a311)
Member

Thanks for the update @zaelgohary. The user has not reported back, he also faced a “nodes not waking up the farmerbot” issue, which he confirmed is resolved. The problem with that was the time/date settings, even though they appeared correct and were set to auto‑sync. Do you think it could be related? Can we close this ticket, or would it be better to ask for the logs?

Thanks for the update @zaelgohary. The user has not reported back, he also faced a “nodes not waking up the farmerbot” issue, which he confirmed is resolved. The problem with that was the time/date settings, even though they appeared correct and were set to auto‑sync. Do you think it could be related? Can we close this ticket, or would it be better to ask for the logs?
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
3 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
mycelium/circle_support#66
No description provided.