v24.08rc2 - bitcoin-cli not a valid config option

[nakoshi-satamoto]

I'm trying to test v24.08rc2
When I attempt to start lightningd I get an error message saying that "bitcoin-cli" is an unknown configuration option. This is a valid config option in v24.05 though, my bitcoin-cli is in a specific filepath that needs declared. Was this config changed in 24.08rc2 to something else?

[nakoshi-satamoto]

Example of my current config

bitcoin-cli=/home/satoshi/bitcoin-27.3/bin/bitcoin-cli

[nakoshi-satamoto]

lightningd: Config file /home/user/.lightning/config line 8: bitcoin-cli=/home/satoshi/bitcoin-27.0/bin/bitcoin-cli: unknown option

[vincenzopalazzo]

Can you post your logs? it is possible that some plugin like bcli.c is dying?

[nakoshi-satamoto]

When I go back to version 24.05 it works as normally. In this case the log shows nothing for 24.08rc2, I can re-attempt later in debug mode and post logs here.

[nakoshi-satamoto]

No other data in log file when attempted in debug

`2024-08-21T16:12:35.311Z INFO lightningd: v24.08rc2

2024-08-21T16:12:35.311Z DEBUG lightningd: Opened log file /home/satoshi/.lightning/ln-log.txt

2024-08-21T16:12:35.326Z DEBUG plugin-manager: started(1446405) /home/satoshi/apps/peerswap/peerswap

2024-08-21T16:12:35.341Z DEBUG lightningd: io_break: check_plugins_manifests

2024-08-21T16:12:35.341Z DEBUG lightningd: io_loop_with_timers: plugins_init
`

standard output shows
lightningd: Config file /home/satoshi/.lightning/config line 8: bitcoin-cli=/home/satoshi/apps/bitcoin-core/bitcoin-27.0/bin/bitcoin-cli: unknown option

[nakoshi-satamoto]

v24.08rc2 is not accepting required config settings necessary to work with Bitcoin Core.

[Lagrang3]

When lightningd starts you should see a lot of plugin-maganer lines indicating the PID of the default plugins.
bitcoin-cli is an option defined within bcli plugin. In your logs there is only peerswap being started. Usually you should see:

2024-08-27T15:31:30.965Z INFO    lightningd: v24.08rc3-1-g48fa438-modded
2024-08-27T15:31:30.994Z INFO    lightningd: Creating configuration directory /tmp/l1/regtest
2024-08-27T15:31:30.994Z DEBUG   lightningd: Opened log file /tmp/l1/log
2024-08-27T15:31:30.996Z DEBUG   plugin-manager: started(508405) /home/lagrange/lightning/plugins/autoclean
2024-08-27T15:31:30.997Z DEBUG   plugin-manager: started(508408) /home/lagrange/lightning/plugins/chanbackup
2024-08-27T15:31:30.999Z DEBUG   plugin-manager: started(508413) /home/lagrange/lightning/plugins/bcli
2024-08-27T15:31:31.000Z DEBUG   plugin-manager: started(508416) /home/lagrange/lightning/plugins/commando
2024-08-27T15:31:31.002Z DEBUG   plugin-manager: started(508420) /home/lagrange/lightning/plugins/funder
2024-08-27T15:31:31.003Z DEBUG   plugin-manager: started(508424) /home/lagrange/lightning/plugins/topology
2024-08-27T15:31:31.004Z DEBUG   plugin-manager: started(508427) /home/lagrange/lightning/plugins/keysend
2024-08-27T15:31:31.005Z DEBUG   plugin-manager: started(508430) /home/lagrange/lightning/plugins/offers
2024-08-27T15:31:31.006Z DEBUG   plugin-manager: started(508433) /home/lagrange/lightning/plugins/pay
2024-08-27T15:31:31.008Z DEBUG   plugin-manager: started(508436) /home/lagrange/lightning/plugins/recklessrpc
2024-08-27T15:31:31.009Z DEBUG   plugin-manager: started(508441) /home/lagrange/lightning/plugins/recover
2024-08-27T15:31:31.010Z DEBUG   plugin-manager: started(508444) /home/lagrange/lightning/plugins/txprepare
2024-08-27T15:31:31.011Z DEBUG   plugin-manager: started(508447) /home/lagrange/lightning/plugins/cln-renepay
2024-08-27T15:31:31.012Z DEBUG   plugin-manager: started(508449) /home/lagrange/lightning/plugins/spenderp
2024-08-27T15:31:31.013Z DEBUG   plugin-manager: started(508453) /home/lagrange/lightning/plugins/cln-askrene
2024-08-27T15:31:31.014Z DEBUG   plugin-manager: started(508456) /home/lagrange/lightning/plugins/sql
2024-08-27T15:31:31.015Z DEBUG   plugin-manager: started(508459) /home/lagrange/lightning/plugins/bookkeeper
2024-08-27T15:31:31.017Z DEBUG   plugin-manager: started(508460) /home/lagrange/lightning/plugins/clnrest/clnrest
2024-08-27T15:31:31.018Z DEBUG   plugin-manager: started(508461) /home/lagrange/lightning/plugins/wss-proxy/wss-proxy
2024-08-27T15:31:31.226Z UNUSUAL plugin-bookkeeper: topic 'utxo_deposit' is not a known notification topic
2024-08-27T15:31:31.226Z UNUSUAL plugin-bookkeeper: topic 'utxo_spend' is not a known notification topic
2024-08-27T15:31:31.226Z DEBUG   lightningd: io_break: check_plugins_manifests
2024-08-27T15:31:31.226Z DEBUG   lightningd: io_loop_with_timers: plugins_init
...

To me it seems lightningd is not finding the path to the builtin plugins in your setup.

[nakoshi-satamoto]

so what is the path to bcli then @Lagrang3 ? I never had to declare the path to that in the earlier versions.

[Lagrang3]

I am looking into the code, it seems that lightningd searches for the builtin plugins relative to his own path ../plugins.
Do you use make install?

[nakoshi-satamoto]

I found it

corelightning-24.05/usr/libexec/c-lightning/plugins/bcli

I'll test today when I get a chance with this path declared as a plugin in the config

[nakoshi-satamoto]

I am looking into the code, it seems that lightningd searches for the builtin plugins relative to his own path ../plugins. Do you use make install?

I am just using the signed binaries. I did not compile.

[grubles]

Couldn't you symlink the binary to somewhere in your PATH?

[nakoshi-satamoto]

Declaring the path of the plugin does not work either, I get this
error starting plugin '/home/satoshi/clightning/corelightning-v24.08rc3/usr/libexec/c-lightning/plugins': opening pipe: Permission denied

[nakoshi-satamoto]

Couldn't you symlink the binary to somewhere in your PATH?

And what would be the proper way to do that? This seems like a hack work around. Would users of core lightning be expected to do the same?