lbrynet-daemon.exe disappears randomly #396

New issue

Closed

opened 2017-07-27 20:24:06 +02:00 by tzarebczan · 6 comments

tzarebczan commented

2017-07-27 20:24:06 +02:00

(Migrated from github.com)

The Issue

We've seen this in the past, but I've decided to make an issue for it as it seems to keep happening. The best way to try to reproduce it is crash your PC unexpectedly while LBRY is running. After restart, the daemon file is missing from C:\Program Files (x86)\LBRY\resources\app\dist and when starting LBRY, you get an error message (see below). LBRY.exe gets stuck in this case because it can't find a daemon and must be manually closed.

Steps to reproduce

Run LBRY
force crash PC
Start LBRY after reboot

Expected behaviour

Daemon does not get deleted

Actual behaviour

daemon is deleted

System Configuration

LBRY Daemon version: 0.14.2
LBRY App version: 0.14rc2
LBRY Installation ID:
Operating system:

Anything Else

Screenshots

## The Issue We've seen this in the past, but I've decided to make an issue for it as it seems to keep happening. The best way to try to reproduce it is crash your PC unexpectedly while LBRY is running. After restart, the daemon file is missing from C:\Program Files (x86)\LBRY\resources\app\dist and when starting LBRY, you get an error message (see below). LBRY.exe gets stuck in this case because it can't find a daemon and must be manually closed. ### Steps to reproduce 1. Run LBRY 2. force crash PC 3. Start LBRY after reboot ### Expected behaviour Daemon does not get deleted ### Actual behaviour daemon is deleted ## System Configuration   - LBRY Daemon version: 0.14.2 - LBRY App version: 0.14rc2 - LBRY Installation ID: - Operating system: ## Anything Else  ## Screenshots  ![27206445-b6c3d40c-5205-11e7-9606-cdaf8d4ed7c6](https://user-images.githubusercontent.com/8120721/28685840-1d365d62-72d7-11e7-9770-d85cb205892a.png)

akinwale commented

2017-08-30 07:01:05 +02:00

(Migrated from github.com)

@tzarebczan I'm curious so that I can reproduce the issue. How do you force the crash?

MSFTserver commented

2017-08-30 08:17:30 +02:00

(Migrated from github.com)

@akinwale http://www.wikihow.com/Force-a-Blue-Screen-in-Windows
also you could try ending needed windows services in task manager eventually it will crash

@akinwale http://www.wikihow.com/Force-a-Blue-Screen-in-Windows also you could try ending needed windows services in task manager eventually it will crash

tzarebczan commented

2017-09-06 17:05:05 +02:00

(Migrated from github.com)

@akinwale just force shutdown the PC (hold power button) while LBRY is running. Or if you are running a VM, force close the VM without saving. I haven't tried this recently nor have I really tried to reproduce it, I just know it happened to me the couple of times my PC did a hard shutdown.

tzarebczan commented

2017-11-13 22:26:45 +01:00

(Migrated from github.com)

@kauffj mentioned he ran into this on Linux as well.

If we can't figure out why its happening, I think we should have the app download the daemon if its missing in the mean time.

@kauffj mentioned he ran into this on Linux as well. If we can't figure out why its happening, I think we should have the app download the daemon if its missing in the mean time.

tzarebczan commented

2018-02-09 04:45:12 +01:00

(Migrated from github.com)

@IGassmann the current app behavior now when this happens (removing lbrynet-daemon) is the green loading screen that gets stuck at "Starting daemon" indefinitely. How can we improve this behavior?

That being said, have not heard of any reports of this happening.

@IGassmann the current app behavior now when this happens (removing lbrynet-daemon) is the green loading screen that gets stuck at "Starting daemon" indefinitely. How can we improve this behavior? That being said, have not heard of any reports of this happening.

lyoshenka commented

2018-02-12 21:53:20 +01:00

(Migrated from github.com)

hasn't happened in a while, closing this. if you can repro, we'll look again.