We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Erigon version: v2.60.10
OS & Version: Linux
Commit hash:
Erigon Command (with flags/config):
Consensus Layer:
Consensus Layer Command (with flags/config):
Chain/Network:
run cmd:
/node/archive/ethereum/bin/erigon --datadir=/node/archive/ethereum/erigon --chain=mainnet --db.size.limit=8TB --prune=disabled --log.dir.verbosity error --authrpc.jwtsecret=/node/archive/ethereum/erigon/jwt.hex --rpc.gascap=600000000 --rpc.evmtimeout=30s --rpc.batch.limit=100 --rpc.returndata.limit=104857600 --txpool.globalslots 1000000 --txpool.globalbasefeeslots 3000000 --txpool.globalqueue 3000000 --http=true --http.api eth,net,web3,debug,trace,txpool --http.addr 0.0.0.0 --http.corsdomain * --http.vhosts * --ws --authrpc.addr localhost --port=21300 --http.port 21301 --ws.port 21302 --private.api.addr= --authrpc.port=21303 --torrent.port=21304 --p2p.allowed-ports 21306 --internalcl --caplin.archive --caplin.backfilling.blob.no-pruning --caplin.backfilling.blob --caplin.backfilling --beacon.api=beacon,builder,config,debug,node,validator,lighthouse --beacon.api.port 21307 --beacon.api.addr 0.0.0.0 --diagnostics.disabled
The node runs and synchronizes normally, but caplin does not listen to the port, and ss does not find port 21307 information when checking the port
[backtrace]
The text was updated successfully, but these errors were encountered:
There should be a request for caplin beacon rpc, which makes caplin port monitoring unstable and then in a non-listeningstate
Sorry, something went wrong.
No branches or pull requests
System information
Erigon version: v2.60.10
OS & Version: Linux
Commit hash:
Erigon Command (with flags/config):
Consensus Layer:
Consensus Layer Command (with flags/config):
Chain/Network:
Expected behaviour
run cmd:
The node runs and synchronizes normally, but caplin does not listen to the port, and ss does not find port 21307 information when checking the port
Actual behaviour
Steps to reproduce the behaviour
Backtrace
The text was updated successfully, but these errors were encountered: