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

Blockscout crashes with Polygon Edge #1845

Open
pmualaba opened this issue Aug 23, 2023 · 4 comments
Open

Blockscout crashes with Polygon Edge #1845

pmualaba opened this issue Aug 23, 2023 · 4 comments

Comments

@pmualaba
Copy link

[ Subject of the issue ]

Description

Describe your issue in as much detail as possible here.

Deploying Blockscout v5.2.1-beta on Kubernetes together with a Hyperledger Besu node works fine.
But deploying the same Blockscout v5.2.1-beta on Kubernetes together with a Polygon Edge node (docker.io/0xpolygon/polygon-edge:0.8.1) crashes the Application indexer a few minutes after deploying the Blockscout Pod.

We already raised a ticket at blockscout which explains exactly what is happening here : blockscout/blockscout#8255

Your environment

  • OS and version: Linux
  • The version of the Polygon Edge: docker.io/0xpolygon/polygon-edge:0.8.1
    (Confirm the version of your Polygon edge client by running the following command: polygon-edge version --grpc-address GRPC_ADDRESS)
  • The branch that causes this issue.
  • Locally or Cloud hosted (which provider).
  • Please confirm if the validators are running under containerized environment (K8s, Docker, etc.).

Steps to reproduce

  • Tell us how to reproduce this issue.
  • Where the issue is, if you know.
  • Which commands triggered the issue, if any.
  • Provide us with the content of your genesis file.
  • Provide us with commands that you used to start your validators.
  • Provide us with the peer list of each of your validators by running the following command: polygon-edge peers list --grpc-address GRPC_ADDRESS.
  • Is the chain producing blocks and serving customers atm?

Expected behavior

  • Tell us what should happen.
  • Tell us what happened instead.

Logs

Provide us with debug logs from all of your validators by setting logging to debug output with: server --log-level debug

Proposed solution

If you have an idea on how to fix this issue, please write it down here, so we can begin discussing it

@NoVa-Toast
Copy link
Contributor

Use docker-compose-no-build-geth.yml and Change the RPC and the other :8545 Ended RPC to two different ones, DO NOT use ganache as it spams the rpcs with too big requests

@NoVa-Toast
Copy link
Contributor

But This is for the blockscout issues, Not polygon-edge

@nnlgsakib
Copy link

I also faced this problem when I connected blockscout directly to the validator node. Then I create an archive node and run blockscout with it.This process solved the problem

@goran-ethernal
Copy link
Collaborator

Do you still have issues with this?

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

4 participants