Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Failed deployment: error - Failed to send request to twinId 8374 with command: zos.storage.pools #2211

Closed
TullysInc opened this issue Feb 26, 2024 · 3 comments
Labels
type_bug Something isn't working

Comments

@TullysInc
Copy link

This issue was initially reported over the support chat:

5376_failed deployment error

Replicated the issue at our end as well:

Node ID: 5376
network: https://next.dashboard.grid.tf/

Dashboard and grid proxy is indicating the node 5376 status is Up.

image

However, when clicking into the Node details it indicates this node is down.

image

@khaledyoussef24 khaledyoussef24 added the type_bug Something isn't working label Feb 26, 2024
@AhmedHanafy725
Copy link
Collaborator

Tried to ping this node over RMB but it always times out. Also when I selected this farm, there were no nodes returned even this node. @sabrinasadik can we check the logs of this node? maybe the RMB service has an issue

@scottyeager
Copy link

Node logs indicate the node can't connect to RMB relay:

2024-02-29 18:26:43	
[+] noded: 2024-02-29T17:26:43.743Z ERROR [rmb::peer::socket] failed to establish connection to Some("relay.grid.tf") : IO error: failed to lookup address information: Try again
2024-02-29 18:26:38	
[+] noded: 2024-02-29T17:26:38.738Z INFO  [rmb::peer::socket] connecting to relay Some("relay.grid.tf")

Messages like this are printing constantly, while the node is still submitting uptime reports. Transferring this issue to Zos repo for further investigation.

@scottyeager scottyeager transferred this issue from threefoldtech/tfgrid-sdk-ts Feb 29, 2024
@muhamadazmy
Copy link
Member

I think this issue was a temporary failure in name resolution. But whatever caused it, it's gone now! i can reach the node normally on rmb now with now issues.

I assume this was a network glitch in the farmer network! but once it was resolved, the node was reachable again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type_bug Something isn't working
Projects
No open projects
Status: Done
Development

No branches or pull requests

5 participants