lighthouse
lighthouse copied to clipboard
sigp
Quick sync startup from checkpoint failed
Description
Failed to start beacon node
Version
version：Lighthouse v4.6.0-1be5253
command：
./lighthouse bn
--network mainnet
--execution-endpoint http://localhost:8551
--execution-jwt /secrets/jwt.hex
--checkpoint-sync-url https://mainnet.checkpoint.sigp.io
--http
--datadir xxx
you need Lighthouse v5 or newer for mainnet
I upgraded the lighthouse version to 5.1.3, but it still cannot start.
how many checkpoint sync URLs have you tried?
could there be something blocking the request, like a firewall?
how many checkpoint sync URLs have you tried?
could there be something blocking the request, like a firewall?
I tried all mainnets except Nimbus.
I have successfully started it before, but after deleting all the previously downloaded data, problems occurred when I started it again. The configuration in the middle has not changed. By the way, I started it in a non-pledged form, and there is the following content in the command line:
--disable-deposit-contract-sync
Can you share the full command you start Lighthouse? The error code is Unexpected EOF. Do you see the same error code when you use a different checkpoint link?
Can you share the full command you start Lighthouse? The error code is
Unexpected EOF. Do you see the same error code when you use a different checkpoint link?
Ok.
version：Lighthouse v5.1.3-3058b96
command：
./lighthouse bn
--network mainnet
--execution-endpoint http://localhost:8551/
--execution-jwt /secrets/jwt.hex
--checkpoint-sync-url https://mainnet.checkpoint.sigp.io/
--disable-deposit-contract-sync
--http
--datadir xxx
I changed the checkpoint link and still got this error, as shown below。The top of the picture is the command I used to start the beacon node.
The picture below is the version information
Can you try to remove the ending slash in the url? i.e., --checkpoint-sync-url https://mainnet.checkpoint.sigp.io
您可以尝试删除网址中的结尾斜杠吗？ IE，
--checkpoint-sync-url https://mainnet.checkpoint.sigp.io
There is no slash at the end of my command line, but there is a slash in the error message URL.
That's strange. it should work and I just try that the checkpoint sync works. Do you have firewall blocks the connection as @michaelsproul sproul suggested?
Can you see if a simple command like below still return the same error:
./lighthouse bn --network mainnet --checkpoint-sync-url https://beaconstate.ethstaker.cc --purge-db
That's strange. it should work and I just try that the checkpoint sync works. Do you have firewall blocks the connection as @michaelsproul sproul suggested?
Can you see if a simple command like below still return the same error:
./lighthouse bn --network mainnet --checkpoint-sync-url https://beaconstate.ethstaker.cc --purge-db
Yes, still the same error.
It seems to be that something is blocking the connection. Do you have another internet connection option available? Try another ISP option if there is
@chengxingxi You can see what curl shows with this request, which is similar to what Lighthouse is trying to do.
curl -v -H "Accept: application/json" "https://mainnet.checkpoint.sigp.io/eth/v2/beacon/blocks/finalized"
As @chong-he says, it looks like a problem with your internet connection.
@chengxingxi您可以看到
curl此请求显示的内容，这与 Lighthouse 尝试做的类似。curl -v -H "Accept: application/json" "https://mainnet.checkpoint.sigp.io/eth/v2/beacon/blocks/finalized"作为@chong-he说，您的互联网连接似乎有问题。 The output result is like this：
The connection is stopped. The curl should return a long data with block info. From your screenshot it seems to indicate a connection to localhost (127.0.0.0)?
Do you have another internet option available? Try that.
The connection is stopped. The curl should return a long data with block info. From your screenshot it seems to indicate a connection to localhost (127.0.0.0)?
Do you have another internet option available? Try that.
Thank you, the node started normally after I changed the network.
I also want to ask a question. I used snapshot synchronization mode for almost a week, and the geth client kept displaying "Post-merge network, but no beacon client seen. Please launch one to follow the chain!" while the lighthouse client kept outputting. "INFO Searching for peers current_slot: 8768669, head_slot: 8768608, finalized_epoch: 274019, finalized_root: 0x581b…ef7e, peers: 1, service: slot_notifier" and similar content.
When I use the eth.syncing command to check, it shows that the current block is 0, as shown below.And I check that 1.7T of data has been downloaded. I check the Ethereum official website and it shows that using geth to synchronize in snapshot mode requires about 500G of hard disk size. . How should I check the downloaded data and know the progress of synchronization?
Looks like the sync is not progressing. Do you have peers on geth and Lighthouse? If you view the geth and Lighthouse logs you can see the sync progress
Looks like the sync is not progressing. Do you have peers on geth and Lighthouse? If you view the geth and Lighthouse logs you can see the sync progress
The beacon node has two log files,
The content of discv5 is as follows:
The content of libp2p is as follows:
It seems like they are reporting errors and not synchronizing properly. geth did not find the log file
How did you start Lighthouse and Geth? Please switch over to Discord for troubleshooting: https://discord.gg/cyAszAh
How did you start Lighthouse and Geth? Please switch over to Discord for troubleshooting: https://discord.gg/cyAszAh
The commands to start lighthouse are the same as before. geth command: geth --cache 4096 --authrpc.addr localhost --authrpc.port 8551 --authrpc.vhosts localhost --authrpc.jwtsecret /secret/jwt.hex --datadir /private/mux/ethereum
When you start geth it should show you the logs, post some logs and also Lighthouse beacon logs