You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
During the execution of the first sweep, some operators reported a problem with the Electrum connection leading to an error and the client exiting the signing loop:
2023-06-07T09:11:41.239Z WARN keep-electrum electrum/electrum.go:795 connection to electrum server is down; reconnecting...
2023-06-07T09:11:41.390Z INFO keep-electrum electrum/electrum.go:800 reconnected to electrum server
(...)
2023-06-07T09:16:42.561Z WARN keep-electrum electrum/electrum.go:795 connection to electrum server is down; reconnecting...
2023-06-07T09:16:42.712Z INFO keep-electrum electrum/electrum.go:800 reconnected to electrum server
(...)
2023-06-07T09:21:43.889Z WARN keep-electrum electrum/electrum.go:795 connection to electrum server is down; reconnecting...
2023-06-07T09:21:44.038Z INFO keep-electrum electrum/electrum.go:800 reconnected to electrum server
(...)
2023-06-07T09:31:18.132Z WARN keep-electrum electrum/electrum.go:795 connection to electrum server is down; reconnecting...
2023-06-07T09:31:18.269Z INFO keep-electrum electrum/electrum.go:800 reconnected to electrum server
(...)
2023-06-07T09:32:44.983Z ERROR keep-tbtc tbtc/wallet.go:116 action execution terminated with error: [error while ensuring wallet state is synced between BTC and host chain: [cannot get mempool: [cannot get P2PKH mempool items for public key hash [0xb0ba76edfe18e81365bddd1d46511a57a4ff8dce]: [failed to get mempool for script [0x76a914b0ba76edfe18e81365bddd1d46511a57a4ff8dce88ac]: [retry timeout [2m0s] exceeded; most recent error: [request failed: [use of closed network connection]]]]]]] {"wallet": "0x04b0a483e97dfbb15e88ecbc2ef8f7e37776dd713eed54089f87704a4fbae0442aa3ff5a0ec7f4d52bf4680b5b9b70be9accb64970df11b96abb61d48be7d8db8b", "action": "DepositSweep"}
I received logs from 6 operators. 4 of them were connected to Electrum server and they all had the same problem. 2 of them were connected to Boar and Keep servers and observed no problem during the signing.
The content you are editing has changed. Please copy your edits and refresh the page.
The blockstream's electrums servers seems very unstable and causes a lot
of noise in the logs, even after our optimizations we did in
ba416ce.
Closes: #3612
The blockstream's electrums servers seems very unstable and causes a lot
of noise in the logs, even after our optimizations we did in
ba416ce.
Closes: #3612
β¦rs (#3620)
The blockstream's electrums servers seems very unstable and causes a lot
of noise in the logs, even after our optimizations we did in
ba416ce.
Closes: #3612
@lukasz-zimnoch π§π»ββοΈ
During the execution of the first sweep, some operators reported a problem with the Electrum connection leading to an error and the client exiting the signing loop:
I received logs from 6 operators. 4 of them were connected to Electrum server and they all had the same problem. 2 of them were connected to Boar and Keep servers and observed no problem during the signing.
Pull Requests
The text was updated successfully, but these errors were encountered: