From e7d77ea15a48246d23876cd8af1dd82630d3520c Mon Sep 17 00:00:00 2001 From: Maeliosa Date: Thu, 10 Aug 2023 16:43:05 +0100 Subject: [PATCH 1/7] Lodestar warning logs added to errors page --- docs/int/faq/errors.mdx | 19 +++++++++++++++++++ 1 file changed, 19 insertions(+) diff --git a/docs/int/faq/errors.mdx b/docs/int/faq/errors.mdx index f7ac92f8f1..406686c5cd 100644 --- a/docs/int/faq/errors.mdx +++ b/docs/int/faq/errors.mdx @@ -386,4 +386,23 @@ docker compose logs The relay you are trying to connect to your peers via is offline or unreachable. + +
+ +

Lodestar

+ +
+ +

+ warn: Potential next epoch attester duties reorg slot=6861821, dutyEpoch=214432, priorDependentRoot=0xa08b0d0000000000000000000000000000000000000000000000000000000000, newDependentRoot=0xc68535c177b97d0f5ca2c2c50888563b6d63fe5c91ede07b86e96df93d64368f{" "} error +

+ Lodestar logs these warnings because charon is not able to return proper dependent_root value in getAttesterDuties API response whenever lodestar calls this API. This is because charon uses go-eth2-client for all the beacon API calls and it doesn't provide dependent_root value in responses. We have reported this to them here. +
+
+ +

+ warn: Potential next epoch attester duties reorg slot=6861822, dutyEpoch=214432, priorDependentRoot=0xa08b0d0000000000000000000000000000000000000000000000000000000000, newDependentRoot=0xc68535c177b97d0f5ca2c2c50888563b6d63fe5c91ede07b86e96df93d64368f {" "} error +

+ Lodestar logs these warnings because charon is not able to return proper dependent_root value in getAttesterDuties API response whenever lodestar calls this API. This is because charon uses go-eth2-client for all the beacon API calls and it doesn't provide dependent_root value in responses. We have reported this to them here. +
\ No newline at end of file From 5537ab3fdc9fe485c9d885afa699cadd678a256f Mon Sep 17 00:00:00 2001 From: maeliosakyne <63511989+maeliosakyne@users.noreply.github.com> Date: Wed, 16 Aug 2023 15:34:19 +0100 Subject: [PATCH 2/7] Update docs/int/faq/errors.mdx removed second lodestar warning Co-authored-by: Thomas H <107747791+thomasheremans@users.noreply.github.com> --- docs/int/faq/errors.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/int/faq/errors.mdx b/docs/int/faq/errors.mdx index 406686c5cd..129e774552 100644 --- a/docs/int/faq/errors.mdx +++ b/docs/int/faq/errors.mdx @@ -394,7 +394,7 @@ docker compose logs

- warn: Potential next epoch attester duties reorg slot=6861821, dutyEpoch=214432, priorDependentRoot=0xa08b0d0000000000000000000000000000000000000000000000000000000000, newDependentRoot=0xc68535c177b97d0f5ca2c2c50888563b6d63fe5c91ede07b86e96df93d64368f{" "} error + warn: Potential next epoch attester duties reorg{" "} error

Lodestar logs these warnings because charon is not able to return proper dependent_root value in getAttesterDuties API response whenever lodestar calls this API. This is because charon uses go-eth2-client for all the beacon API calls and it doesn't provide dependent_root value in responses. We have reported this to them here.
From d00ee3aedcdbcb4de3f7b09413c1f44acf1cd3d1 Mon Sep 17 00:00:00 2001 From: maeliosakyne <63511989+maeliosakyne@users.noreply.github.com> Date: Wed, 16 Aug 2023 15:34:31 +0100 Subject: [PATCH 3/7] Update docs/int/faq/errors.mdx Co-authored-by: Thomas H <107747791+thomasheremans@users.noreply.github.com> --- docs/int/faq/errors.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/int/faq/errors.mdx b/docs/int/faq/errors.mdx index 129e774552..e1e6bd895b 100644 --- a/docs/int/faq/errors.mdx +++ b/docs/int/faq/errors.mdx @@ -396,7 +396,7 @@ docker compose logs

