Skip to content
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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Failed to propose block #5731

Closed
xrow opened this issue May 4, 2020 · 5 comments 路 Fixed by #5848
Closed

Failed to propose block #5731

xrow opened this issue May 4, 2020 · 5 comments 路 Fixed by #5848
Assignees
Labels
Bug Something isn't working Priority: Medium Medium priority item

Comments

@xrow
Copy link

xrow commented May 4, 2020

#4918 馃悶 Bug Report

Description

I saw a missed blocks of my validators. If I look in the logs I see this message:

Has this worked before in a previous version?

It might have been around for a while.

馃敩 Minimal Reproduction

I just wait for a missed proposed block.

馃敟 Error


time="2020-05-03 20:14:24" level=info msg="Previous epoch aggregated voting summary" attestationInclusionPercentage=0.01 correctlyVotedHeadPercentage=0.01 correctlyVotedSourcePercentage=0.01 correctlyVotedTargetPercentage=0.01 epoch=3545 prefix=validator
--
聽 | time="2020-05-03 20:14:26" level=info msg="New assignment" attesterSlot=113474 committeeIndex=2 epoch=3546 prefix=validator proposerSlots=[113482] pubKey=0xa09f182da02c status=ACTIVE validatorIndex=17351
聽 | time="2020-05-03 20:14:52" level=info msg="Submitted new attestations" AggregatorIndices=[] AttesterIndices=[17351] BeaconBlockRoot=0x9c2f66f34c40 CommitteeIndex=2 Slot=113474 SourceEpoch=3545 SourceRoot=0x7d503454a7a9 TargetEpoch=3546 TargetRoot=0x49d5d393f8cb prefix=validator
聽 | time="2020-05-03 20:16:27" level=error msg="Failed to request block from beacon node" blockSlot=113482 error="rpc error: code = Internal desc = Could not compute state root: could not calculate state root at slot 113481: could not process block: could not process block operation: could not process block attester slashings: unable to slash any validator despite confirmed attester slashing" prefix=validator pubKey=0xa09f182da02c
聽 | time="2020-05-03 20:20:48" level=info msg="Previous epoch voting summary" correctlyVotedHead=true correctlyVotedSource=true correctlyVotedTarget=true epoch=3546 inclusionDistance=1 inclusionSlot=113422 newBalance=32.12191223 oldBalance=32.121850736 percentChange="0.00019%" prefix=validator pubKey=0xa09f182da02ce9bd

馃實 Your Environment

Operating System:

  
linux
  

What version of Prysm are you running? (Which release)

  
alpha.6
  

Anything else relevant (validator index / public key)?
see logs

@xrow
Copy link
Author

xrow commented May 4, 2020

Here is a list of my validators https://beaconcha.in/dashboard?validators=17311,17343,17350,17351,17352,23859

Only 17351 had this issue once. The others suffered a missed blocks due downtime.

@xrow xrow changed the title Fails to propose block Failed to propose block May 4, 2020
@terencechain
Copy link
Member

A block was failed to propose because of a bad slashing object. @0xKiwi can you take a look here?

@0xKiwi
Copy link
Contributor

0xKiwi commented May 4, 2020

Wow, @xrow. You're not running a slasher? This was from validators connected to your own beacon node?

@xrow
Copy link
Author

xrow commented May 4, 2020

This was a log from a validator. A slasher was also there.

@prestonvanloon
Copy link
Member

Can we validate slashing objects before adding them to a block?

@0xKiwi 0xKiwi added Bug Something isn't working Priority: Medium Medium priority item labels May 11, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Something isn't working Priority: Medium Medium priority item
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants