🦦
Erigon 2 Documentation
  • Welcome to Erigon 2
    • Disclaimer
    • Project Links
  • ELI5 NODES
    • How to run an Ethereum node
    • How to run a Gnosis Chain node
    • How to run a Polygon node
  • Basic usage
    • Getting started
      • Linux and MacOS
      • Windows
      • Docker
    • Usage
      • Type of Node
    • Upgrading from a previous version
    • Supported Networks
    • Default Ports and Firewalls
    • Otterscan
    • Wallet
  • Advanced Usage
    • Configure Erigon
    • Consensus Layer
      • Prysm
      • Lighthouse
      • JWT secret
      • Block production
    • Options
    • RPC daemon
    • TxPool
    • Sentry
    • Downloader
    • TLS Authentication
    • ❔FAQ
    • External resources
      • Erigon on a Raspberry Pi 4
  • DIAGNOSTIC TOOL
    • Introduction
    • Installation
    • Setup
    • User Interface
  • About
    • Contributing to Erigon
    • Donate
    • License
    • Privacy policy
Powered by GitBook
On this page
  • What happens if I interrupt the Erigon synchronization?
  • How to get diagnostic for bug report?
  • How to run local devnet?
  • Docker permissions error

Was this helpful?

  1. Advanced Usage

FAQ

Frequently Asked Questions

Last updated 1 year ago

Was this helpful?

What happens if I interrupt the Erigon synchronization?

Interrupting the synchronization process is not recommended, but it doesn't cause any major problems. Erigon will resume synchronization after restart.

Anyhow, in some rare cases the database could get corrupted.

How to get diagnostic for bug report?

  • Get stack trace: kill -SIGUSR1 <pid>, get trace and stop: kill -6 <pid>

  • Get CPU profiling: add --pprof flag run go tool pprof -png http://127.0.0.1:6060/debug/pprof/profile\?seconds\=20 > cpu.png

  • Get RAM profiling: add --pprof flag run go tool pprof -inuse_space -png http://127.0.0.1:6060/debug/pprof/heap > mem.png

How to run local devnet?

You can find a detailed explanation .

Docker permissions error

Docker uses user Erigon with UID/GID 1000 (for security reasons). You can see this user being created in the Dockerfile. Can fix by giving a host's user ownership of the folder, where the host's user UID/GID is the same as the docker's user UID/GID (1000). More details in this .

❔
post
here