You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
difficult to start teku / reth pair on sepolia due to the following error:
Unsure if it happens on other EL / CL, but does consistently apparently occur with teku / reth.
2024-12-09 05:21:13.723 INFO - Quartz scheduler 'QuartzScheduler' initialized from an externally provided properties instance.
2024-12-09 05:21:13.723 INFO - Quartz scheduler version: 2.3.2
2024-12-09 05:21:13.758 INFO - Initializing storage
2024-12-09 05:21:14.118 INFO - Storage initialization complete
2024-12-09 05:21:14.119 WARN - Ignoring weak subjectivity period check (--ignore-weak-subjectivity-period-enabled). Syncing from outside of the weak subjectivity period is considered UNSAFE.
2024-12-09 05:21:14.134 INFO - Loaded C-KZG-4844 library
2024-12-09 05:21:16.408 INFO - BLS: loaded BLST library
2024-12-09 05:21:16.660 INFO - Completed regeneration of state for block 0x42a176d41c1f497dcfe9a47d58ec5a78f1c787ba87dc1428afc7dcf46b6f82ed at slot 6496512 by replaying 30 blocks. Took 418ms
2024-12-09 05:21:16.858 INFO - Execution Client is online
2024-12-09 05:21:16.892 INFO - Loading generated p2p private key from: generated-node-key
2024-12-09 05:21:16.897 FATAL - Exiting due to fatal error in fork choice
java.util.concurrent.CompletionException: tech.pegasys.teku.infrastructure.exceptions.FatalServiceFailureException: Optimistic sync finalized an invalid transition block. Unable to recover.
at java.base/java.util.concurrent.CompletableFuture.encodeRelay(CompletableFuture.java:368) ~[?:?]
at java.base/java.util.concurrent.CompletableFuture.completeRelay(CompletableFuture.java:377) ~[?:?]
at java.base/java.util.concurrent.CompletableFuture$UniCompose.tryFire(CompletableFuture.java:1152) ~[?:?]
at java.base/java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:510) ~[?:?]
at java.base/java.util.concurrent.CompletableFuture.complete(CompletableFuture.java:2179) ~[?:?]
at tech.pegasys.teku.infrastructure.async.SafeFuture.lambda$propagateResult$3(SafeFuture.java:147) ~[teku-infrastructure-async-24.10.3.jar:24.10.3]
at java.base/java.util.concurrent.CompletableFuture.uniWhenComplete(CompletableFuture.java:863) ~[?:?]
at java.base/java.util.concurrent.CompletableFuture$UniWhenComplete.tryFire(CompletableFuture.java:841) ~[?:?]
at java.base/java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:510) ~[?:?]
at java.base/java.util.concurrent.CompletableFuture.complete(CompletableFuture.java:2179) ~[?:?]
Caused by: tech.pegasys.teku.infrastructure.exceptions.FatalServiceFailureException: Optimistic sync finalized an invalid transition block. Unable to recover.
at tech.pegasys.teku.statetransition.forkchoice.MergeTransitionBlockValidator.lambda$verifyFinalizedTransitionBlock$2(MergeTransitionBlockValidator.java:100) ~[teku-ethereum-statetransition-24.10.3.jar:24.10.3]
at java.base/java.util.concurrent.CompletableFuture$UniCompose.tryFire(CompletableFuture.java:1150) ~[?:?]
at java.base/java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:510) ~[?:?]
at java.base/java.util.concurrent.CompletableFuture.complete(CompletableFuture.java:2179) ~[?:?]
at tech.pegasys.teku.infrastructure.async.SafeFuture.lambda$propagateResult$3(SafeFuture.java:147) ~[teku-infrastructure-async-24.10.3.jar:24.10.3]
at java.base/java.util.concurrent.CompletableFuture.uniWhenComplete(CompletableFuture.java:863) ~[?:?]
at java.base/java.util.concurrent.CompletableFuture$UniWhenComplete.tryFire(CompletableFuture.java:841) ~[?:?]
at java.base/java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:510) ~[?:?]
at java.base/java.util.concurrent.CompletableFuture.complete(CompletableFuture.java:2179) ~[?:?]
Causing a customer significant issues, will put to top of current for investigation.
The text was updated successfully, but these errors were encountered:
difficult to start teku / reth pair on sepolia due to the following error:
Unsure if it happens on other EL / CL, but does consistently apparently occur with teku / reth.
Causing a customer significant issues, will put to top of current for investigation.
The text was updated successfully, but these errors were encountered: