Open mohamedmansour opened 2 years ago
This seems to be an issue with the prysm.sh script. The first step of the prysm.sh script is to check if there is a new update available. That step requires an internet connection.
Workaround
There are two things I think you can do as a workaround (either would work):
1) Manually specify the prysm version with an environment variable USE_PRYSM_VERSION=v2.0.6
2) Use the binary files directly rather than on the prysm.sh script. These files are downloaded to the dist/
directory.
Fix
I think the fix here is for the prysm.sh
to choose the highest previously downloaded binary to start if no specific version was requested and the latest release is unable to be determined. There are more reasons than local internet issues that could cause prysm.sh to fail to retrieve the latest version tag so this could be a bigger issue if not resolved.
🐞 Bug Report
Description
Power outage happened for two hours, and it automatically shut down my server safely when battery depleted in my UPS. It should have not crashed and continued checking for internet connection. Geth recovered really quickly at the end of 01:09AM with peers, meanwhile Prysm couldn't find internet connection at 1:10 and crashed.
🔬 Minimal Reproduction
10:12 PM - Power out, Internet Out, Backup Battery on 12:47 - Power on, Internet Out, Beacon attempting to retrying 12:49 - Power out again 01:09 - Power on, Internet still out 01:10 - Beacon exited, Failed to start eth2
🔥 Error
uptime
reboot logs
### prysm beacon logs Comparing with geth, it didn't crash and it found peers in 1:09:54: ## 🌍 Your Environment **Operating System:** **What version of Prysm are you running? (Which release)**