AirM

Results 16 comments of AirM

Hi @AskAlexSharov, i tried to debug it as much as possible. erigon version 2022.08.2-alpha-35c4faa1 Tried to compile with 1.18 and 1.19, same error. Machine is AMD Ryzen 9 5950X, 128GB...

... and erigon_2022.99.99-dev-ede0d437 continued the snapshot sync normally. Will see what happens next.

``` DBUG[08-22|16:51:36.050] Sentry peer did Connect peer=b1d16562dac280dacaaf45d54516b85bc6c994252a9825c5cc4e080d3e53446d05f63ba495ea7d44d6c316b54cd92b245c5c328c37da24605c4a93a0d099c400 DBUG[08-22|16:51:58.763] QuerySeeds read nodes from the node DB count=0 INFO[08-22|16:52:25.403] [snapshots] Indexing progress="v1-019500-020000-transactions.seg=50%" alloc=4.5GB sys=8.7GB DBUG[08-22|16:52:25.761] [recsplit] etl: temp files removed total size=1.6GB...

After succesfull snapshot downloading we are looping at the same state. Any advice where to look at? ``` INFO[08-23|10:43:13.096] [txpool] stat block=19999999 pending=0 baseFee=0 queued=11 alloc=3.6GB sys=7.7GB .... INFO[08-23|10:41:31.792] [1/16...

@AskAlexSharov I fixed it simply starting again after crash. So currently we are having the peers, but i don't get why node is not passing step 1? I am running...

No warnings at startup. Everything seems fine. I will wait now, will see what happens next. Maybe it is really needs some time to gather more healthy peers. Thanks @AskAlexSharov...

Within one night no grow of data. Log is full of: ``` INFO[08-24|08:43:23.856] [1/16 Headers] Wrote block headers number=20714824 blk/second=0.350 alloc=2.8GB sys=7.4GB WARN[08-24|08:43:23.856] Added future link hash=0xa2224871e7a75b4f2479f1cb34523fa521403534fefa5f3148c6b1a6a7babc0c height=20714825 timestamp=1661323405 DBUG[08-24|08:43:24.857]...

So finally, for information: With this command i am able to sync: `/usr/local/bin/erigon_2022.99.99-dev-07a9dc9d --chain bsc --networkid 56 --datadir /data/erigon --private.api.addr localhost:9090 --http --ws --http.api eth,engine,erigon,trace --verbosity 4 --downloader.verify --maxpeers 1000...

Hello @AskAlexSharov . So after properly synchronizing for around 10 days our node stuck at block 20753654. Version currently is: 2022.09.1-alpha-4067b7c4 Logs: ``` [DBUG] [09-08|10:00:48.731] [txpool] Commit written_kb=948 in=117.711019ms [INFO]...

State is the same, in addition: ``` integration_2022.09.1-alpha-4067b7c4_localbuild state_stages --unwind=1000 --datadir=/data/erigon/erigon --chain bsc panic: runtime error: index out of range [0] with length 0 goroutine 1 [running]: github.com/ledgerwatch/erigon/eth/ethconsensusconfig.CreateConsensusEngine(0xc00019ab00, {0x1b36000?, 0xc000543e60?},...