Closed clsdubai closed 1 year ago
same problem....
same problem :(
What to do now? We tried to upgrade the node, restarting multiple times, same error
你的对等节点不一定是全节点. 比如我在我的full node执行了如下代码 setInterval(function () { var OldHigh = new Array(); var p = admin.peers; for (var n = 0; n < p.length; n++) { OldHigh.push(p[n].network.remoteAddress+p[n].protocols.eth.difficulty); } setTimeout(function(){ var p = admin.peers; for (var n = 0; n < p.length; n++) { if(OldHigh.indexOf(p[n].network.remoteAddress+p[n].protocols.eth.difficulty) == -1 && p[n].protocols.eth.difficulty > admin.nodeInfo.protocols.eth.difficulty-100 ) continue;
console.log("移除节点:",p[n].network.remoteAddress);
admin.removePeer(p[n].enode);
}
},60*1000);
},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 I did the build from scratch of the geth of the develop branch and mount a Light node from scratch, but it gives the same error. I think that's the cause, I don't know what the solution would be.
@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. Although light sometimes worked without opening the ports to the public, I did eventually get this error. When I opened the ports, and restarted geth, the error went away
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 https://github.com/binance-chain/bsc/pull/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.
你的对等节点不一定是全节点. 比如我在我的full node执行了如下代码 setInterval(function () { var OldHigh = new Array(); var p = admin.peers; for (var n = 0; n < p.length; n++) { OldHigh.push(p[n].network.remoteAddress+p[n].protocols.eth.difficulty); } setTimeout(function(){ var p = admin.peers; for (var n = 0; n < p.length; n++) { if(OldHigh.indexOf(p[n].network.remoteAddress+p[n].protocols.eth.difficulty) == -1 && p[n].protocols.eth.difficulty > admin.nodeInfo.protocols.eth.difficulty-100 ) continue;
console.log("移除节点:",p[n].network.remoteAddress); admin.removePeer(p[n].enode); } },60*1000);
},120*1000); 并且...设置了不服务轻节点.. -_,
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
iptables -I INPUT -p tcp --dport 30311 -j ACCEPT
iptables -I INPUT -p udp --dport 30311 -j ACCEPT
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
:point_up: nevermind, this helped but I'm still getting 5s execution timeouts and:
err="getDeleteStateObject (0000000000000000000000000000000000000000) error: no suitable peers available" X-Forwarded-For=nil
UP Function eth.GetBalance("any_address") return getDeleteStateObject error: no suitable peers available. Everything else works as it should. UPDATE: Only the block receiving function works. Everything else no longer works in Light mode
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? Peers - 1 or not at all.
same problem while using version 1.1.9
I also have the same problem 🤦♂️
Same issue here!
INFO [05-13|08:38:35.422] Imported new block headers count=1 elapsed="258.737µs" number=17,762,231 hash=7b4938..179586
INFO [05-13|08:38:38.451] Imported new block headers count=1 elapsed="389.851µs" number=17,762,232 hash=c959e0..4af702
WARN [05-13|08:38:39.432] Served eth_call reqid=1053 t=18.007552483s err="getDeleteStateObject (0000000000000000000000000000000000000000) error: no suitable peers available" X-Forwarded-For=nil
WARN [05-13|08:38:39.432] Served eth_call reqid=1053 t=18.007549386s err="getDeleteStateObject (0000000000000000000000000000000000000000) error: no suitable peers available"
INFO [05-13|08:38:41.245] Imported new block headers count=1 elapsed="369.497µs" number=17,762,233 hash=4ea6b2..b6a0dc
INFO [05-13|08:38:44.206] Imported new block headers count=1 elapsed="331.534µs" number=17,762,234 hash=bdf708..a04b76
INFO [05-13|08:38:47.298] Imported new block headers count=1 elapsed="380.17µs" number=17,762,235 hash=afd6ff..a4280f
INFO [05-13|08:38:50.359] Imported new block headers count=1 elapsed="417.712µs" number=17,762,236 hash=8ed68c..101748
INFO [05-13|08:38:53.434] Imported new block headers count=1 elapsed="555.957µs" number=17,762,237 hash=683c81..1281bd
INFO [05-13|08:38:56.570] Imported new block headers count=1 elapsed="375.626µs" number=17,762,238 hash=335492..c994a5
INFO [05-13|08:38:59.337] Imported new block headers count=1 elapsed=1.325ms number=17,762,239 hash=eeee1d..6329a5
INFO [05-13|08:39:02.416] Imported new block headers count=1 elapsed="410.709µs" number=17,762,240 hash=810d5f..2fe2eb
INFO [05-13|08:39:05.359] Imported new block headers count=1 elapsed="382.134µs" number=17,762,241 hash=91e3e1..8506fa
WARN [05-13|08:39:07.438] Served eth_call reqid=1063 t=18.004659844s err="getDeleteStateObject (0000000000000000000000000000000000000000) error: no suitable peers available" X-Forwarded-For=nil
WARN [05-13|08:39:07.438] Served eth_call reqid=1063 t=18.00465677s err="getDeleteStateObject (0000000000000000000000000000000000000000) error: no suitable peers available"
INFO [05-13|08:39:08.782] Imported new block headers count=1 elapsed="253.203µs" number=17,762,242 hash=90e046..de6d06
INFO [05-13|08:39:11.366] Imported new block headers count=1 elapsed="306.499µs" number=17,762,243 hash=6b12c2..c50bf8
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: