Closed
Description
System information
Geth version: 1.15.10
CL client & version: lodestar 1.29.0
OS & Version: linux + docker
Commit hash : N/A
Expected behaviour
Actual behaviour
Steps to reproduce the behaviour
Updated from 1.15.6 to 1.15.10 and ~10 hours later I start getting the following messages.
Backtrace
... (ALL GOOD)
INFO [04-25|22:05:13.265] Imported new potential chain segment number=22,348,907 hash=69b737..5b1489 blocks=1 txs=185 mgas=18.382 elapsed=367.542ms mgasps=50.012 snapdiffs=9.29MiB triediffs=217.65MiB triedirty=69.07MiB
INFO [04-25|22:05:13.410] Chain head was updated number=22,348,907 hash=69b737..5b1489 root=b8d362..6957e9 elapsed=5.92321ms
INFO [04-25|22:05:26.081] Imported new potential chain segment number=22,348,908 hash=397327..a09a93 blocks=1 txs=151 mgas=14.153 elapsed=181.582ms mgasps=77.941 snapdiffs=9.33MiB triediffs=217.38MiB triedirty=69.49MiB
INFO [04-25|22:05:26.223] Chain head was updated number=22,348,908 hash=397327..a09a93 root=a498da..c1489e elapsed=4.772658ms
INFO [04-25|22:05:37.575] Imported new potential chain segment number=22,348,909 hash=fc4957..1b404d blocks=1 txs=210 mgas=24.776 elapsed=686.373ms mgasps=36.097 snapdiffs=9.37MiB triediffs=217.16MiB triedirty=69.96MiB
INFO [04-25|22:05:37.695] Chain head was updated number=22,348,909 hash=fc4957..1b404d root=049a34..c2f6c5 elapsed=7.018634ms
WARN [04-25|22:05:46.016] Served eth_getLogs conn=172.18.0.3:52044 reqid=11052339 duration=1.370535039s err="failed to process log index epoch 270: failed to retrieve log at index 18122937602: failed to retrieve log value pointer of block 22323558 while binary searching log value index 18122937602: failed to retrieve log value pointer of block 22323558: pebble: not found"
WARN [04-25|22:05:48.466] Served eth_getLogs conn=172.18.0.3:52044 reqid=11052341 duration=1.357920462s err="failed to process log index epoch 270: failed to retrieve log at index 18122937602: failed to retrieve log value pointer of block 22323558 while binary searching log value index 18122937602: failed to retrieve log value pointer of block 22323558: pebble: not found"
INFO [04-25|22:05:49.249] Imported new potential chain segment number=22,348,910 hash=01a691..771a1b blocks=1 txs=164 mgas=18.495 elapsed=307.970ms mgasps=60.055 snapdiffs=9.42MiB triediffs=216.75MiB triedirty=70.46MiB
INFO [04-25|22:05:49.363] Chain head was updated number=22,348,910 hash=01a691..771a1b root=fcf438..1acd1c elapsed=5.283277ms
WARN [04-25|22:05:49.447] Blob transaction swapped out by signer from=0x479B7c95b9509E1A834C994fc94e3581aA8A73B9 nonce=861 id=536,870,913
WARN [04-25|22:05:51.028] Served eth_getLogs conn=172.18.0.3:52044 reqid=11052343 duration=1.541003981s err="failed to process log index epoch 270: failed to retrieve log at index 18122937602: failed to retrieve log value pointer of block 22323558 while binary searching log value index 18122937602: failed to retrieve log value pointer of block 22323558: pebble: not found"
WARN [04-25|22:05:53.436] Served eth_getLogs conn=172.18.0.3:52044 reqid=11052345 duration=1.404113283s err="failed to process log index epoch 270: failed to retrieve log at index 18122937602: failed to retrieve log value pointer of block 22323558 while binary searching log value index 18122937602: failed to retrieve log value pointer of block 22323558: pebble: not found"
Looks like a fried DB, but no shutdown has occurred.