I've been regularly seeing SLPDB stall out on testing. I've seen this happen once on mainnet, but it happens consistently on testnet. I'm running it against a BCHN node.
I've captured the output of SLPDB on the last two stalls and uploaded them to pastebin:
It looks me like SLPDB catches up to the current block, then just stops processing blocks. e.g. it doesn't seem to process blocks and then stall for some reason, it just never seems to process blocks after catching up with the current chain tip.
I'm running SLPDB v1 (commit f1f48a3) and synced from genesis. I had hoped that syncing from genesis on the latest version would resolve the issue, but it didn't.
I've been regularly seeing SLPDB stall out on testing. I've seen this happen once on mainnet, but it happens consistently on testnet. I'm running it against a BCHN node.
I've captured the output of SLPDB on the last two stalls and uploaded them to pastebin:
It looks me like SLPDB catches up to the current block, then just stops processing blocks. e.g. it doesn't seem to process blocks and then stall for some reason, it just never seems to process blocks after catching up with the current chain tip.
I'm running SLPDB v1 (commit f1f48a3) and synced from genesis. I had hoped that syncing from genesis on the latest version would resolve the issue, but it didn't.