Handle daemon not fully starting scenario better #2021

Closed
opened 2018-10-09 20:49:01 +02:00 by tzarebczan · 4 comments
tzarebczan commented 2018-10-09 20:49:01 +02:00 (Migrated from github.com)

The Issue

Handle scenarios like https://github.com/lbryio/lbry-desktop/issues/2020 where the daemon doesn't fully connect to the LBRY network, and thus the app gets stuck on initializing. We should try connecting for some period of time before timing out and showing an error message similar to:9844cbdaf6/src/renderer/component/splash/view.jsx (L54)
along with a link to https://lbry.io/faq/startup-troubleshooting

System Configuration

  • LBRY Daemon version:
  • LBRY App version:
  • LBRY Installation ID:
  • Operating system:

Anything Else

Screenshots

Acceptance Criteria

Definition of Done

  • Tested against acceptance criteria
  • Tested against the assumptions of the user story
  • The project builds without errors
  • Unit tests are written and passing
  • Tests on devices/browsers listed in the issue have passed
  • QA performed & issues resolved
  • Refactoring completed
  • Any configuration or build changes documented
  • Documentation updated
  • Peer Code Review performed
<!-- Thanks for reporting an issue to LBRY and helping us improve! To make it possible for us to help you, please fill out below information carefully. Before reporting any issues, please make sure that you're using the latest version. - App releases: https://github.com/lbryio/lbry-desktop/releases - Standalone daemon: https://github.com/lbryio/lbry/releases We are also available on live chat at https://chat.lbry.io --> ## The Issue Handle scenarios like https://github.com/lbryio/lbry-desktop/issues/2020 where the daemon doesn't fully connect to the LBRY network, and thus the app gets stuck on initializing. We should try connecting for some period of time before timing out and showing an error message similar to:https://github.com/lbryio/lbry-desktop/blob/9844cbdaf6f6cad3eefba7dfaa1a7598cdbb1bd1/src/renderer/component/splash/view.jsx#L54 along with a link to https://lbry.io/faq/startup-troubleshooting ## System Configuration <!-- For the app, this info is in the About section at the bottom of the Help page. You can include a screenshot instead of typing it out --> <!-- For the daemon, run: curl 'http://localhost:5279' --data '{"method":"version"}' and include the full output --> - LBRY Daemon version: - LBRY App version: - LBRY Installation ID: - Operating system: ## Anything Else <!-- Include anything else that does not fit into the above sections --> ## Screenshots <!-- If a screenshot would help explain the bug, please include one or two here --> ### Acceptance Criteria 1. 2. 3. ### Definition of Done - [ ] Tested against acceptance criteria - [ ] Tested against the assumptions of the user story - [ ] The project builds without errors - [ ] Unit tests are written and passing - [ ] Tests on devices/browsers listed in the issue have passed - [ ] QA performed & issues resolved - [ ] Refactoring completed - [ ] Any configuration or build changes documented - [ ] Documentation updated - [ ] Peer Code Review performed
phillipyork commented 2018-10-31 16:36:11 +01:00 (Migrated from github.com)

I have this exact problem .where the daemon doesn't fully connect to the LBRY network, and thus the app gets stuck on initializing. screen shot below

snapshot

**I have this exact problem .where the daemon doesn't fully connect to the LBRY network, and thus the app gets stuck on initializing.** screen shot below ![snapshot](https://user-images.githubusercontent.com/26136041/47797972-a6916200-dce4-11e8-8805-5378c4928a3f.PNG)
tzarebczan commented 2018-10-31 16:46:04 +01:00 (Migrated from github.com)

@phillipyork can you send us your logfile (https://lbry.io/faq/how-to-find-lbry-log-file) so we can better diagnose it? Or you can also look at https://lbry.io/faq/startup-troubleshooting in the meantime.

@phillipyork can you send us your logfile (https://lbry.io/faq/how-to-find-lbry-log-file) so we can better diagnose it? Or you can also look at https://lbry.io/faq/startup-troubleshooting in the meantime.
phillipyork commented 2018-10-31 21:18:55 +01:00 (Migrated from github.com)

lbrynet.log

heres my log file

[lbrynet.log](https://github.com/lbryio/lbry-desktop/files/2536243/lbrynet.log) heres my log file
tzarebczan commented 2018-11-01 15:16:21 +01:00 (Migrated from github.com)

@phillipyork , This would be better over email. Do you have AVG, AVAST or another Antivirus program installed? I've seen this error previously when LBRY is blocked from startup. If not, can you also try rebooting your machine and trying again? Let's please continue this over email or #help at https://chat.lbry.io

@phillipyork , This would be better over email. Do you have AVG, AVAST or another Antivirus program installed? I've seen this error previously when LBRY is blocked from startup. If not, can you also try rebooting your machine and trying again? Let's please continue this over email or #help at https://chat.lbry.io
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: LBRYCommunity/lbry-desktop#2021
No description provided.