Open johnhckuo opened 12 months ago
Are you running rpcdaemon
separately? Are you giving it --datadir
flag?
Faced the same issue. I was running rpcdaemon
as a separate container, and the fix was to add --datadir
and use tini
to run rpcdaemon
. Need to have a different pid than erigon
process - otherwise you'll get the below error:
mdbx_lck_seize:31231 lock-against-without-lck, err 11
[EROR] [10-27|10:58:33.275] Erigon startup err="mdbx_env_open: resource temporarily unavailable, label: chaindata, trace: [kv_mdbx.go:293 node.go:365 node.go:368 backend.go:233 node.go:122 main.go:80 make_app.go:43 command.go:274 app.go:332 app.go:309 main.go:41 proc.go:250 asm_amd64.s:1598]"
mdbx_env_open: resource temporarily unavailable, label: chaindata, trace: [kv_mdbx.go:293 node.go:365 node.go:368 backend.go:233 node.go:122 main.go:80 make_app.go:43 command.go:274 app.go:332 app.go:309 main.go:41 proc.go:250 asm_amd64.s:1598]
[INFO] [10-27|10:59:06.621] logging to file system log dir=/data/erigon/logs file prefix=erigon log level=info json=false
System information
Erigon version: v2.52.5
OS & Version: Linux
Erigon Command (with flags/config): ./build/bin/erigon --http.api=eth,engine,erigon,web3,net,debug,trace,txpool,parity
Consensus Layer: none
Chain/Network: ETH Goerli
Expected behaviour
trace_block
should return successfully with correct block numberActual behaviour
rpc error:
Erigon node error log:
Steps to reproduce the behaviour
Starts up Erigon v2.52.5, and curl
trace_block
endpoint on Goerli with correct block number, then node will panic.Backtrace