Electrum index error
Opened this issue · 1 comments
da-kami commented
When monitoring the mainnet CFD I opened I noticed that lock confirmation was not being picked up.
I think this is because the connection to Electrum ran into a problem, I found this in the logs:
2022-09-16T12:26:27.584568Z Error: Electrum server error: {"code":-32603,"message":"unavailable index"}
This means the setup is likely not complete!
da-kami commented
Taking it back, Electrum was just slow with syncing the blocks, not sure why.
I restarted electrs service and then the lock transaction was picked up; from the ItchySats service logs:
txid=8c22aac2decf26083881dd0be481a81b2a59fa97487b03f1a81b3b33f37a20e3 status=confirmed with 4 blocks
2022-09-16T13:21:23.357080Z 2022-09-16 13:21:23 DEBUG Send message every interval{interval_secs=20}:xtra_actor_request{actor_type=daemon::monitor::Actor message_type=daemon::monitor::Sync}:xtra_message_handler:Handle Sync:Sync monitor: btsieve: Bitcoin transaction reached monitoring target txid=8c22aac2decf26083881dd0be481a81b2a59fa97487b03f1a81b3b33f37a20e3 target=confirmed with 1 blocks current=confirmed with 4 blocks
2022-09-16T13:21:23.358144Z 2022-09-16 13:21:23 INFO Send message every interval{interval_secs=20}:xtra_actor_request{actor_type=daemon::monitor::Actor message_type=daemon::monitor::Sync}:xtra_message_handler:Handle Sync:Sync monitor: model::cfd: order_id=3e46c7a5-a5a7-4094-9f37-2688a7ca02db peer_id=Some(12D3KooWP3BN6bq9jPy8cP7Grj1QyUBfr7U6BeQFgMwfTTu12wuY) Issuing event: LockConfirmed
We should still investigate if the previously reported error {"code":-32603,"message":"unavailable index"} can be a problem - but it looks like this was a temporary issue. Removing the bug and critical label.