-
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
Protocol eth/67 failed #1526
Comments
Hello @seonggwonyoon, looks like you are running on mainnet. Please note that it is not recommend for mainnet to use this version, especially validator, since more test is needed to make sure it is stable. |
Sorry, I raised the log level to warning in this commit: The node can still work, I did not expect there would be so many logs... |
It works fine. thank you |
I downloaded the just released v1.2.0 and ran it, but a
Protocol eth/67 failed
Warning appears as shown below.There's actually nothing wrong with syncing blocks.
Command
#!/bin/bash /root/geth --config /bsc/config.toml --datadir /bsc/node --datadir.ancient /bsc/node/geth/chaindata/ancient --cache 20000 --rpc.allow-unprotected-txs --txlookuplimit 0
System information
Geth version: v1.2.0
OS & Version: Linux (Ubuntu 22.04)
Commit hash : 30c298f
Logs
The text was updated successfully, but these errors were encountered: