node-launcher
node-launcher copied to clipboard
Mac OS 6.0.7 Node Launcher
-
I'm submitting a ...
- [ ] bug report
- [ ] feature request
- [x ] support request
-
What is the current behavior? If I download the .zip of the 6.0.7 mac os node launcher, unzip and double-click on Node Launcher from .zip file, I get a warning that I should download 6.0.7 and that I am running 6.0.6. Opening Node Launcher Advanced confirms that I am at 6.0.6. Sorry if this is a repeat, I could not find the earlier thread.
-
If the current behavior is a bug, please provide the steps to reproduce
-
What is the expected behavior? That the version would display as 6.0.7 and I would not get a warning message.
-
What is the motivation / use case for changing the behavior?
-
Please tell us about your environment:
- Operating System: [ Windows | macOS | Linux ] mac OS Catalina 10.15.2
-
Other information (e.g. detailed explanation, stacktraces, related issues, suggestions how to fix, links for us to have context, eg. stackoverflow, gitter, etc)
I confirm that. I downloaded the 6./0.7 version and have this.
Node Launcher version 6.0.6
Error information:
HTTPSConnectionPool(host='github.com', port=443): Max retries exceeded with url: /lightningnetwork/lnd/releases/download/v0.7.1-beta/lnd-darwin-amd64-v0.7.1-beta.tar.gz (Caused by NewConnectionError(': Failed to establish a new connection: [Errno 22] Invalid argument'))
File "run.py", line 22, in File "node_launcher/gui/application.py", line 15, in __init__ File "node_launcher/node_set/node_set.py", line 41, in __init__ File "node_launcher/node_set/lnd.py", line 90, in __init__ File "node_launcher/services/lnd_software.py", line 15, in lnd File "node_launcher/services/node_software.py", line 72, in executable_path File "node_launcher/services/node_software.py", line 81, in download File "requests/api.py", line 75, in get File "requests/api.py", line 60, in request File "requests/sessions.py", line 533, in request File "requests/sessions.py", line 646, in send File "requests/adapters.py", line 516, in send
I don't receive any alert/error. More simply, nothing happens.
I also find that despite the warning to upgrade to 6.0.7, the Node Launcher which announces itself as 6.0.6 will run, and the Bitcoin section sync's OK, but the Lightning section stops with this output error:
2020-01-03 10:20:24.169 [INF] LTND: Version: 0.7.1-beta commit=v0.7.1-beta, build=production, logging=default
2020-01-03 10:20:24.169 [INF] LTND: Active chain: Bitcoin (network=mainnet)
2020-01-03 10:20:24.170 [INF] CHDB: Checking for schema update: latest_version=9, db_version=9
2020-01-03 10:20:24.178 [INF] RPCS: password RPC server listening on 127.0.0.1:10009
2020-01-03 10:20:24.178 [INF] RPCS: password gRPC proxy started at 127.0.0.1:8080
2020-01-03 10:20:24.178 [INF] LTND: Waiting for wallet encryption password. Use lncli create
to create a wallet, lncli unlock
to unlock an existing wallet, or lncli changepassword
to change the password of an existing wallet and unlock it.
2020-01-03 10:20:26.319 [INF] LNWL: Opened wallet
2020-01-03 10:20:26.414 [INF] LTND: Primary chain is set to: bitcoin
2020-01-03 10:20:26.438 [ERR] LTND: Unable to create chain control: unable to connect to bitcoind: -28: Loading block index...
2020-01-03 10:20:26.438 [INF] LTND: Shutdown complete
Unable to create chain control: unable to connect to bitcoind: -28: Loading block index...
2020-01-03 10:20:29.969 [INF] LTND: Version: 0.7.1-beta commit=v0.7.1-beta, build=production, logging=default
2020-01-03 10:20:29.969 [INF] LTND: Active chain: Bitcoin (network=mainnet)
2020-01-03 10:20:29.970 [INF] CHDB: Checking for schema update: latest_version=9, db_version=9
2020-01-03 10:20:29.979 [INF] RPCS: password RPC server listening on 127.0.0.1:10009
2020-01-03 10:20:29.979 [INF] RPCS: password gRPC proxy started at 127.0.0.1:8080
2020-01-03 10:20:29.979 [INF] LTND: Waiting for wallet encryption password. Use lncli create
to create a wallet, lncli unlock
to unlock an existing wallet, or lncli changepassword
to change the password of an existing wallet and unlock it.
2020-01-03 10:20:30.835 [INF] LNWL: Opened wallet
2020-01-03 10:20:30.936 [INF] LTND: Primary chain is set to: bitcoin
2020-01-03 10:20:30.961 [ERR] LTND: Unable to create chain control: unable to connect to bitcoind: -28: Verifying blocks...
Unable to create chain control: unable to connect to bitcoind: -28: Verifying blocks...
2020-01-03 10:20:30.961 [INF] LTND: Shutdown complete
2020-01-03 10:20:33.978 [INF] LTND: Version: 0.7.1-beta commit=v0.7.1-beta, build=production, logging=default
2020-01-03 10:20:33.978 [INF] LTND: Active chain: Bitcoin (network=mainnet)
2020-01-03 10:20:33.979 [INF] CHDB: Checking for schema update: latest_version=9, db_version=9
2020-01-03 10:20:33.988 [INF] RPCS: password RPC server listening on 127.0.0.1:10009
2020-01-03 10:20:33.988 [INF] RPCS: password gRPC proxy started at 127.0.0.1:8080
2020-01-03 10:20:33.988 [INF] LTND: Waiting for wallet encryption password. Use lncli create
to create a wallet, lncli unlock
to unlock an existing wallet, or lncli changepassword
to change the password of an existing wallet and unlock it.
2020-01-03 10:20:34.911 [INF] LNWL: Opened wallet
2020-01-03 10:20:35.008 [INF] LTND: Primary chain is set to: bitcoin
2020-01-03 10:20:35.033 [ERR] LTND: Unable to create chain control: unable to connect to bitcoind: -28: Verifying blocks...
2020-01-03 10:20:35.033 [INF] LTND: Shutdown complete
Unable to create chain control: unable to connect to bitcoind: -28: Verifying blocks...
Does anyone know of a workaround for this?
Thanks,
Edward
I updated to latest.
It tells me otherwise.