warn: Potential next epoch attester duties reorg{" "} error

- Lodestar logs these warnings because charon is not able to return proper dependent_root value in getAttesterDuties API response whenever lodestar calls this API. This is because charon uses go-eth2-client for all the beacon API calls and it doesn't provide dependent_root value in responses. We have reported this to them here. + Lodestar logs these warnings because charon is not able to return proper dependent_root value in getAttesterDuties API response whenever lodestar calls this API. This is because charon uses go-eth2-client for all the beacon API calls and it doesn't provide dependent_root value in responses. We have reported this to them here.
From 8b32009869190cea9d224f1ac343d52a0a59c2e9 Mon Sep 17 00:00:00 2001 From: Maeliosa Date: Mon, 21 Aug 2023 14:00:49 +0100 Subject: [PATCH 4/7] second lodestar warning removed --- docs/int/faq/errors.mdx | 7 ------- 1 file changed, 7 deletions(-) diff --git a/docs/int/faq/errors.mdx b/docs/int/faq/errors.mdx index 406686c5cd..79165211a3 100644 --- a/docs/int/faq/errors.mdx +++ b/docs/int/faq/errors.mdx @@ -398,11 +398,4 @@ docker compose logs Lodestar logs these warnings because charon is not able to return proper dependent_root value in getAttesterDuties API response whenever lodestar calls this API. This is because charon uses go-eth2-client for all the beacon API calls and it doesn't provide dependent_root value in responses. We have reported this to them here.
-
- -

- warn: Potential next epoch attester duties reorg slot=6861822, dutyEpoch=214432, priorDependentRoot=0xa08b0d0000000000000000000000000000000000000000000000000000000000, newDependentRoot=0xc68535c177b97d0f5ca2c2c50888563b6d63fe5c91ede07b86e96df93d64368f {" "} error -

- Lodestar logs these warnings because charon is not able to return proper dependent_root value in getAttesterDuties API response whenever lodestar calls this API. This is because charon uses go-eth2-client for all the beacon API calls and it doesn't provide dependent_root value in responses. We have reported this to them here. -
\ No newline at end of file From 109213096311f8d1870331c39cfb2c2b91006cc1 Mon Sep 17 00:00:00 2001 From: Maeliosa Date: Wed, 23 Aug 2023 12:29:12 +0100 Subject: [PATCH 5/7] issue #240 #243 #247 --- docs/fr/eth.md | 1 - docs/int/faq/errors.mdx | 2 +- docs/int/quickstart/advanced/prysm-vc.md | 26 ------------------------ 3 files changed, 1 insertion(+), 28 deletions(-) delete mode 100644 docs/int/quickstart/advanced/prysm-vc.md diff --git a/docs/fr/eth.md b/docs/fr/eth.md index 9de166df23..31c972073f 100644 --- a/docs/fr/eth.md +++ b/docs/fr/eth.md @@ -86,7 +86,6 @@ This page serves material necessary to catch up with the current state of Ethere ### Serenity research posts -* [Sharding v2.1 Spec](https://notes.ethereum.org/SCIg8AH5SA-O4C1G1LYZHQ) * [Casper/Sharding/Beacon Chain FAQs](https://notes.ethereum.org/9MMuzWeFTTSg-3Tz_YeiBA?view) * [RETIRED! Sharding Phase 1 Spec](https://ethresear.ch/t/sharding-phase-1-spec-retired/1407/92) * [Exploring the Proposer/Collator Spec and Why it Was Retired](https://ethresear.ch/t/exploring-the-proposer-collator-split/1632/24) diff --git a/docs/int/faq/errors.mdx b/docs/int/faq/errors.mdx index 702560ed6f..6161f94e81 100644 --- a/docs/int/faq/errors.mdx +++ b/docs/int/faq/errors.mdx @@ -330,7 +330,7 @@ docker compose logs

Unauthorized: authentication error: invalid token

