You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Correct me if I'm wrong, but I understand this would result in three additional connections: one chain RPC connection and two (in most cases) to the Rmb-relays, which would not be used afterward.
I also checked with @hossnys and we found that our farmer-bot instance on the mainnet established these connections.
What happened?
I noticed this
https://github.com/threefoldtech/tfgrid-sdk-go/blob/76ac3fea5e67f47b95ab727d4412fc21fe103dc3/farmerbot/internal/farmerbot.go#L234C16-L242C3
Correct me if I'm wrong, but I understand this would result in three additional connections: one chain RPC connection and two (in most cases) to the Rmb-relays, which would not be used afterward.
I also checked with @hossnys and we found that our farmer-bot instance on the mainnet established these connections.
6 are to
2a01:4f8:e0:1f52::2
which is one of our grid stacksand 2 to
2a01:4f8:221:1e0b::2
which we are not sure relates to which serviceIs the number of connections expected? If not, what is the anticipated number?
which network/s did you face the problem on?
Main
Twin ID/s
No response
Version
No response
Node ID/s
No response
Farm ID/s
No response
Contract ID/s
No response
Relevant log output
NA
The text was updated successfully, but these errors were encountered: