Closed xtc0r closed 11 months ago
I switched back to Lukso cli 0.81 and erigon 2.45.3 and my node is syncing again.
[INFO] [12-07|14:51:13.242] logging to file system log dir=mainnet-data/execution/logs file prefix=erigon log level=info json=false
[INFO] [12-07|14:51:13.243] Starting metrics server addr=http://127.0.0.1:6060/debug/metrics/prometheus
[INFO] [12-07|14:51:13.243] Build info git_branch= git_tag= git_commit=
[INFO] [12-07|14:51:13.244] Maximum peer count ETH=100 total=100
[INFO] [12-07|14:51:13.244] starting HTTP APIs APIs=erigon,engine
[INFO] [12-07|14:51:13.244] torrent verbosity level=WRN
[INFO] [12-07|14:51:15.353] Set global gas cap cap=50000000
[INFO] [12-07|14:51:15.501] [Downloader] Runnning with ipv6-enabled=true ipv4-enabled=true download.rate=16mb upload.rate=4mb
[INFO] [12-07|14:51:15.501] Opening Database label=chaindata path=/home/basti/myLUKSOnode/mainnet-data/execution/chaindata
mdbx_setup_dxb:15946 filesize mismatch (expect 208896b/51p, have 2147483648b/524288p)
[INFO] [12-07|14:51:15.508] Initialised chain configuration config="{ChainID: 42, Homestead: 0, DAO: <nil>, Tangerine Whistle: 0, Spurious Dragon: 0, Byzantium: 0, Constantinople: 0, Petersburg: 0, Istanbul: 0, Muir Glacier: <nil>, Berlin: 0, London: 0, Arrow Glacier: <nil>, Gray Glacier: <nil>, Terminal Total Difficulty: 0, Merge Netsplit: <nil>, Shanghai: 1687969198, Cancun: <nil>, Prague: <nil>, Engine: unknown}" genesis=0x5df88817dfb9b00d8ef142370671e8a9bc00c548ab78fbaf205df53db2b24a26
[INFO] [12-07|14:51:15.517] Initialising Ethereum protocol network=42
[INFO] [12-07|14:51:15.517] Disk storage enabled for ethash DAGs dir=/home/basti/myLUKSOnode/mainnet-data/execution/ethash-dags count=2
[INFO] [12-07|14:51:15.527] new subscription to logs established
[INFO] [12-07|14:51:15.527] Starting private RPC server on=127.0.0.1:9098
[INFO] [12-07|14:51:15.528] rpc filters: subscribing to Erigon events
[INFO] [12-07|14:51:15.529] new subscription to newHeaders established
[INFO] [12-07|14:51:15.529] New txs subscriber joined
[INFO] [12-07|14:51:15.530] Reading JWT secret path=./configs/shared/secrets/jwt.hex
[INFO] [12-07|14:51:15.530] HTTP endpoint opened for Engine API url=127.0.0.1:8551 ws=true ws.compression=true
[INFO] [12-07|14:51:15.531] HTTP endpoint opened url=127.0.0.1:8545 ws=true ws.compression=true grpc=false
[INFO] [12-07|14:51:15.537] Started P2P networking version=68 self=enode://cef92b00b7eafb8d6f45bc657b09e259c1eb5137c803ed43486acbcb5cd35d35103871960d3ba84c62d882dc3870fea5ab27bc668ae04ae1c2eacf73111247bd@127.0.0.1:0 name=erigon/v2.45.1/linux-arm64/go1.20.4
[INFO] [12-07|14:51:15.539] [txpool] Started
[INFO] [12-07|14:51:15.540] [2/15 Headers] Waiting for Consensus Layer...
[INFO] [12-07|14:51:15.542] Started P2P networking version=67 self=enode://cef92b00b7eafb8d6f45bc657b09e259c1eb5137c803ed43486acbcb5cd35d35103871960d3ba84c62d882dc3870fea5ab27bc668ae04ae1c2eacf73111247bd@127.0.0.1:0 name=erigon/v2.45.1/linux-arm64/go1.20.4
[INFO] [12-07|14:51:48.956] [2/15 Headers] Downloading PoS headers... height=unknown hash=0x4a22578d17c47907ca368ae5f13eced86a559165ebdc4aec03a0ab28c27335cf requestId=1
[INFO] [12-07|14:52:15.530] [txpool] stat pending=0 baseFee=0 queued=0 alloc=29.8MB sys=56.3MB
[INFO] [12-07|14:53:15.517] [p2p] GoodPeers
[INFO] [12-07|14:53:15.530] [txpool] stat pending=0 baseFee=0 queued=0 alloc=32.0MB sys=56.3MB
[INFO] [12-07|14:54:15.529] [txpool] stat pending=0 baseFee=0 queued=0 alloc=38.6MB sys=81.4MB
[INFO] [12-07|14:54:45.531] [downloader] Downloaded PoS Headers now=1376892 blk/sec=294.400
[INFO] [12-07|14:55:15.518] [p2p] GoodPeers eth67=1
[INFO] [12-07|14:55:15.530] [downloader] Downloaded PoS Headers now=1368444 blk/sec=281.600
[INFO] [12-07|14:55:15.530] [txpool] stat pending=0 baseFee=0 queued=0 alloc=70.0MB sys=117.4MB
[INFO] [12-07|14:55:45.529] [downloader] Downloaded PoS Headers now=1358652 blk/sec=326.400
Hey, sorry for the inconvenience. Sadly, this issue could not be reproduced from our network team using the default installation version from the LUKSO CLI Version 0.14. (Erigon v2.55.0
)
Could you please provide the Erigon version, chip, and operating system that you tested on?
Did you, by any chance run the
lukso update
command? Updating fetches the latest upstream directly from the client's releases, while the installation only downloads the clients up to the latest version that was tested and verified by the team.
lukso update
for the clientI think a look at the logs is needed. Why is Erigon 2.55.1
expecting chainID = 1? this also leads to different genesis configuration.
Initialised chain configuration config="{ChainID: 1, Homestead: 1150000, DAO: 1920000, Tangerine Whistle: 2463000, Spurious Dragon: 2675000, Byzantium: 4370000, Constantinople: 7280000, Petersburg: 7280000, Istanbul: 9069000, Muir Glacier: 9200000, Berlin: 12244000, London: 12965000, Arrow Glacier: 13773000, Gray Glacier: 15050000, Terminal Total Difficulty: 58750000000000000000000, Merge Netsplit: <nil>, Shanghai: 1681338455, Cancun: <nil>, Prague: <nil>, Engine: ethash}" genesis=0xd4e56740f876aef8c010b86a40d5f56745a118d0906a34e69aec8c0db1cb8fa3
Initialising Ethereum protocol network=42
Thats from erigon 2.45.3
Initialised chain configuration config="{ChainID: 42, Homestead: 0, DAO: <nil>, Tangerine Whistle: 0, Spurious Dragon: 0, Byzantium: 0, Constantinople: 0, Petersburg: 0, Istanbul: 0, Muir Glacier: <nil>, Berlin: 0, London: 0, Arrow Glacier: <nil>, Gray Glacier: <nil>, Terminal Total Difficulty: 0, Merge Netsplit: <nil>, Shanghai: 1687969198, Cancun: <nil>, Prague: <nil>, Engine: unknown}" genesis=0x5df88817dfb9b00d8ef142370671e8a9bc00c548ab78fbaf205df53db2b24a26
Initialising Ethereum protocol network=42```
Regarding the chain ID, it might be that the client has to be re-initialized using thelukso init
command.
Could you try updating to Erigon 2.55.0 using lukso install
instead of lukso update
please? It has some more checks and might catch up with the right LUKSO configuration.
Like stated in my opening post I used lukso init
Where gets the chain ID set? In the erigon.toml
only? There it was set to 42 when I used 2.55.1.
And what is the difference between network
and chainID
? As it seems network ID
is 42
(correct) but ChainID
is 1
(not 42
)
@Wolmin @mxmar
Could this have something to do with our network-config file? Maybe this can be adjusted on Release 0.15
?
Internal ticket: https://app.clickup.com/t/2645698/DEV-9313
Hey @xtc0r, sadly we are unable to reproduce this issue. Could you also share the logs from your lukso start
command? The invalid chain ID may be a cause of some kind of error present during erigon init
command that is run when lukso start
is active, in order to correctly prepare the data directory - if you are going to do so, please try with data directory being reset - so we get logs different that "database already present - continuing"
I gave it a new try today.
Updated Lukso CLI from 0.8.0 to 0.15.0
Run lukso update
to download Erigon v2.55.0 and LH v4.5.0
Run lukso start --validator --transaction-fee-recipient "0x1337" --checkpoint-sync
Check log via lukso logs execution
and get the following error:
[INFO] [12-19|12:27:19.871] logging to file system log dir=mainnet-data/execution/logs file prefix=erigon log level=info json=false
[INFO] [12-19|12:27:19.871] Enabling metrics export to prometheus path=http://127.0.0.1:6060/debug/metrics/prometheus
[INFO] [12-19|12:27:19.871] Build info git_branch= git_tag= git_commit=
[INFO] [12-19|12:27:19.873] Maximum peer count ETH=100 total=100
[INFO] [12-19|12:27:19.873] starting HTTP APIs APIs=erigon,engine
[INFO] [12-19|12:27:19.874] torrent verbosity level=WRN
[INFO] [12-19|12:27:21.984] Set global gas cap cap=50000000
[INFO] [12-19|12:27:22.120] [Downloader] Runnning with ipv6-enabled=true ipv4-enabled=true download.rate=16mb upload.rate=4mb
[INFO] [12-19|12:27:22.121] Opening Database label=chaindata path=/home/basti/myLUKSOnode/mainnet-data/execution/chaindata
mdbx_setup_dxb:15897 could not apply preconfigured db-geometry: err -30417
[EROR] [12-19|12:27:22.125] Erigon startup err="mdbx_env_open: MDBX_TOO_LARGE: Database is too large for current system, e.g. could NOT be mapped into RAM, label: chaindata, trace: [kv_mdbx.go:295 node.go:365 node.go:368 backend.go:239 node.go:124 main.go:65 make_app.go:52 command.go:274 app.go:332 app.go:309 main.go:34 proc.go:250 asm_arm64.s:1172]"
mdbx_env_open: MDBX_TOO_LARGE: Database is too large for current system, e.g. could NOT be mapped into RAM, label: chaindata, trace: [kv_mdbx.go:295 node.go:365 node.go:368 backend.go:239 node.go:124 main.go:65 make_app.go:52 command.go:274 app.go:332 app.go:309 main.go:34 proc.go:250 asm_arm64.s:1172]
Fixed the error by adding "db.size.limit"="8TB"
to erigon.toml
. I told @fhildeb in discord already about this breaking change. See here: erigon 2.55.0 release notes
Restarted erigon without any issues.
Manually downloaded erigon 2.55.1
and repleaced the bin in /usr/local/bin
because this ticket was opened when I used erigon2.55.1
as lukso update
did download this version at this point in time. Fixed now with lukso cli 0.15.0
Also erigon 2.55.1
starts fine. See log below. ChainID
and networkID
are both 42
[INFO] [12-19|12:46:51.818] [db] chaindata sizeLimit=8TB pageSize=4096
[INFO] [12-19|12:46:51.823] Initialised chain configuration config="{ChainID: 42, Homestead: 0, DAO: <nil>, Tangerine Whistle: 0, Spurious Dragon: 0, Byzantium: 0, Constantinople: 0, Petersburg: 0, Istanbul: 0, Muir Glacier: <nil>, Berlin: 0, London: 0, Arrow Glacier: <nil>, Gray Glacier: <nil>, Terminal Total Difficulty: 0, Merge Netsplit: <nil>, Shanghai: 1687969198, Cancun: <nil>, Prague: <nil>, Engine: unknown}" genesis=0x5df88817dfb9b00d8ef142370671e8a9bc00c548ab78fbaf205df53db2b24a26
[INFO] [12-19|12:46:51.831] Initialising Ethereum protocol network=42
[INFO] [12-19|12:46:51.831] Disk storage enabled for ethash DAGs dir=/home/basti/myLUKSOnode/mainnet-data/execution/ethash-dags count=2
[INFO] [12-19|12:46:52.643] Starting private RPC server on=127.0.0.1:9098
[INFO] [12-19|12:46:52.643] new subscription to logs established
[INFO] [12-19|12:46:52.643] rpc filters: subscribing to Erigon events
[INFO] [12-19|12:46:52.644] New txs subscriber joined
[INFO] [12-19|12:46:52.644] new subscription to newHeaders established
[INFO] [12-19|12:46:52.646] JsonRpc endpoint opened ws=true ws.compression=true grpc=false http.url=127.0.0.1:8545
[INFO] [12-19|12:46:52.647] Reading JWT secret path=./configs/shared/secrets/jwt.hex
[INFO] [12-19|12:46:52.647] HTTP endpoint opened for Engine API url=127.0.0.1:8551 ws=true ws.compression=true
[WARN] [12-19|12:46:52.649] NAT ExternalIP resolution has failed, try to pass a different --nat option err="no UPnP or NAT-PMP router discovered"
[WARN] [12-19|12:46:52.652] NAT ExternalIP resolution has failed, try to pass a different --nat option err="no UPnP or NAT-PMP router discovered"
[INFO] [12-19|12:46:52.652] Started P2P networking version=68 self=enode://cef92b00b7eafb8d6f45bc657b09e259c1eb5137c803ed43486acbcb5cd35d35103871960d3ba84c62d882dc3870fea5ab27bc668ae04ae1c2eacf73111247bd@127.0.0.1:30313 name=erigon/v2.55.1/linux-arm64/go1.20.7
[INFO] [12-19|12:46:52.654] [txpool] Started
[INFO] [12-19|12:46:52.658] Started P2P networking version=67 self=enode://cef92b00b7eafb8d6f45bc657b09e259c1eb5137c803ed43486acbcb5cd35d35103871960d3ba84c62d882dc3870fea5ab27bc668ae04ae1c2eacf73111247bd@127.0.0.1:30314 name=erigon/v2.55.1/linux-arm64/go1.20.7
Conclusion:
Issue can't be reproduced with lukso cli 0.15.0
using erigon 2.55.0
nor 2.55.1
but erigon.toml
needs to be updated to add "db.size.limit"="8TB"
You can close the issue. I don't do it to keep you aware of the needed erigon.toml
change.
Conclusion: Issue can't be reproduced with
lukso cli 0.15.0
using erigon2.55.0
nor2.55.1
buterigon.toml
needs to be updated to add"db.size.limit"="8TB"
You can close the issue. I don't do it to keep you aware of the needederigon.toml
change.
Thanks for pointing this out - we have created a PR in network config repository so we can avoid this being an issue for other people running their node 👍 - https://github.com/lukso-network/network-configs/pull/129 - since this PR merging process is another thing, I'll close this issue
Type
Erigon does not sync with a chain ID error. I had to delete my mainnet db after updating erigon. Now I'm stuck re-syncing. checkpoint flag is set and
lukso init
was done after updating.Description
The Invalid chainID error gets repeated several times then log continues like this:
At this point I'm currently stuck.