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
e.g. https://hivetests.ethdevops.io/viewer.html?suiteid=1711397722-d50036babc50796ef1719e295f3b3136.json&suitename=consensus&testid=2&file=%2Fresults%2Ferigon%2Fclient-12ec110ba712b8b92ee6437fe3f0de96b485e7a2ee13e8c2100e0c88c9302063.log
INFO] [03-24|13:39:42.924] Starting private RPC server on=127.0.0.1:9090 [INFO] [03-24|13:39:42.924] new subscription to logs established [INFO] [03-24|13:39:42.925] [txpool] Started [EROR] [03-24|13:39:42.927] catch panic err="runtime error: invalid memory address or nil pointer dereference" stack="[main.go:29 panic.go:914 panic.go:261 signal_unix.go:861 import_cmd.go:78 make_app.go:111 command.go:279 command.go:272 app.go:337 app.go:311 main.go:34 proc.go:267 asm_amd64.s:1650]" Running erigon with flags --log.console.verbosity=3 --fakepow --datadir /erigon-hive-datadir --db.size.limit 2GB --networkid 1337 --http --http.addr=0.0.0.0 --http.api=admin,debug,eth,net,txpool,web3 --ws --ws.port=8546 --txpool.blobslots=1000 --txpool.totalblobpoollimit=10000 --authrpc.addr=0.0.0.0 --authrpc.jwtsecret=/jwt.secret --snapshots=false --nat=none
The text was updated successfully, but these errors were encountered:
See also erigontech/erigon#9179 (comment)
Sorry, something went wrong.
Thanks guys! Looking into it
It would be nice if I had a full setup (inputs and commands) so I can reproduce it
No branches or pull requests
e.g. https://hivetests.ethdevops.io/viewer.html?suiteid=1711397722-d50036babc50796ef1719e295f3b3136.json&suitename=consensus&testid=2&file=%2Fresults%2Ferigon%2Fclient-12ec110ba712b8b92ee6437fe3f0de96b485e7a2ee13e8c2100e0c88c9302063.log
The text was updated successfully, but these errors were encountered: