AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
Amd link deadline exceeded9/20/2023 The CPU is an AMD EPYC 24c/48t, which should be more than enough. I'm aware that's there's an issue with high memory usage when performing a backup however, you can see that there's a few massive CPU spikes, as well. I would suggest that you double check your CPU specs.įWIW: I received 2 of these "Could not retrieve pre state context deadline exceeded" errors within 10 to 25 minutes following a beacon DB backup invocation. Nowadays however the network has grown, and CPU needs to have enough processing power to keep up. This was not an issue while the network was small with a few thousand nodes in the network. I was only running 2 cores, and since I have more than 1 validator, at times my machine would have a hard time keeping up. We have identified the issue to be lack of CPU power. What version of Prysm are you running? (Which release)Īnything else relevant (validator index / public key)? slot=584827įeb 20 17:26:11 eths validator-v1.2.2: time=" 17:26:11" level=error msg="Could not submit slot signature to beacon node" error="rpc error: code = DeadlineExceeded desc = context deadline exceeded" prefix=validator slot=584828įeb 20 17:26:11 eths validator-v1.2.2: time=" 17:26:11" level=error msg="Could not request attestation to sign at slot" error="rpc error: code = DeadlineExceeded desc = context deadline exceeded" prefix=validator pubKey=0x98b.slot=584828Ģ Cores ( Intel(R) Xeon(R) Gold 6140 CPU 2.30GHz ( Cache Size 4MB) ) slot=584826įeb 20 17:25:59 eths validator-v1.2.2: time=" 17:25:59" level=error msg="Could not request attestation to sign at slot" error="rpc error: code = DeadlineExceeded desc = context deadline exceeded" prefix=validator pubKey=0x814. Feb 20 17:25:47 eths validator-v1.2.2: time=" 17:25:47" level=error msg="Could not request attestation to sign at slot" error="rpc error: code = DeadlineExceeded desc = context deadline exceeded" prefix=validator pubKey=0xa36.
0 Comments
Read More
Leave a Reply. |