Open YuXiaoCoder opened 6 months ago
time="2024-03-16 19:21:23" level=warning msg="removing invalid exit from pool" error="non-active validator cannot exit"
time="2024-03-16 19:21:23" level=warning msg="removing invalid exit from pool" error="non-active validator cannot exit"
time="2024-03-17 05:49:09" level=warning msg="Could not process attestation for fork choice" aggregationCount=12 beaconBlockRoot=0x1ced048b0824 committeeIndex=28 error="could not process attestation: target epoch 270315 does not match current epoch 270317 or prev epoch 270316" prefix=blockchain slot=8650098 targetRoot=0x81a453a2689a
time="2024-03-17 09:45:57" level=warning msg="Could not process attestation for fork choice" aggregationCount=21 beaconBlockRoot=0x95e0c9f6c5f1 committeeIndex=61 error="could not process attestation: target epoch 270352 does not match current epoch 270354 or prev epoch 270353" prefix=blockchain slot=8651290 targetRoot=0x961c30a3eafc
time="2024-03-17 09:52:21" level=warning msg="Could not process attestation for fork choice" aggregationCount=26 beaconBlockRoot=0x909b757fb815 committeeIndex=8 error="could not process attestation: target epoch 270353 does not match current epoch 270355 or prev epoch 270354" prefix=blockchain slot=8651322 targetRoot=0x1336dbe36b51
time="2024-03-17 11:41:09" level=warning msg="Could not process attestation for fork choice" aggregationCount=2 beaconBlockRoot=0x998ff0d073c2 committeeIndex=49 error="could not process attestation: target epoch 270370 does not match current epoch 270372 or prev epoch 270371" prefix=blockchain slot=8651868 targetRoot=0xa4f53f9738fe
UPDATE 2024-03-21 17:32:00: After watching for a while, I don't see that my attestations are being affected.
I have similar log output on my beacon-chain running the same software Prysm (5.0.1) and Geth (1.13.14). I have two validators running (25044) and (392415) on Ubuntu 22.04.4 LTS in a virtual machine.
[2024-03-21 16:13:09] WARN blockchain: Could not process attestation for fork choice aggregationCount=478 beaconBlockRoot=0x5aa5f3ffc30f committeeIndex=46 error=could not process attestation: target epoch 271425 does not match current epoch 271427 or prev epoch 271426 slot=8685627 targetRoot=0xd02c6023e8de
[2024-03-21 16:13:09] WARN blockchain: Could not process attestation for fork choice aggregationCount=477 beaconBlockRoot=0x5aa5f3ffc30f committeeIndex=27 error=could not process attestation: target epoch 271425 does not match current epoch 271427 or prev epoch 271426 slot=8685627 targetRoot=0xd02c6023e8de
[2024-03-21 16:13:09] WARN blockchain: Could not process attestation for fork choice aggregationCount=476 beaconBlockRoot=0x5aa5f3ffc30f committeeIndex=30 error=could not process attestation: target epoch 271425 does not match current epoch 271427 or prev epoch 271426 slot=8685627 targetRoot=0xd02c6023e8de
[2024-03-21 16:13:09] WARN blockchain: Could not process attestation for fork choice aggregationCount=472 beaconBlockRoot=0xad7632c4ef88 committeeIndex=42 error=could not process attestation: target epoch 271425 does not match current epoch 271427 or prev epoch 271426 slot=8685622 targetRoot=0xd02c6023e8de
(removed)
[2024-03-21 16:25:57] WARN blockchain: Could not process attestation for fork choice aggregationCount=473 beaconBlockRoot=0x03e8d3b4f8a3 committeeIndex=50 error=could not process attestation: target epoch 271427 does not match current epoch 271429 or prev epoch 271428 slot=8685690 targetRoot=0x9525a83c89e6
(removed)
[2024-03-21 16:32:21] WARN blockchain: Could not process attestation for fork choice aggregationCount=474 beaconBlockRoot=0x1adbc63bca84 committeeIndex=56 error=could not process attestation: target epoch 271428 does not match current epoch 271430 or prev epoch 271429 slot=8685722 targetRoot=0xb9bb48a530ff
(removed)
[2024-03-21 16:45:09] WARN blockchain: Could not process attestation for fork choice aggregationCount=92 beaconBlockRoot=0x59b40efc46a7 committeeIndex=9 error=could not process attestation: target epoch 271430 does not match current epoch 271432 or prev epoch 271431 slot=8685788 targetRoot=0x063a32f9d74a
*Note timestamps and gaps.
Also, I had shutdown and restarted my validators prior to these logs in order to increase hard drive space on the virtual machine running these. You will see some missed attestations while things sync'ed again. I noticed the messages when I was monitoring the logs to ensure everything was okay. I do not know how long the messages have been occurring. I didn't notice them during the Dencun fork but was only watching for about an hour.
I am only an end-user so I can't offer any additional insight. Please let me know if you need additional information to help with this issue.
@terencechain @prestonvanloon I'm an end user and I've been disturbed for a long time, can you help me?
@YuXiaoCoder Maybe try the Discord channel: Prysm Ethereum Client
Describe the bug
GETH Version:
v1.13.14
Beacon Version:v5.0.1
My beacon service reports the following error log, which prevents it from processing the validator's request to submit a attestation and causes my validator to lose the attestation
Validator Version:
v5.0.0
Has this worked before in a previous version?
🔬 Minimal Reproduction
No response
Error
No response
Platform(s)
No response
What version of Prysm are you running? (Which release)
No response
Anything else relevant (validator index / public key)?
No response