breez / breez-sdk-greenlight

MIT License
241 stars 42 forks source link

Recover existing node fails with "transport error" #511

Closed JssDWt closed 2 weeks ago

JssDWt commented 1 year ago

SDK version: 0.2.5 Bindings: Rust

Steps to reproduce (I don't know whether it is reproducible, but these were my steps)

Sync fails with:

No credentials found, trying to recover existing node
First run, syncing in foreground
pull changed since 0
forgotten_closed_channels Ok([])
fetching static backup file from node
Sync duration: 9.542260096s
First run, finished running syncing in foreground
SDK initialized in: 9.545900567s
SDK connected in: 11.005153014s
backup status: Ok(BackupStatus { backed_up: true, last_backup_time: None })
Pushing compressed data with size = 2751
set_value key = ["breez-sdk", "backup"] data length=2783
NodeState { id: "0391aaad30180b44512195bbc69a4f7338902cdb0a486ddf1319c19d493fa27536", block_height: 811326, channels_balance_msat: 7269837, onchain_balance_msat: 0, utxos: [], max_payable_msat: 7269837, max_receivable_msat: 3992730163, max_single_payment_amount_msat: 4294967000, max_chan_reserve_msats: 0, connected_peers: ["02c811e575be2df47d8b48dab3d3f1c9b0f6e16d0d40b5ed78253308fc2bd7170d"], inbound_liquidity_msats: 38400163 }
Sync failed: status: Unknown, message: "transport error", details: [], metadata: MetadataMap { headers: {} }
backup sync failed status: Unknown, message: "transport error", details: [], metadata: MetadataMap { headers: {} }

Running a second time in the now initialized working directory does work without errors.

Initializing greenlight from existing credentials
Starting existing node 0391aaad30180b44512195bbc69a4f7338902cdb0a486ddf1319c19d493fa27536
SDK initialized in: 1.711864ms
SDK connected in: 30.346395ms
backup status: Ok(BackupStatus { backed_up: true, last_backup_time: None })
Pushing compressed data with size = 2751
set_value key = ["breez-sdk", "backup"] data length=2783
NodeState { id: "0391aaad30180b44512195bbc69a4f7338902cdb0a486ddf1319c19d493fa27536", block_height: 811326, channels_balance_msat: 7269837, onchain_balance_msat: 0, utxos: [], max_payable_msat: 7269837, max_receivable_msat: 3992730163, max_single_payment_amount_msat: 4294967000, max_chan_reserve_msats: 0, connected_peers: ["02c811e575be2df47d8b48dab3d3f1c9b0f6e16d0d40b5ed78253308fc2bd7170d"], inbound_liquidity_msats: 38400163 }

Recording this event in the case this is reproducible. I don't have time right now to investigate.

JssDWt commented 2 weeks ago

I think most transport errors have been tackled by now