We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I've noticed something like this flooding my logs every now and then, which is a potential cause of excessive log file size.
13 08:15:48, coins:rpc_clients:2045] INFO Electrum client connected to electrs.electroncash.de:60002 13 08:15:49, coins:rpc_clients:2069] INFO EOF from electrs.electroncash.de:60002 13 08:15:49, coins:rpc_clients:2111] INFO electrs.electroncash.de:60002 connection dropped 13 08:15:49, utxo:1821] Electrum electrs.electroncash.de:60002 server.version error "JsonRpcError { client_info: "coin: tBCH", request: JsonRpcRequest { jsonrpc: "2.0", id: "18", method: "server.version", params: [String("AtomicDex Desktop 0.5.4-beta GUI/MM2 2.1.5183_dev_6a634c091_Linux_Release"), Array([String("1.2"), String("1.4")])] }, error: Transport("rpc_clients:1446] rpc_clients:2278] rpc_clients:2276] 60s timed out waiting for the future to complete") }".
Also seen with VRSC earlier
07 08:31:13, utxo:1539] Electrum el0.verus.io:17486 server.version error "JsonRpcError { client_info: "coin: VRSC", request: JsonRpcRequest { jsonrpc: "2.0", id: "173843", method: "server.version", params: [String("MM2CLI GUI/MM2 2.1.5048_mm2.1_879f96abb_Linux_Release"), Array([String("1.2"), String("1.4")])] }, error: Transport("rpc_clients:1297] rpc_clients:2097] rpc_clients:2095] 60s timed out waiting for the future to complete") }".
Seen on versions: 2.1.5048_mm2.1_879f96abb_Linux_Release (VRSC) 2.1.5183_dev_6a634c091_Linux_Release (tBCH)
2.1.5048_mm2.1_879f96abb_Linux_Release
2.1.5183_dev_6a634c091_Linux_Release
Results scanning my logs folder for "waiting for the future":
Reached maximum result size. Check "find_in_files_max_result_size". 24966 matches across 36 files
The text was updated successfully, but these errors were encountered:
Avoid log spam on malfunctioning electrums reconnects #1193 #1161.
5a4157c
Avoid log spam and malfunctioning electrums excessive reconnects #1193 …
e9707d4
…#1161. (#1194) * Avoid log spam on malfunctioning electrums reconnects #1193 #1161. * Fix Clippy and WASM.
Fixed in the linked PR. Thanks for the report!
Sorry, something went wrong.
artemii235
No branches or pull requests
I've noticed something like this flooding my logs every now and then, which is a potential cause of excessive log file size.
Also seen with VRSC earlier
Seen on versions:
2.1.5048_mm2.1_879f96abb_Linux_Release
(VRSC)2.1.5183_dev_6a634c091_Linux_Release
(tBCH)Results scanning my logs folder for "waiting for the future":
The text was updated successfully, but these errors were encountered: