Open lilaclabs opened 5 years ago
PierreRochard
commented
5 years ago That is odd. I don't have an exact answer but I would note that Bitcoin Core does not need to be installed for the Node Launcher.
Leaving this issue open in case others have the same error
DriftwoodPalace
commented
5 years ago Windows usually don't like it if two services are trying to use the same ports. Might be the case here. You could download https://docs.microsoft.com/en-us/sysinternals/downloads/tcpview and monitor the activity on your network. Look for other services that might use port 3332, 8008 or 10009 and close any if you find.
Another option is to simply change the port number in the config-file and see if there's any difference.
I'm submitting a ...
What is the current behavior? After starting LND it begins to sync but then crashes and reports a port related error. Occurred on initial attempt to use node launcher. Managed to get this to work briefly by completely uninstalling Bitcoin Core and reinstalling it and going through Node Launcher from scratch again, but error started occurring again on second time running application and persists despite restarts of computer. Wiping LND doesn't seem to prevent the error.
Error message is as follows: 2019-03-08 07:54:10.664 [INF] LTND: Initializing bitcoind backed fee estimator 2019-03-08 07:54:11.478 [INF] LNWL: The wallet has been unlocked without a time limit 2019-03-08 07:54:11.488 [INF] LTND: LightningWallet opened 2019-03-08 07:54:11.497 [INF] LNWL: Caught up to height 20000 2019-03-08 07:54:11.513 [INF] HSWC: Restoring in-memory circuit state from disk 2019-03-08 07:54:11.514 [INF] HSWC: Payment circuits loaded: num_pending=0, num_open=0 2019-03-08 07:54:11.537 [INF] RPCS: RPC server listening on 127.0.0.1:10009 2019-03-08 07:54:11.560 [INF] RPCS: gRPC proxy started at 127.0.0.1:8080 2019-03-08 07:54:11.564 [INF] LTND: Waiting for chain backend to finish sync, start_height=566184 2019-03-08 07:54:41.031 [INF] LNWL: Caught up to height 30000 2019-03-08 07:54:55.397 [WRN] LNWL: Unable to synchronize wallet to chain: Post http://127.0.0.1:8332: dial tcp 127.0.0.1:8332: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted. 2019-03-08 07:54:55.787 [INF] LTND: Shutdown complete Post http://127.0.0.1:8332: dial tcp 127.0.0.1:8332: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.
If the current behavior is a bug, please provide the steps to reproduce Attempting to launch LND triggers it.
What is the expected behavior? Correct sync of LND
What is the motivation / use case for changing the behavior?
Please tell us about your environment: Windows 10 64-bit Professional
Other information (e.g. detailed explanation, stacktraces, related issues, suggestions how to fix, links for us to have context, eg. stackoverflow, gitter, etc)