Closed scholtz closed 1 year ago
did your indexer instance exit with an error code? the logs seems to show it recovered from the error after retry and continue to import rounds after 29015075. ... BlkSeed\n","level":"error","msg":"block 29015075 import failed","time":"2023-04-09T08:53:14Z"} {"level":"info","msg":"adding block 29015075","time":"2023-04-09T08:53:15Z"} {"level":"info","msg":"round r=29015075 (133 txn) imported in 32.573721ms","time":"2023-04-09T08:53:15Z"} {"level":"info","msg":"adding block 29015076","time":"2023-04-09T08:53:18Z"} {"level":"info","msg":"round r=29015076 (18 txn) imported in 11.557642ms","time":"2023-04-09T08:53:18Z"} {"level":"info","msg":"adding block 29015077","time":"2023-04-09T08:53:21Z"}
this error should be fixed in the next go-algorand release.
Subject of the issue
I am running testnet indexer v 2.15.3 for testnet and noticed these errors in the logs
Your environment
algod -v
goal node status
Operating System details
K8S setup
Steps to reproduce
Run the indexer
Expected behaviour
No error logs
Actual behaviour