erigon
erigon copied to clipboard
BSC - No block headers to write in this log period block number
System information
Erigon version: erigon version 2.27.0-stable-6d8b304e
OS & Version: Linux
Commit hash : 6d8b304
Expected behaviour
Syncing to the latest block
Actual behaviour
Error: No block headers to write in this log period
bsc-node-000 | [INFO] [10-11|15:02:13.458] [p2p] GoodPeers eth66=86
bsc-node-000 | [INFO] [10-11|15:02:13.470] [txpool] stat block=0 pending=1 baseFee=0 queued=16 alloc=3.8GB sys=65.4GB
bsc-node-000 | [INFO] [10-11|15:02:31.125] [2/16 Headers] No block headers to write in this log period block number=20304127 blk/second=0.000
bsc-node-000 | [INFO] [10-11|15:02:51.125] [2/16 Headers] No block headers to write in this log period block number=20304127 blk/second=0.000
bsc-node-000 | [INFO] [10-11|15:03:11.126] [2/16 Headers] No block headers to write in this log period block number=20304127 blk/second=0.000
bsc-node-000 | [INFO] [10-11|15:03:13.468] [txpool] stat block=0 pending=1 baseFee=0 queued=16 alloc=3.3GB sys=65.4GB
bsc-node-000 | [INFO] [10-11|15:03:31.125] [2/16 Headers] No block headers to write in this log period block number=20304127 blk/second=0.000
bsc-node-000 | [INFO] [10-11|15:03:51.126] [2/16 Headers] No block headers to write in this log period block number=20304127 blk/second=0.000
Steps to reproduce the behaviour
command:
- erigon
- --datadir=/root/.local/share/erigon
- --chain=bsc
- --port=29505
- --private.api.addr=0.0.0.0:9090
- --http=false
- --db.pagesize=16kb
- --prune=hrtc
- --torrent.port=29506
- --torrent.download.rate=1000mb
- --torrent.download.slots=6
- --downloader.verify
- --batchSize=512M
- --etl.bufferSize=512M
- --healthcheck
- --verbosity=3
Same issue here, sync stopped at block 22107424
additional log:
[WARN] [10-12|11:18:19.176] [7/16 Execution] Execution failed block=22107425 hash=0x71044292c200a2138a4b1cfe258bbeb3998e1a6cc1a06f0a380522c4527702c2 err="expected system tx (hash 0xf1753cfe253f554860cac1c86ef60fcb5bf094116afd0ddeff8548e54b30d29f, nonce 831138, to 0x0000000000000000000000000000000000001000, value 0x161441e802c87a4, gas 9223372036854775807, gasPrice 0x0, data f340fa010000000000000000000000009f8ccdafcc39f3c7d6ebf637c9151673cbc36b88), actual tx (hash 0xe053c8c705c470a3032854fa2d36b41ca638d7972d48f9c9ec344bbc8a05bca8, nonce 831138, to 0x0000000000000000000000000000000000001000, value 0x16144381caf53a4, gas 9223372036854775807, gasPrice 0x0, data f340fa010000000000000000000000009f8ccdafcc39f3c7d6ebf637c9151673cbc36b88)"
[INFO] [10-12|11:18:19.177] UnwindTo block=22107424 bad_block_hash=0x71044292c200a2138a4b1cfe258bbeb3998e1a6cc1a06f0a380522c4527702c2
Erigon version: v2.28.0
@AdminAnticaptcha please upgrade to v2.28.0 this is the BSC hardfork Moran
@AdminAnticaptcha please upgrade to v2.28.0 this is the BSC hardfork Moran
I'm on v.2.28.0, same as @nikolinsko
Update: one of 2 nodes was eventually able to process this block. I restarted the second one, going to update after it downloads torrent data.
@AdminAnticaptcha did you do something in particular?
@mikolajsobolewski
i'm at the following commit / tag:
git_branch=heads/v2.28.0 git_tag=v2.28.0 git_commit=355837aee5ea2374bf420eff6e93360deb83d3f7
after:
[WARN] [10-12|12:17:08.820] [7/16 Execution] Execution failed block=22107425 hash=0x71044292c200a2138a4b1cfe258bbeb3998e1a6cc1a06f0a380522c4527702c2 err="expected system tx (hash 0xf1753cfe253f554860cac1c86ef60fcb5bf094116afd0ddeff8548e54b30d29f, nonce 831138, to 0x0000000000000000000000000000000000001000, value 0x161441e802c87a4, gas 9223372036854775807, gasPrice 0x0, data f340fa010000000000000000000000009f8ccdafcc39f3c7d6ebf637c9151673cbc36b88), actual tx (hash 0xe053c8c705c470a3032854fa2d36b41ca638d7972d48f9c9ec344bbc8a05bca8, nonce 831138, to 0x0000000000000000000000000000000000001000, value 0x16144381caf53a4, gas 9223372036854775807, gasPrice 0x0, data f340fa010000000000000000000000009f8ccdafcc39f3c7d6ebf637c9151673cbc36b88)"
[INFO] [10-12|12:17:08.820] UnwindTo block=22107424 bad_block_hash=0x71044292c200a2138a4b1cfe258bbeb3998e1a6cc1a06f0a380522c4527702c2
[INFO] [10-12|12:17:08.820] [7/16 Execution] Completed on block=22107424
[INFO] [10-12|12:17:12.526] [2/16 Headers] Waiting for headers... from=22107424
the following is looped
[INFO] [10-12|12:23:12.527] [2/16 Headers] No block headers to write in this log period block number=22107424 blk/second=0.000
[INFO] [10-12|12:23:12.527] Req/resp stats req=5 reqMin=22107528 reqMax=22108296 skel=15 skelMin=22108960 skelMax=22403680 resp=100 respMin=22107721 respMax=22109074 dups=30
[INFO] [10-12|12:23:12.527] [Downloader] Queue sizes anchors=1 links=1354 persisted=64055
[INFO] [10-12|12:23:12.527] {22107721-22109074 links=1354 (22107721-22109074)} => 14663dfdaf1c69c514afeecc726a10af8e9be6766bfa1b1f9248285873388ec9, anchorQueue.idx=0, next retry in 1.691698652s
integration shows:
Snapshots 22107422 0
Headers 22107424 0
BlockHashes 22107424 0
Bodies 22107424 0
Senders 22107424 0
Execution 22107424 22107422
Translation 0 0
HashState 22107422 0
IntermediateHashes 22107422 22107422
AccountHistoryIndex 22107422 22107422
StorageHistoryIndex 22107422 22107422
LogIndex 22107422 22107422
CallTraces 22107422 22107422
TxLookup 22107422 22102422
Finish 22107422 0
prune distance: --prune.h.older=5000 --prune.r.older=5000 --prune.t.older=5000 --prune.c.older=5000
sequence: EthTx=3541637689, NonCanonicalTx=230018
first header in db: 1
first body in db: 1
snapsthos: blocks=0, segments=0, indices=0
The same issue, 2.28.0 update doesn't help
@nikolinsko I just installed same version to 2 nodes. One had synced, the other after several attempts to download snapshots still not able to pass this block.
@AdminAnticaptcha did you modify anything with your synced node?
@tinoh99 no I didn't.
Stuck at same issue, was earlier working with 2.27.0 and before 5hrs got this issue. Upgraded erigon to 2.28.0 and still stuck at same place
erigon-erigon-1 | [INFO] [10-12|14:41:38.054] [2/16 Headers] No block headers to write in this log period block number=22107424 blk/second=0.000
erigon-erigon-1 | [INFO] [10-12|14:41:38.054] Req/resp stats req=31 reqMin=22107423 reqMax=22112585 skel=14 skelMin=22108960 skelMax=22403680 resp=77 respMin=22108000 respMax=22114132 dups=85
erigon-erigon-1 | [INFO] [10-12|14:41:38.054] [Downloader] Queue sizes anchors=1 links=6134 persisted=59168
erigon-erigon-1 | [INFO] [10-12|14:41:38.054] {22108000-22114132 links=6134 (22108000-22114130-22114132)} => 3cc9c62721e50b37936edbcc888fc5171c056fc449eaa02666adff10d5cc1d81, anchorQueue.idx=0, next retry in 38.281912ms
I just ran ./build/bin/integration stage_exec --datadir <your_datadir> --chain bsc --unwind 10
and start erigon and seems to be working as expected
@poloplayingsolo @nikolinsko @AdminAnticaptcha @breezytm can u try this once and see if this is working for u.
I just ran
./build/bin/integration stage_exec --datadir <your_datadir> --chain bsc --unwind 10
and start erigon and seems to be working as expected@poloplayingsolo @nikolinsko @AdminAnticaptcha @breezytm can u try this once and see if this is working for u.
In my case I am not sure if there is any data to unwind because this is a new deployment. It never synced. It does that right after finish the snapshot download.
I just ran
./build/bin/integration stage_exec --datadir <your_datadir> --chain bsc --unwind 10
and start erigon and seems to be working as expected@poloplayingsolo @nikolinsko @AdminAnticaptcha @breezytm can u try this once and see if this is working for u.
yup, seems like that fixes the issue.
Thanks for the tip.
@breezytm still give a try. As i was stuck at same issue. U dnt need full sync to get complete to unwind.
Did anyone find a workaround for this? Unwinding doesn't help.
I synced multiple nodes from scratch and now it's stuck at No block headers to write in this log period block number=xxxxx
. On every restart, it adds a few blocks and then gets stuck again.
I think the best way now to sync for those who still have issues with unwind is to use a snapshot like this one: https://github.com/allada/bsc-archive-snapshot
Adding the --snap.stop
flag and restarting erigon fixed this for me — multiple nodes.
@a26nine I have tried your flag but it's still stucked, did you input any additional flag?
Perhaps boot nodes need to be updated for BSC, can someone check
@a26nine I have tried your flag but it's still stucked, did you input any additional flag?
I did add --downloader.verify
earlier for another issue — don't know whether that would help.
@breezytm still give a try. As i was stuck at same issue. U dnt need full sync to get complete to unwind.
This is what I am getting
bsc-node-000 | [INFO] [10-13|13:08:38.253] [Downloader] Queue sizes anchors=1 links=801 persisted=65536
bsc-node-000 | [INFO] [10-13|13:08:38.253] {22139860-22140660 links=801 (22139860-22140660)} => 50669e6f4e517c35cedba5a40781c83c5286da9bc21cfc08b9ebc62d5d8824ce, anchorQueue.idx=0, next retry in 3.591337491s
bsc-node-000 | [INFO] [10-13|13:08:58.252] [2/16 Headers] No block headers to write in this log period block number=21499999 blk/second=0.000
bsc-node-000 | [INFO] [10-13|13:08:58.252] Req/resp stats req=5 reqMin=22139283 reqMax=22139859 skel=13 skelMin=21501535 skelMax=21796255 resp=32 respMin=22140666 respMax=22140667 dups=7
bsc-node-000 | [INFO] [10-13|13:08:58.252] [Downloader] Queue sizes anchors=1 links=1192 persisted=65536
bsc-node-000 | [INFO] [10-13|13:08:58.252] {22139476-22140667 links=1192 (22139476-22140667)} => b9813bf7c311b2bff7a5945d221381ed36d2bb308d33a71d90eda071242068a5, anchorQueue.idx=0, next retry in 1.305319751s
bsc-node-000 | [INFO] [10-13|13:09:18.252] [2/16 Headers] No block headers to write in this log period block number=21499999 blk/second=0.000
bsc-node-000 | [INFO] [10-13|13:09:18.252] Req/resp stats req=4 reqMin=22139283 reqMax=22139475 skel=17 skelMin=21501535 skelMax=21796255 resp=43 respMin=22140638 respMax=22140674 dups=14
bsc-node-000 | [INFO] [10-13|13:09:18.252] [Downloader] Queue sizes anchors=1 links=1199 persisted=65536
bsc-node-000 | [INFO] [10-13|13:09:18.253] {22139476-22140674 links=1199 (22139476-22140674)} => b9813bf7c311b2bff7a5945d221381ed36d2bb308d33a71d90eda071242068a5, anchorQueue.idx=0, next retry in 3.133441457s
bsc-node-000 | [INFO] [10-13|13:09:28.888] [txpool] stat block=21499999 pending=0 baseFee=0 queued=91 alloc=2.6GB sys=5.1GB
bsc-node-000 | [INFO] [10-13|13:09:38.252] [2/16 Headers] No block headers to write in this log period block number=21499999 blk/second=0.000
bsc-node-000 | [INFO] [10-13|13:09:38.252] Req/resp stats req=6 reqMin=22138707 reqMax=22139475 skel=15 skelMin=21501535 skelMax=21796255 resp=46 respMin=22140671 respMax=22140681 dups=15
bsc-node-000 | [INFO] [10-13|13:09:38.252] [Downloader] Queue sizes anchors=1 links=1782 persisted=65536
bsc-node-000 | [INFO] [10-13|13:09:38.252] {22138900-22140681 links=1782 (22138900-22140681)} => 56042078e493a16e1caa5f922eea21a9777832bdfa601c512a9a5c03a289ed70, anchorQueue.idx=0, next retry in -3.992642ms
Just to chime in that I have the exact same issues as above on v2.28.0, have tried all workarounds in the thread (downloader.verify
, snap.stop
, unwind
etc) without success
I had this same issue with a new node I was spinning up from snapshots. I tried all sorts of things and was finally able to resolve it by deleting all of the snapshot files and restarting erigon then letting them re-download and index etc. It took about 24 hours but it solved the issue and my node is now functioning normally.
As @PolarSyncZ said, I'd been working with them to help get their node online. I'll be updating the s3 snapshot folder in https://github.com/allada/bsc-archive-snapshot. I'll post back here with the s3 command you'all can use to download just the snapshots tomorrow-ish or you can delete the snapshots
folder and torrent the files yourself.
For those that want to test if your snapshot folder will fix the issue, here's what should
fix the issue:
-
make integration
-
./build/bin/integration stage_exec --datadir <your_datadir> --chain bsc --unwind 1000 # You might be able to get away with less blocks
-
rm -rf <your_datadir>/snapshots/*
-
cd <your_datadir>/snapshots && aws s3 --request-payer=requester sync s3://public-blockchain-snapshots/bsc/erigon-snapshots-folder-latest/ ./
Note: You will need an AWS account configured on the computer it is running on, as your aws account will be billed for the download costs, which is about $50USD in data xfer costs unless you are running the instance in AWS's us-west-2
data center, which it'll be about $0.10USD.
For those that want to test if your snapshot folder will fix the issue, here's what
should
fix the issue:
make integration
./build/bin/integration stage_exec --datadir <your_datadir> --chain bsc --unwind 1000 # You might be able to get away with less blocks
rm -rf <your_datadir>/snapshots/*
cd <your_datadir>/snapshots && aws s3 --request-payer=requester sync s3://public-blockchain-snapshots/bsc/erigon-snapshots-folder-latest/ ./
Note: You will need an AWS account configured on the computer it is running on, as your aws account will be billed for the download costs, which is about $50USD in data xfer costs unless you are running the instance in AWS's
us-west-2
data center, which it'll be about $0.10USD.
Hi @allada, thanks for you snapshots file, but maybe s3 sync need "ListObjectsV2" permission When I use "aws s3 --request-payer=requester sync" return:
An error occurred (AccessDenied) when calling the ListObjectsV2 operation: Access Denied
Hi @allada, thanks for you snapshots file, but maybe s3 sync need "ListObjectsV2" permission
You need to make sure the account you are using has the ability to charge your account for S3 requests. These permissions are set in your account, and IIRC you can just allow s3:ListBucket
and other related permissions to resource: arn:aws:s3:::public-blockchain-snapshots
and I think it'll work.
Hi @allada, thanks for you snapshots file, but maybe s3 sync need "ListObjectsV2" permission
You need to make sure the account you are using has the ability to charge your account for S3 requests. These permissions are set in your account, and IIRC you can just allow
s3:ListBucket
and other related permissions to resource:arn:aws:s3:::public-blockchain-snapshots
and I think it'll work.
@allada Thanks, it's my problem. It's syncing now.
fyi: there is also https://github.com/BNB48Club/bsc-snapshots. Seems to be from a validator, so as close as trustworthy as you can get on bsc :D
I have the same issue Erigon version is 2.28.1 Last log:
erigon_1 | [INFO] [10-18|07:24:55.556] [txpool] stat block=19999999 pending=1 baseFee=0 queued=146 alloc=4.2GB sys=7.0GB
erigon_1 | [INFO] [10-18|07:25:04.634] [2/16 Headers] No block headers to write in this log period block number=20348671 blk/second=0.000
erigon_1 | [INFO] [10-18|07:25:24.635] [2/16 Headers] No block headers to write in this log period block number=20348671 blk/second=0.000
erigon_1 | [INFO] [10-18|07:25:44.635] [2/16 Headers] No block headers to write in this log period block number=20348671 blk/second=0.000
erigon_1 | [INFO] [10-18|07:25:55.557] [txpool] stat block=19999999 pending=1 baseFee=0 queued=146 alloc=4.5GB sys=7.0GB
erigon_1 | [INFO] [10-18|07:26:04.634] [2/16 Headers] No block headers to write in this log period block number=20348671 blk/second=0.000
erigon_1 | [INFO] [10-18|07:26:24.634] [2/16 Headers] No block headers to write in this log period block number=20348671 blk/second=0.000
erigon_1 | [INFO] [10-18|07:26:44.634] [2/16 Headers] No block headers to write in this log period block number=20348671 blk/second=0.000
erigon_1 | [INFO] [10-18|07:26:55.535] [p2p] GoodPeers eth66=20
erigon_1 | [INFO] [10-18|07:26:55.557] [txpool] stat block=19999999 pending=1 baseFee=0 queued=146 alloc=4.2GB sys=7.0GB
erigon_1 | [INFO] [10-18|07:27:04.635] [2/16 Headers] No block headers to write in this log period block number=20348671 blk/second=0.000
erigon_1 | [INFO] [10-18|07:27:24.635] [2/16 Headers] No block headers to write in this log period block number=20348671 blk/second=0.000
erigon_1 | [INFO] [10-18|07:27:44.634] [2/16 Headers] No block headers to write in this log period block number=20348671 blk/second=0.000
erigon_1 | [INFO] [10-18|07:27:55.556] [txpool] stat block=19999999 pending=1 baseFee=0 queued=146 alloc=4.3GB sys=7.0GB
erigon_1 | [INFO] [10-18|07:28:04.634] [2/16 Headers] No block headers to write in this log period block number=20348671 blk/second=0.000
erigon_1 | [INFO] [10-18|07:28:24.634] [2/16 Headers] No block headers to write in this log period block number=20348671 blk/second=0.000
erigon_1 | [INFO] [10-18|07:28:44.634] [2/16 Headers] No block headers to write in this log period block number=20348671 blk/second=0.000
erigon_1 | [INFO] [10-18|07:28:55.535] [p2p] GoodPeers eth66=20
erigon_1 | [INFO] [10-18|07:28:55.555] [txpool] stat block=19999999 pending=1 baseFee=0 queued=146 alloc=4.2GB sys=7.0GB
erigon_1 | [INFO] [10-18|07:29:04.634] [2/16 Headers] No block headers to write in this log period block number=20348671 blk/second=0.000
erigon_1 | [INFO] [10-18|07:29:24.634] [2/16 Headers] No block headers to write in this log period block number=20348671 blk/second=0.000
erigon_1 | [INFO] [10-18|07:29:44.634] [2/16 Headers] No block headers to write in this log period block number=20348671 blk/second=0.000
erigon_1 | [INFO] [10-18|07:29:55.556] [txpool] stat block=19999999 pending=1 baseFee=0 queued=146 alloc=4.3GB sys=7.0GB
erigon_1 | [INFO] [10-18|07:30:04.634] [2/16 Headers] No block headers to write in this log period block number=20348671 blk/second=0.000
erigon_1 | [INFO] [10-18|07:30:24.634] [2/16 Headers] No block headers to write in this log period block number=20348671 blk/second=0.000
erigon_1 | [INFO] [10-18|07:30:44.635] [2/16 Headers] No block headers to write in this log period block number=20348671 blk/second=0.000
erigon_1 | [INFO] [10-18|07:30:55.535] [p2p] GoodPeers eth66=20
erigon_1 | [INFO] [10-18|07:30:55.555] [txpool] stat block=19999999 pending=1 baseFee=0 queued=146 alloc=4.2GB sys=7.0GB
erigon_1 | [INFO] [10-18|07:31:04.634] [2/16 Headers] No block headers to write in this log period block number=20348671 blk/second=0.000
Restart doesn't help
@1scrooge, read above for fix. There is unlikely to be any "fix" by erigon since users can fix it themselves.
Same version , same problem for me. Tried to unwind stages and re-download snapshots. Stuck at the same message but different block.
I have the same issue Erigon version is 2.28.1 Last log:
erigon_1 | [INFO] [10-18|07:24:55.556] [txpool] stat block=19999999 pending=1 baseFee=0 queued=146 alloc=4.2GB sys=7.0GB erigon_1 | [INFO] [10-18|07:25:04.634] [2/16 Headers] No block headers to write in this log period block number=20348671 blk/second=0.000 erigon_1 | [INFO] [10-18|07:25:24.635] [2/16 Headers] No block headers to write in this log period block number=20348671 blk/second=0.000 erigon_1 | [INFO] [10-18|07:25:44.635] [2/16 Headers] No block headers to write in this log period block number=20348671 blk/second=0.000 erigon_1 | [INFO] [10-18|07:25:55.557] [txpool] stat block=19999999 pending=1 baseFee=0 queued=146 alloc=4.5GB sys=7.0GB erigon_1 | [INFO] [10-18|07:26:04.634] [2/16 Headers] No block headers to write in this log period block number=20348671 blk/second=0.000 erigon_1 | [INFO] [10-18|07:26:24.634] [2/16 Headers] No block headers to write in this log period block number=20348671 blk/second=0.000 erigon_1 | [INFO] [10-18|07:26:44.634] [2/16 Headers] No block headers to write in this log period block number=20348671 blk/second=0.000 erigon_1 | [INFO] [10-18|07:26:55.535] [p2p] GoodPeers eth66=20 erigon_1 | [INFO] [10-18|07:26:55.557] [txpool] stat block=19999999 pending=1 baseFee=0 queued=146 alloc=4.2GB sys=7.0GB erigon_1 | [INFO] [10-18|07:27:04.635] [2/16 Headers] No block headers to write in this log period block number=20348671 blk/second=0.000 erigon_1 | [INFO] [10-18|07:27:24.635] [2/16 Headers] No block headers to write in this log period block number=20348671 blk/second=0.000 erigon_1 | [INFO] [10-18|07:27:44.634] [2/16 Headers] No block headers to write in this log period block number=20348671 blk/second=0.000 erigon_1 | [INFO] [10-18|07:27:55.556] [txpool] stat block=19999999 pending=1 baseFee=0 queued=146 alloc=4.3GB sys=7.0GB erigon_1 | [INFO] [10-18|07:28:04.634] [2/16 Headers] No block headers to write in this log period block number=20348671 blk/second=0.000 erigon_1 | [INFO] [10-18|07:28:24.634] [2/16 Headers] No block headers to write in this log period block number=20348671 blk/second=0.000 erigon_1 | [INFO] [10-18|07:28:44.634] [2/16 Headers] No block headers to write in this log period block number=20348671 blk/second=0.000 erigon_1 | [INFO] [10-18|07:28:55.535] [p2p] GoodPeers eth66=20 erigon_1 | [INFO] [10-18|07:28:55.555] [txpool] stat block=19999999 pending=1 baseFee=0 queued=146 alloc=4.2GB sys=7.0GB erigon_1 | [INFO] [10-18|07:29:04.634] [2/16 Headers] No block headers to write in this log period block number=20348671 blk/second=0.000 erigon_1 | [INFO] [10-18|07:29:24.634] [2/16 Headers] No block headers to write in this log period block number=20348671 blk/second=0.000 erigon_1 | [INFO] [10-18|07:29:44.634] [2/16 Headers] No block headers to write in this log period block number=20348671 blk/second=0.000 erigon_1 | [INFO] [10-18|07:29:55.556] [txpool] stat block=19999999 pending=1 baseFee=0 queued=146 alloc=4.3GB sys=7.0GB erigon_1 | [INFO] [10-18|07:30:04.634] [2/16 Headers] No block headers to write in this log period block number=20348671 blk/second=0.000 erigon_1 | [INFO] [10-18|07:30:24.634] [2/16 Headers] No block headers to write in this log period block number=20348671 blk/second=0.000 erigon_1 | [INFO] [10-18|07:30:44.635] [2/16 Headers] No block headers to write in this log period block number=20348671 blk/second=0.000 erigon_1 | [INFO] [10-18|07:30:55.535] [p2p] GoodPeers eth66=20 erigon_1 | [INFO] [10-18|07:30:55.555] [txpool] stat block=19999999 pending=1 baseFee=0 queued=146 alloc=4.2GB sys=7.0GB erigon_1 | [INFO] [10-18|07:31:04.634] [2/16 Headers] No block headers to write in this log period block number=20348671 blk/second=0.000
Restart doesn't help
Hi @1scrooge @amurde Double check your firewall config. I fixed this issue by allowing tcp/udp ports of downloader
and sentry
containers.
@nftgeek Can you please clarify? Re-checked again: ports 30303 and 42069 tcp/udp is currently opened.
As i see from documentation, sentry private port is 9091 and it should not be exposed. "...sentry process will run one eth/xx protocol (e.g. eth/66) and will be exposed to the internet on 30303...".
What you mean as downloader port?
Thanks in advance!
@nftgeek Firewall is OK. The bsc testnet node is fully synchronized with the same VM configuration