You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am running a Bor full node and using the --cache.triesinmemory flag to keep the state for 3600 blocks, allowing me to call the debug_traceTransaction RPC beyond the 128-block range. This worked fine in Bor v1.4.1.
However, after upgrading to Bor v1.5.5, now receive the following error when querying beyond 128 blocks:
required historical state unavailable (reexec=128)
Could you please check if there are any changes in Bor v1.5.5 that might be causing this issue?
Below is the Bor startup command I am using. Note that the same command worked correctly on v1.4.1.
Additionally, my config.toml file only contains trusted node settings
System information
Bor client version: v1.5.5
Heimdall client version: 1.2.0
OS & Version: Linux
Environment: Polygon Mainnet
Type of node: bor full
Overview of the problem
I am running a Bor full node and using the
--cache.triesinmemory
flag to keep the state for 3600 blocks, allowing me to call the debug_traceTransaction RPC beyond the 128-block range. This worked fine in Bor v1.4.1.However, after upgrading to Bor v1.5.5, now receive the following error when querying beyond 128 blocks:
Could you please check if there are any changes in Bor v1.5.5 that might be causing this issue?
Below is the Bor startup command I am using. Note that the same command worked correctly on v1.4.1.
Additionally, my
config.toml
file only contains trusted node settingsReproduction Steps
--cache.triesinmemory=3600
flag.debug_traceTransaction
RPC for transactions within the range of 128 to 3600 blocks.required historical state unavailable (reexec=128)
message appears.Let me know if you need any additional details. Thanks!
The text was updated successfully, but these errors were encountered: