search

lbryio / lbry-desktop

A browser and wallet for LBRY, the decentralized, user-controlled content marketplace.
https://lbry.tech
MIT License
3.57k stars 414 forks source link

LBRY app error on startup: Wallet server took a bit too long to respond #7762

Closed Sessh22 closed 11 months ago

Sessh22 commented 11 months ago

Bug Occasionally when starting the app, I will get a persistent error about how the wallet server was taking too long to connect and LBRY won't start up.

To Reproduce This is intermittent and seems to happen randomly. This PC (Windows 7) is on 24/7 as it LBRY. After some time, LBRY will stop loading channel video lists and stop populating my "Uploads" list prompting me to restart the app. I'd say 4/5 times, the app loads normally upon restart. The other time, I get this error which usually persists for 12-24 hours before spontaneously resolving itself and being fine again for several restarts.

Screenshots Clipboard01

System Configuration

Using most recent LBRY version ( I always update when prompted). I tried rolling back a version and it has no effect on the issue nor did reinstall of the latest 53.9.

Additional context

The following is from the lbrynet.txt file in AppData/Local/lbry/lbrynet:

2023-07-30 11:03:00,202 INFO lbry.wallet.network:254: 2 possible spv servers to try (0 urls in config) 2023-07-30 11:03:00,410 INFO lbry.wallet.network:269: spv17.lbry.com/147.135.65.178:50001 has latency of 206.97ms (available: False, height: 0) 2023-07-30 11:03:03,193 WARNING lbry.wallet.network:284: 2 spv status probes failed, retrying later. servers tried: spv17.lbry.com/147.135.65.178 (('147.135.65.178', 50001)), 54.39.21.165 (('54.39.21.165', 50001)) 2023-07-30 11:03:03,194 WARNING lbry.wallet.network:287: trying fallback to randomly selected spv: 147.135.65.178:50001 2023-07-30 11:03:03,195 INFO lbry.wallet.udp:232: closed udp spv server selection client 2023-07-30 11:03:04,816 WARNING lbry.wallet.network:307: Connecting to 147.135.65.178:50001 failed 2023-07-30 11:03:04,817 WARNING lbry.wallet.network:323: failed to connect to any spv servers, retrying later 2023-07-30 11:03:14,174 INFO lbry.torrent.session:146: torrent alert: UDP error: An existing connection was forcibly closed by the remote host from: 10.5.0.2 op: sock_read 2023-07-30 11:03:34,823 INFO lbry.wallet.network:254: 2 possible spv servers to try (0 urls in config) 2023-07-30 11:03:35,032 INFO lbry.wallet.network:269: spv17.lbry.com/147.135.65.178:50001 has latency of 207.58ms (available: False, height: 0) 2023-07-30 11:03:37,822 WARNING lbry.wallet.network:284: 2 spv status probes failed, retrying later. servers tried: spv17.lbry.com/147.135.65.178 (('147.135.65.178', 50001)), 54.39.21.165 (('54.39.21.165', 50001)) 2023-07-30 11:03:37,823 WARNING lbry.wallet.network:287: trying fallback to randomly selected spv: 54.39.21.165:50001 2023-07-30 11:03:37,824 INFO lbry.wallet.udp:232: closed udp spv server selection client 2023-07-30 11:03:43,829 WARNING lbry.wallet.network:307: Connecting to 54.39.21.165:50001 failed 2023-07-30 11:03:43,830 WARNING lbry.wallet.network:323: failed to connect to any spv servers, retrying later 2023-07-30 11:04:09,173 INFO lbry.torrent.session:146: torrent alert: UDP error: An existing connection was forcibly closed by the remote host from: 10.5.0.2 op: sock_read 2023-07-30 11:04:13,943 INFO lbry.wallet.network:254: 2 possible spv servers to try (0 urls in config) 2023-07-30 11:04:14,156 INFO lbry.wallet.network:269: 147.135.65.178/spv17.lbry.com:50001 has latency of 211.85ms (available: False, height: 0) 2023-07-30 11:04:16,953 WARNING lbry.wallet.network:284: 2 spv status probes failed, retrying later. servers tried: 54.39.21.165 (('54.39.21.165', 50001)), 147.135.65.178/spv17.lbry.com (('147.135.65.178', 50001)) 2023-07-30 11:04:16,954 WARNING lbry.wallet.network:287: trying fallback to randomly selected spv: 54.39.21.165:50001 2023-07-30 11:04:16,955 INFO lbry.wallet.udp:232: closed udp spv server selection client 2023-07-30 11:04:22,945 WARNING lbry.wallet.network:307: Connecting to 54.39.21.165:50001 failed 2023-07-30 11:04:22,946 WARNING lbry.wallet.network:323: failed to connect to any spv servers, retrying later

Any ideas what this might be or how I can resolve it? This is a relatively new issue which started maybe a couple months ago. I was hoping it was temporary, but figured I'd report it here this time and see what's up with this.

amaloy commented 11 months ago

I'm getting the same on Linux.

Sessh22 commented 11 months ago

As I stated in the OP as to how this problem "fixes itself", it once again resolved itself spontaneously later on in the evening which put it at around a full day of not being able to start up under these conditions. I am just wondering if this is a LBRY issue that can be fixed or if it's a server issue and out of the scope of what can be fixed in the app.

Glad to know it's not just me though.

keikari commented 11 months ago

That happens with default hub servers having issues. If it happens again, you could try to connect to Odysee hub, or some other hub. You can do that by adding something like this in your daemon_settings.yml https://lbry.tech/resources/daemon-settings

lbryum_servers:
  - a-hub1.odysee.com:50001

(Hub servers index the metadata from blockchain in a database that can be queried. https://github.com/lbryio/hub)

Sessh22 commented 11 months ago

Cool so I just made a backup of the original daemon_settings.yml file and added this line to the one in use:

lbryum_servers: ['spv11.lbry.com:50001','spv19.lbry.com:50001','a-hub1.odysee.com:50001']

I restarted LBRY with this line in there and it still started up fine. I didn't know if I had to include the two default servers in there or not as I didn't want to override the defaults by using only the odysee one. If I only have the odysee one in this file, does it just include it with the two default servers or does it prioritize this entry?

keikari commented 11 months ago

Not sure how it selects. But if you prefer to use default servers, you can just remove or comment out that line completely. Generally default servers should be up, so rarely need to handle hubs manually.

Sessh22 commented 11 months ago

Ok. I suppose I will just leave it as it is now with three servers (including the two defaults) manually added and see if this happens again. I'll close this issue, but at least there's a solution here to try for anyone else having this issue from time to time.