- You can ignore this error unless you have been contacted by the Obol Team with monitoring credentials. In that case, follow Step 6 of the quickstart. It does not affect cluster performance or prevent the cluster from running. + You can ignore this error unless you have been contacted by the Obol Team with monitoring credentials. In that case, follow Getting Started Monitoring your Node in our advanced guides. It does not affect cluster performance or prevent the cluster from running.
diff --git a/docs/int/quickstart/advanced/prysm-vc.md b/docs/int/quickstart/advanced/prysm-vc.md deleted file mode 100644 index 50e9b349fe..0000000000 --- a/docs/int/quickstart/advanced/prysm-vc.md +++ /dev/null @@ -1,26 +0,0 @@ ---- -sidebar_position: 6 -description: Run Prysm VCs in a DV ---- - -# Run Prysm validators as part of a DV Cluster - - -:::info -Support for prysm validator clients is in an experimental phase as prysm doesn't provide [complete support](https://github.com/prysmaticlabs/prysm/issues/11580) -for running their validator client on a beacon node REST API yet. Stay up to date on the latest support information for all validator clients at [dvt.obol.tech](https://dvt.obol.tech). -::: - -We have provided experimental support of prysm validator client through [compose-prysm.yml](https://github.com/ObolNetwork/charon-distributed-validator-cluster/blob/main/compose-prysm.yml) -which needs a prysm beacon node to work alongside a REST based beacon node. Here are the steps to test prysm in a DV Cluster: - -1. Run the following command: - ```sh - cp docker-compose.override.yml.sample docker-compose.override.yml - ``` -2. **Disable** the VCs in `docker-compose.override.yml` that are to be replaced by corresponding prysm VCs by un-commenting the `profiles` field -([more details on profiles](https://docs.docker.com/compose/profiles/)). Also disable the prysm VCs that are not required in the cluster in `docker-compose.override.yml`. -3. Run the following command: - ```sh - docker compose -f docker-compose.yml -f compose-prysm.yml -f docker-compose.override.yml up --build - ``` From b08633b22bdee9e07b46bb18ec4f3f2dacf92d0c Mon Sep 17 00:00:00 2001 From: Maeliosa Date: Wed, 18 Oct 2023 16:05:37 +0100 Subject: [PATCH 6/7] broken link fixed --- docs/int/faq/errors.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/int/faq/errors.mdx b/docs/int/faq/errors.mdx index b704ceba32..c526faa3d9 100644 --- a/docs/int/faq/errors.mdx +++ b/docs/int/faq/errors.mdx @@ -342,7 +342,7 @@ docker compose logs

Unauthorized: authentication error: invalid token

- You can ignore this error unless you have been contacted by the Obol Team with monitoring credentials. In that case, follow Getting Started Monitoring your Node in our advanced guides. It does not affect cluster performance or prevent the cluster from running. + You can ignore this error unless you have been contacted by the Obol Team with monitoring credentials. In that case, follow Getting Started Monitoring your Node in our advanced guides. It does not affect cluster performance or prevent the cluster from running.
From 52ca59f06ab5bf6aae4aafe8f32d0181c91e74f0 Mon Sep 17 00:00:00 2001 From: Maeliosa Date: Wed, 18 Oct 2023 16:46:54 +0100 Subject: [PATCH 7/7] broken link --- docs/int/faq/errors.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/int/faq/errors.mdx b/docs/int/faq/errors.mdx index c526faa3d9..df6d09e17e 100644 --- a/docs/int/faq/errors.mdx +++ b/docs/int/faq/errors.mdx @@ -342,7 +342,7 @@ docker compose logs

Unauthorized: authentication error: invalid token

- You can ignore this error unless you have been contacted by the Obol Team with monitoring credentials. In that case, follow Getting Started Monitoring your Node in our advanced guides. It does not affect cluster performance or prevent the cluster from running. + You can ignore this error unless you have been contacted by the Obol Team with monitoring credentials. In that case, follow Getting Started Monitoring your Node in our advanced guides. It does not affect cluster performance or prevent the cluster from running.