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’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[HOLESKY PECTRA] exception trace to look at from external validator #9169

Open
rolfyone opened this issue Feb 24, 2025 · 1 comment
Open
Assignees

Comments

@rolfyone
Copy link
Contributor

│ teku at tech.pegasys.teku.validator.coordinator.ValidatorApiHandler.sendSignedAttestations(ValidatorApiHandler.java:584) ~[teku-beacon-validator-25.2.0.jar:25.2.0]                                        │
│ teku at java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(Unknown Source) ~[?:?]                                                                                                            │
│ teku at java.base/java.lang.reflect.Method.invoke(Unknown Source) ~[?:?]                                                                                                                                   │
│ geth {"t":"2025-02-24T22:47:21.532597942Z","lvl":"info","msg":"Chain head was updated","number":"3419870","hash":"0xade84a8cf42ee766ce4639bf9da07a5d0e7ecb2e80edc298c4d4a70577110fdf","root":"0x6e9b0b3779 │
│ teku at tech.pegasys.teku.infrastructure.events.DirectEventDeliverer.executeMethod(DirectEventDeliverer.java:74) ~[teku-infrastructure-events-25.2.0.jar:25.2.0]                                           │
│ geth {"t":"2025-02-24T22:47:21.609553151Z","lvl":"info","msg":"Imported new potential chain segment","number":"3419871","hash":"0x08a1be6b7532def6c02d2408380963e54d68f551d2c925d1bf5a424403931d03","block │
│ geth {"t":"2025-02-24T22:47:21.903806503Z","lvl":"info","msg":"Chain head was updated","number":"3419871","hash":"0x08a1be6b7532def6c02d2408380963e54d68f551d2c925d1bf5a424403931d03","root":"0xa0a3ed45ae │
│ geth {"t":"2025-02-24T22:47:22.009650927Z","lvl":"info","msg":"Imported new potential chain segment","number":"3419872","hash":"0xa8b0a41118a3fb8ea33e1284c135f12556c10c89676b77a55cba8370a0d8532e","block │
│ teku at tech.pegasys.teku.infrastructure.events.DirectEventDeliverer.deliverToWithResponse(DirectEventDeliverer.java:67) ~[teku-infrastructure-events-25.2.0.jar:25.2.0]                                   │
│ teku at tech.pegasys.teku.infrastructure.events.AsyncEventDeliverer.lambda$deliverToWithResponse$1(AsyncEventDeliverer.java:80) ~[teku-infrastructure-events-25.2.0.jar:25.2.0]                            │
│ teku at tech.pegasys.teku.infrastructure.events.AsyncEventDeliverer$QueueReader.deliverNextEvent(AsyncEventDeliverer.java:125) ~[teku-infrastructure-events-25.2.0.jar:25.2.0]                             │
│ teku at tech.pegasys.teku.infrastructure.events.AsyncEventDeliverer$QueueReader.run(AsyncEventDeliverer.java:116) ~[teku-infrastructure-events-25.2.0.jar:25.2.0]                                          │
│ teku at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) ~[?:?]                                                                                                                 │
│ teku at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) ~[?:?]
 Caused by: java.lang.IllegalStateException: Single attestation is not supported

also from a holesky-validator node to investigate

@mehdi-aouadi
Copy link
Contributor

mehdi-aouadi commented Mar 3, 2025

This is caused by the Performance Tracker which rejects Single Attestations.
In a normal scenario we should not supply a Single (non converted attestation) to it but it looks like there was an edge case that triggered this.
@rolfyone On which node did this happen? I searched the grafana logs and in some log files (all the Holesky nodes running geth ad EL since I see some geth logs) but can't find any trace of this happening. It would be really helpful to get the whole context and dig further
EDIT: Never mind, I found the initial report from TG

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants