Error: not able to find Headers static file for block about reth HOT 3 OPEN

Here are logs for a "WARN Could not find block ...". In that zip file is reth.log and reth.log.starting-reth-version.could-not-find-block which was created with:

kendall@ethel 24-04-09T18:38:53.440Z:~/eth2-data/reth/holesky
$ rg 'Starting reth version|Could not find block' reth.log > reth.log.starting-reth-version.could-not-find-block
kendall@ethel 24-04-09T18:39:20.716Z:~/eth2-data/reth/holesky

When you look at reth.log.starting-reth-version.could-not-find-block the file has 3350 "Starting reth" from "2024-04-08T17:26:10.127770Z" .. "2024-04-09T00:42:05.917330Z". After "2024-04-09T00:42:05.917330Z" I stopped reth when I discovered that my node was rebooting because of the "Failed to insert block" issue that's being tracked in issue 7430. Eventually I dropped the merkle stage and restarted reth at "2024-04-09T03:47:22.649347Z".

Then today I thought I'd add a panic when an InsertBlockError occurs, I did that and accidentally started reth.service which has unmodified version "0.2.0-beta.5 (55f75cdcc)". I stopped it and then started my modified version "0.2.0-beta.5-dev (cd1c2bf)" and then we see the "Could not find block".

So I'm guessing the problem related to this issue occurred some short time before "2024-04-09T17:21:33.262346Z" (i.e. when I stopped reth.service) and "2024-04-09T17:24:14.711716Z " when the "Could not find block" happened.

2024-04-08T17:26:10.127770Z  INFO reth::cli: Starting reth version="0.2.0-beta.5 (54f75cdcc)"
...
2024-04-09T00:42:05.917330Z  INFO reth::cli: Starting reth version="0.2.0-beta.5 (54f75cdcc)"
2024-04-09T03:47:22.649347Z  INFO reth::cli: Starting reth version="0.2.0-beta.5 (54f75cdcc)"
2024-04-09T17:21:33.262346Z  INFO reth::cli: Starting reth version="0.2.0-beta.5 (54f75cdcc)"
2024-04-09T17:24:14.670824Z  INFO reth::cli: Starting reth version="0.2.0-beta.5-dev (cd1c2bf99)"
2024-04-09T17:24:14.711716Z  WARN provider::static_file: Could not find block or tx number on a range request segment=Headers number=1311784

Hopefully these logs and maybe my observations are helpful.

from reth.

Here are logs for a "WARN Could not find block ...". In that zip file is reth.log and reth.log.starting-reth-version.could-not-find-block which was created with:

kendall@ethel 24-04-09T18:38:53.440Z:~/eth2-data/reth/holesky
$ rg 'Starting reth version|Could not find block' reth.log > reth.log.starting-reth-version.could-not-find-block
kendall@ethel 24-04-09T18:39:20.716Z:~/eth2-data/reth/holesky

When you look at reth.log.starting-reth-version.could-not-find-block the file has 3350 "Starting reth" from "2024-04-08T17:26:10.127770Z" .. "2024-04-09T00:42:05.917330Z". After "2024-04-09T00:42:05.917330Z" I stopped reth when I discovered that my node was rebooting because of the "Failed to insert block" issue that's being tracked in issue 7430. Eventually I dropped the merkle stage and restarted reth at "2024-04-09T03:47:22.649347Z".

Then today I thought I'd add a panic when an InsertBlockError occurs, I did that and accidentally started reth.service which has unmodified version "0.2.0-beta.5 (55f75cdcc)". I stopped it and then started my modified version "0.2.0-beta.5-dev (cd1c2bf)" and then we see the "Could not find block".

So I'm guessing the problem related to this issue occurred some short time before "2024-04-09T17:21:33.262346Z" (i.e. when I stopped reth.service) and "2024-04-09T17:24:14.711716Z " when the "Could not find block" happened.

2024-04-08T17:26:10.127770Z  INFO reth::cli: Starting reth version="0.2.0-beta.5 (54f75cdcc)"
...
2024-04-09T00:42:05.917330Z  INFO reth::cli: Starting reth version="0.2.0-beta.5 (54f75cdcc)"
2024-04-09T03:47:22.649347Z  INFO reth::cli: Starting reth version="0.2.0-beta.5 (54f75cdcc)"
2024-04-09T17:21:33.262346Z  INFO reth::cli: Starting reth version="0.2.0-beta.5 (54f75cdcc)"
2024-04-09T17:24:14.670824Z  INFO reth::cli: Starting reth version="0.2.0-beta.5-dev (cd1c2bf99)"
2024-04-09T17:24:14.711716Z  WARN provider::static_file: Could not find block or tx number on a range request segment=Headers number=1311784

Hopefully these logs and maybe my observations are helpful.

looking through the logs it seems like yours presented differently than mine, and considerably sooner, then again it seems you are also using holesky?

from reth.

looking through the logs it seems like yours presented differently than mine, and considerably sooner, then again it seems you are also using holesky?

Yes I'm on holesky

from reth.