mirror of https://gitlab.com/pulsechaincom/erigon-pulse.git synced 2025-01-20 09:21:11 +00:00

History

p2p: refactor peer errors to propagate with a DiscReason (#8089 )

Improve p2p error handling to propagate errors
from the origin up the call chain the Server peer removal code
using a new PeerError type containing a DiscReason and a more detailed
description.

The origin can be tracked down using PeerErrorCode (code) and DiscReason
(reason)
which looks like this in the log:

> [TRACE] [08-28|16:33:40.205] Removing p2p peer peercount=0
url=enode://d399f4b...@1.2.3.4:30303 duration=6.901ms
err="PeerError(code=remote disconnect reason, reason=too many peers,
err=<nil>, message=Peer.run got a remote DiscReason)"

2023-08-31 16:45:23 +01:00

sentry

p2p: refactor peer errors to propagate with a DiscReason (#8089 )

2023-08-31 16:45:23 +01:00

main.go

mdbx_to_mdbx: to use logger (#7860 )

2023-07-09 08:04:20 +01:00

README.md

Sentry doc (#5040 )

2022-08-13 21:37:51 +07:00

README.md

Sentry - component to

In the root of Erigon project, use this command to build the sentry:

make sentry

There are two modes in which the program can be run - with external p2p sentry, or with internal p2p sentry (also called combined). Ethereum mainnet configuration is currently hard-coded.

Running with an external p2p sentry

./buid/bin/sentry

./buid/bin/sentry --datadir=<sentry_datadir>

The command above specifies --datadir option - directory where the database files will be written (it doesn't need access to Erion's datadir). These two options will need to be specified regardless of the mode the program is run. This specific command above assumes and external p2p sentry running on the same computer listening to the port 9091. In order to use a p2p sentry on a different computer, or a different port (or both), the option --sentry.api.addr can be used. For example:

./buid/bin/sentry --datadir=<sentry1_datadir> --sentry.api.addr=localhost:9091
./buid/bin/sentry --datadir=<sentry2_datadir> --sentry.api.addr=localhost:9191
./build/bin/erigon --sentry.api.addr="localhost:9091,localhost:9191"

The command above will expect the p2p sentry running on the same computer, but on the port 9091

Options --nat, --port, --staticpeers, --netrestrict, --discovery are also available.

We are currently testing against two implementations of the p2p sentry - one internal to Erigon, and another - written in Rust as a part of rust-ethereum: https://github.com/rust-ethereum/sentry In order to run the internal sentry, use the following command: