trace_block returns "insufficient funds for gas * price + value" error on block 21030627

[quick-pawiromitchel]

System information

Erigon version: erigon/2.60.4/linux-amd64/go1.22.5

OS & Version: Linux

Chain/Network: Mainnet

Steps to reproduce the behaviour

{
  "method": "trace_block",
  "params": [
    "0x140e6e3"
  ],
  "id": 1,
  "jsonrpc": "2.0"
}

Returns

{
  "jsonrpc": "2.0",
  "id": 1,
  "error": {
    "code": -32000,
    "message": "first run for txIndex 85 error: insufficient funds for gas * price + value: address 0x0b92619DdE55C0cbf828d32993a7fB004E00c84B have 1414044108792614043 want 1414044806692614043"
  }
}

Backtrace

Oct 29 13:25:37 erigon[1105]: [WARN] [10-29|13:25:37.367] [rpc] served                             conn=xxxxx:59459 method=trace_block reqid=1 t=34.504079ms err="first run for txIndex 85 error: insufficient funds for gas * price + value: address 0x0b92619DdE55C0cbf828d32993a7fB004E00c84B have 1414044108792614043 want 1414044806692614043"

[yperbasis]

Fixed by PR #12559 and will be released in v2.60.10.

[Tommel71]

@yperbasis There seems to be something wrong, we still get the error on 2.60.10 with the newest docker container and the git_tag seems to be 2.60.9 still

○ → docker run erigontech/erigon:latest
[INFO] [11-06|14:44:41.097] logging to file system                   log dir=/home/erigon/.local/share/erigon/logs file prefix=erigon log level=info json=false
[INFO] [11-06|14:44:41.098] Build info                               git_branch=release/2.60 git_tag=v2.60.9-4-g3afee08bff git_commit=3afee08bfff043a731485e0a92dd8650823d8884
[INFO] [11-06|14:44:41.098] Starting Erigon on Ethereum mainnet...

[yperbasis]

@yperbasis There seems to be something wrong, we still get the error on 2.60.10 with the newest docker container and the git_tag seems to be 2.60.9 still

○ → docker run erigontech/erigon:latest
[INFO] [11-06|14:44:41.097] logging to file system                   log dir=/home/erigon/.local/share/erigon/logs file prefix=erigon log level=info json=false
[INFO] [11-06|14:44:41.098] Build info                               git_branch=release/2.60 git_tag=v2.60.9-4-g3afee08bff git_commit=3afee08bfff043a731485e0a92dd8650823d8884
[INFO] [11-06|14:44:41.098] Starting Erigon on Ethereum mainnet...

@VBulikov @lystopad could you check this please

[lystopad]

Hi, all

"git_tag" in this case is the output of git describe --tags '--match=v*' --dirty see here

This outputs basically means -- the last tag found in git was "v2.60.9" and current git repository state is 4 commits on top of that tag and latest short commit id is "3afee08bff". More details could be found here.

It is done so, because we decided to TAG git repository after release.
Let me know if you would like to discuss/change it.

P.S.
In the following PR #12658 I changed short commit id to be 7 chars which will match short commit IDs in github history (easy to find).

[Tommel71]

@yperbasis @lystopad

It is not just the tag but more importantly that the issue described in this thread persists.

[yperbasis]

@Tommel71 trace_block now works fine for 0x140e6e3 on my v2.60.10 node (albeit I built it locally instead of using the docker image).

[soad003]

@yperbasis for us (same team as @Tommel71), the issue persists after updating to the v2.60.10 docker image.

The curl call returns an error as before. Do you have any advice, is there some cache we need to reset or could it be an issue with the docker image?