LifeSaver
ElementsProject/lightning

Solvedlightning bitcoin-cli exec failed: No such file or directory

kryo2k posts at
ElementsProject/lightning
kryo2k
271

This might be due to my setup, but here's the full log. The bitcoin-cli script is located in the same directory I am calling lightningd from.

./lightningd --network=testnet --log-level=debug --bitcoin-datadir="$HOME/.bitcoin"
2805 bytes, Wed Jan 17 07:00:10 2018
+0.021871853 lightningd(4621):DEBUG: Trying to guess public addresses...
+0.021943165 lightningd(4621):DEBUG: Address *.*.*.*:9735 is not routable
+0.021973197 lightningd(4621):DEBUG: Failed to connect 10 socket: Network is unreachable
+0.022974651 lightningd(4621):DEBUG: testing ~/lightning/lightningd/lightning_channeld
+0.024865263 lightningd(4621):DEBUG: testing ~/lightning/lightningd/lightning_closingd
+0.026722068 lightningd(4621):DEBUG: testing ~/lightning/lightningd/lightning_gossipd
+0.028319916 lightningd(4621):DEBUG: testing ~/lightning/lightningd/lightning_hsmd
+0.029509792 lightningd(4621):DEBUG: testing ~/lightning/lightningd/lightning_onchaind
+0.031377750 lightningd(4621):DEBUG: testing ~/lightning/lightningd/lightning_openingd
+0.074536457 lightningd(4621):DEBUG: HSM TRACE: Client: Received message 11 from client
+0.098804596 lightningd(4621):DEBUG: Loaded 0 invoices from DB
+0.098956937 lightningd(4621):DEBUG: HSM TRACE: Client: Received message 9 from client
+0.099308768 lightning_gossipd(4629):DEBUG: pid 4629, msgfd 12
+0.099475284 lightningd(4621):DEBUG: Loaded 0 channels from DB
+0.111171097 lightningd(4621):BROKEN: bitcoin-cli exec failed: No such file or directory
+0.111329584 lightningd(4621):BROKEN: FATAL SIGNAL 6 RECEIVED
+0.116936853 lightningd(4621):BROKEN: backtrace: lightningd/log.c:436 (log_crash) 0x40ffe9
+0.116971181 lightningd(4621):BROKEN: backtrace: (null):0 ((null)) 0x7f9c5824e4af
+0.116982399 lightningd(4621):BROKEN: backtrace: (null):0 ((null)) 0x7f9c5824e428
+0.116991647 lightningd(4621):BROKEN: backtrace: (null):0 ((null)) 0x7f9c58250029
+0.117001423 lightningd(4621):BROKEN: backtrace: lightningd/log.c:525 (fatal) 0x410423
+0.117268675 lightningd(4621):BROKEN: backtrace: lightningd/bitcoind.c:664 (wait_for_bitcoind) 0x4053be
+0.117586775 lightningd(4621):BROKEN: backtrace: lightningd/chaintopology.c:726 (setup_topology) 0x4079f6
+0.117762875 lightningd(4621):BROKEN: backtrace: lightningd/lightningd.c:326 (main) 0x40e952
+0.117774621 lightningd(4621):BROKEN: backtrace: (null):0 ((null)) 0x7f9c5823982f
+0.117783345 lightningd(4621):BROKEN: backtrace: (null):0 ((null)) 0x403138
+0.117790538 lightningd(4621):BROKEN: backtrace: (null):0 ((null)) 0xffffffffffffffff

 ((null)) 0x7f16179b082f
+0.223667773 lightningd(4377):BROKEN: backtrace: (null):0 ((null)) 0x403138
+0.223676502 lightningd(4377):BROKEN: backtrace: (null):0 ((null)) 0xffffffffffffffff
25 Answers
Share
Original

✔️Accepted Answer

practicalswift
31

To make things more friendly for new c-lightning users we could perhaps add more helpful error messages for the most common failure scenarios:

  • bitcoind not installed/running – suggest installing Bitcoin Core
  • bitcoin-cli not in PATH – suggest updating PATH
  • bitcoin-cli in PATH but unable to connect to bitcoind – suggest configuring RPC, etc.
  • bitcoind not in sync yet – inform user about blockchain synchronization times

Any other common failure scenarios for users just getting started with c-lightning? :-)

Other Answers:

jb55
15

Related Issues:

6
lightning bitcoin-cli exec failed: No such file or directory
To make things more friendly for new c-lightning users we could perhaps add more helpful error messa...
LifeSaver
Privacy PolicyDisclaimer