From 94f4e9b8d3e1124b573dc74ca98c4d4972bd8c7c Mon Sep 17 00:00:00 2001 From: maeliosakyne <63511989+maeliosakyne@users.noreply.github.com> Date: Wed, 18 Oct 2023 17:11:46 +0100 Subject: [PATCH] Maeliosa/broken links (#250) * Lodestar warning logs added to errors page * Update docs/int/faq/errors.mdx removed second lodestar warning Co-authored-by: Thomas H <107747791+thomasheremans@users.noreply.github.com> * Update docs/int/faq/errors.mdx Co-authored-by: Thomas H <107747791+thomasheremans@users.noreply.github.com> * second lodestar warning removed * issue #240 #243 #247 * broken link fixed --------- Co-authored-by: Maeliosa Co-authored-by: Thomas H <107747791+thomasheremans@users.noreply.github.com> --- docs/int/faq/errors.mdx | 14 ++++++++++++- docs/int/quickstart/advanced/prysm-vc.md | 26 ------------------------ 2 files changed, 13 insertions(+), 27 deletions(-) delete mode 100644 docs/int/quickstart/advanced/prysm-vc.md diff --git a/docs/int/faq/errors.mdx b/docs/int/faq/errors.mdx index 26b36ec5e0..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 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.
@@ -398,4 +398,16 @@ 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{" "} 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 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 - ```