-
Notifications
You must be signed in to change notification settings - Fork 413
New issue
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
LBRY daemon does not always launch when the app runs #19
Comments
I can vouch that it doesn't work for me. MacOS 10.12.3 Hey stupid question: With the commandline version of the daemon I see python. What version of python is required for all this to run properly? Note: The commandline version doesn't work for me either. |
@drakythe installing the daemon from source is (relatively) painless: https://github.com/lbryio/lbry/blob/master/INSTALL.md If you're also not seeing the daemon run properly when run directly, that may explain why it is not launching when the browser runs either. Could you share the output of why it is failing? Thank you! |
Sure, output I get when I try to run the daemon is this: lbrynet-daemon-v0.9.1-macos $ ./lbrynet-daemon
2017-03-22 15:28:59,201 INFO lbrynet.lbrynet_daemon.DaemonControl:92: Starting lbrynet-daemon from command line
2017-03-22 15:28:59,804 INFO lbrynet.lbrynet_daemon.DaemonControl:126: Making attempt 1 / 5 to startup
2017-03-22 15:28:59,807 INFO lbrynet.lbrynet_daemon.DaemonServer:56: Using non-authenticated API
2017-03-22 15:28:59,808 INFO lbrynet.lbrynet_daemon.DaemonServer:40: Daemon already running, exiting app
Unhandled error in Deferred:
2017-03-22 15:28:59,808 CRITICAL twisted:154: Unhandled error in Deferred:
2017-03-22 15:28:59,810 CRITICAL twisted:154:
Traceback (most recent call last):
File "site-packages/twisted/internet/defer.py", line 1299, in _inlineCallbacks
File "site-packages/lbrynet/lbrynet_daemon/DaemonServer.py", line 47, in start
File "site-packages/lbrynet/lbrynet_daemon/DaemonServer.py", line 41, in _setup_server
SystemExit: 1 And it just hangs there. If I force exit the script with a ctrl+c I get this ^CUnhandled Error
Traceback (most recent call last):
File "daemon.py", line 4, in <module>
File "site-packages/lbrynet/lbrynet_daemon/DaemonControl.py", line 97, in start
File "site-packages/twisted/internet/base.py", line 1199, in run
File "site-packages/twisted/internet/base.py", line 1208, in mainLoop
--- <exception caught here> ---
File "site-packages/twisted/internet/base.py", line 801, in runUntilCurrent
File "site-packages/twisted/internet/base.py", line 584, in stop
twisted.internet.error.ReactorNotRunning: Can't stop reactor that isn't running.
2017-03-22 15:31:22,319 CRITICAL twisted:154: Unhandled Error
Traceback (most recent call last):
File "daemon.py", line 4, in <module>
File "site-packages/lbrynet/lbrynet_daemon/DaemonControl.py", line 97, in start
File "site-packages/twisted/internet/base.py", line 1199, in run
File "site-packages/twisted/internet/base.py", line 1208, in mainLoop
--- <exception caught here> ---
File "site-packages/twisted/internet/base.py", line 801, in runUntilCurrent
File "site-packages/twisted/internet/base.py", line 584, in stop
twisted.internet.error.ReactorNotRunning: Can't stop reactor that isn't running.
2017-03-22 15:31:22,321 INFO lbrynet.lbrynet_daemon.Daemon:523: Closing lbrynet session
2017-03-22 15:31:22,322 INFO lbrynet.lbrynet_daemon.Daemon:524: Status at time of shutdown: initializing
2017-03-22 15:31:22,323 INFO lbrynet.lbrynet_daemon.ExchangeRateManager:163: Stopping exchange rate manager Further, if I leave it running for a bit, and then ctrl+c it I get ^C2017-03-22 15:31:02,036 INFO lbrynet.lbrynet_daemon.Daemon:523: Closing lbrynet session
2017-03-22 15:31:02,037 INFO lbrynet.lbrynet_daemon.Daemon:524: Status at time of shutdown: initializing
2017-03-22 15:31:02,037 INFO lbrynet.lbrynet_daemon.ExchangeRateManager:163: Stopping exchange rate manager Which seems to indicate it reached further than the first message, but it never goes anywhere or gives any further output. And no matter how long I wait a curl against localhost/127.0.0.1 won't return anything. This is all on my iMac. Out of curiosity I installed the app on my Air, and it worked without issue. I have not yet tried just the daemon, but I imagine it works just fine. |
@drakythe Can you check your task/process manager and ensure there is not already a frozen copy running? The output seems to indicate that. Though it certainly didn't handle it cleanly. |
@kauffj I'm not 100% sure what I'm looking for, but reviewing my Activity Monitor does not seem to indicate a running lbry process, either under that name, a Daemon name, or a python process. Can you give me the exact task I should be looking for? |
@drakythe Sounds like probably a bug on our end. The way the app is spawning and killing the daemon process is being changed (literally by the guy sitting next to me as I type this), so let's wait until the next release and see if this is cleaned up. |
@alexliebowitz is this fixed? |
Hmm, I guess I'd call it "mostly fixed." It's really more of a category of problems that all cause the same symptom. If memory serves, we decided that it usually happens because there's a hung daemon process running and the app latches onto that instead of starting a new one. The main thing we've done to reduce that issue is that we now stop the daemon by issuing a Things we can do in the future:
We could close this issue now since it seems like it's improved a lot already, and getting it down to 0 will be a gradual process. Or we could leave it open until we're confident that we've got it down to an acceptable level. |
@kauffj is this related to the same issue Niko and I have been seeing on Linux with daemon start up? I have to retry it many times before it gets past "starting daemon....". |
Yes, this sounds like the same issue.
…On Mon, May 29, 2017 at 8:13 PM, Thomas Zarebczan ***@***.***> wrote:
@kauffj <https://github.com/kauffj> is this related to the same issue
Niko and I have been seeing on Linux with daemon start up? I have to retry
it many times before it gets past "starting daemon....".
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#19 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAgZVq5kDG1CvKuBIh5gtRbbDn9KUtcPks5r-19BgaJpZM4Mhv9V>
.
--
Jeremy Kauffman, Founder, LBRY <http://lbry.io/>
(267) 210-4292
Build LBRY: get <https://lbry.io/get>, follow <https://twitter.com/lbryio>,
like <https://facebook.com/lbryio>
|
I ran into some issues as well. Working on a script to see if it helps. |
Logfile from a Linux user with daemon startup issues |
https://github.com/sleepdefic1t/lbryBuilder let me know if this helps. |
request() didn't hit the callback sometimes fixes lbryio#19 fixes lbryio#188
The Issue
I've heard of this issue on Reddit and from several people on Slack, but I have not experienced it myself.
Several people report that the daemon does not launch when the app is run and that they have to launch it manually to get it to work.
Steps to reproduce
I can't :(
Expected behaviour
App launches daemon.
Actual behaviour
Sometimes it doesn't, apparently.
The text was updated successfully, but these errors were encountered: