-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
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
[BUG] Erigon startup EROR: mdbx_env_open: MDBX_TOO_LARGE #7367
Comments
hi.
|
Can confirm that I encountered the same problem on 2.43 even after setting db.size.limit, the machine has 32 cores and 128 GB of RAM, I'm running Erigon in a Docker container. edit: the ulimit inside the docker container is as follows:
Could one of these values be the problem? |
what is --db.pagesize ? |
--db.pagesize=16k |
make db-tools |
seems i fixed it by #7482 |
Still getting this on devel:
|
Output of stat
I'm not sure why it shows a pagesize of 4096 considering I am running Erigon v2.42.0 fine with --db.pagesize=16k with no errors. |
@paul-serdiuk
To change db pagesize: |
Doesn't --db.pagesize show an error when trying to open a database that was created with a different pagesize? Also, will Erigon show an error if the limit is reached? I hope the current DB is not borked by that. |
This fix works fine! Tested on BSC Chapel. |
I still met this issue in version
|
Your db is “ Pagesize: 4096” |
I know how large my Pagesize is. I was always using the default setting until I upgraded to the latest version. I also tried set
My server has 80GB of RAM and 4x2T RAID SSD. |
@WhymustIhaveaname see breaking change section in release notes: https://github.com/ledgerwatch/erigon/releases/tag/v2.55.0 and #7367 (comment) |
Thank you! It works after I set
|
System information
Erigon version:
./erigon --version
erigon version 2.43.0-dev-ef71909c
OS & Version: Windows/Linux/OSX
ubuntu:20.04
Commit hash:
ef71909
Erigon Command (with flags/config):
./erigon --datadir=./data --private.api.addr=0.0.0.0:9090 --http.addr=0.0.0.0 --http.vhosts=* --http.corsdomain=* --http.api=eth,erigon,web3,net,debug,trace,txpool --ws --log.dir.path=./logs/
Specific implementation steps
Problem Description
In the test, the current dev branch 2.43.0-dev-ef71909c, after initializing with genesis.json, an error is reported at startup
./erigon --datadir=./data --private.api.addr=0.0.0.0:9090 --http.addr=0.0.0.0 --http.vhosts=* --http.corsdomain=* --http.api=eth,erigon,web3,net,debug,trace,txpool --ws --log.dir.path=./logs/
Probability of recurrence
100%
Version comparison test
In version: 2.42.0-stable, this problem does not occur
Why the test for this question
We are the technical team from opside.network (A Decentralized ZK-RaaS Network.), we are exploring related technologies
The text was updated successfully, but these errors were encountered: