-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
light node - no suitable peers available #702
Comments
same problem.... |
same problem :( |
What to do now? We tried to upgrade the node, restarting multiple times, same error |
你的对等节点不一定是全节点.
},120*1000); |
The same mistake over here. I think the nodes updated the geth with the version v1.1.7-99cb655f which is a build of the Develop branch of github bsc, since all the peers give name Geth / v1.1.7-99cb655f / linux-amd64 / go1.17.2 |
@machavez2086 i confirm that the issue was present also in 1.1.6. We switched to Moralis |
If you're not connected to a light server, data retrievals won't work. The only solution is to wait until a server serves you. |
Sometimes it works, but only when within the list of peers there is one other than Geth / v1.1.7-99cb655f. If you could put some rule so that it only accepts versions of peers smaller than v1.1.7-99 it would work, but I think that most of the peer servers have that compilation. The Developer branch has already changed to a compilation that should work, but until the full nodes do not update with that compilation I do not see a possible solution, except for some configuration that can select peers with compilation less than v1.1.7-99 .. |
I think it may caused by #640. The fullnode that the light client connected with has switch fullnode who do not have MPT, so can not service eth_getBalance, and light client disconnected them. |
how do you run this ? bash? |
Geth/v1.1.7-74f6b613/linux-amd64/go1.16.10 same issue light node It was still available yesterday |
works for me i wiped my data directory, ran the genesis command again, opened the peer port
not sure what exactly made it work for me because I changed all of those things at once (whoops), but oughta help if any of you are stuck on this |
☝️ nevermind, this helped but I'm still getting 5s execution timeouts and:
|
UP |
I think I ran into the same problem. Can anyone help me? Thanks. |
So, is noone serving lightnodes anymore or what is going on? |
Do you know what the problem is? Can you count on a fix? When will version 1.1.9 be released? |
same problem while using version 1.1.9 |
I also have the same problem 🤦♂️ |
Same issue here!
|
same problem while using version 1.1.15 |
This https://gist.github.com/rfikki/e2a8c47f4460668557b1e3ec8bae9c11 works in my case |
@MatusKysel can you track this issue as well with your peer filtering work. |
I think there is no enough light nodes on the network, if you need to have access to state, I guess you need to run "normal" node or subscribe to some API service |
I am using a light node v1.1.7, when sending requests to GetBalance, the following error occurs:
WARN [01-06|17:29:47.817] Served eth_getBalance reqid=1 t=3.0091902s err="getDeleteStateObject (295e26495cef6f69dfa69911d9d8e4f3bbadb89a) error: no suitable peers available"
before that there were such errors:
WARN [01-06|14:33:28.035] Served eth_call reqid=1 t=21.046081163s err="execution aborted (timeout = 5s)" X-Forwarded-For=nil
net.peerCount
returns 16.firewall is inactive.
started geth with arguments:
--config=D:\config.toml --metrics --metrics.addr 0.0.0.0 --cache 8192 --syncmode light --diffsync
config.toml:
The text was updated successfully, but these errors were encountered: