--- Log opened Tue Sep 05 00:00:13 2023
00:20 -!- vincenzopalazzo [~vincenzop@146.70.134.103] has quit [Quit: Leaving]
01:32 -!- NewMan1992 [~ident@165.sub-174-215-176.myvzw.com] has joined #c-lightning
02:14 -!- NewMan1992 [~ident@165.sub-174-215-176.myvzw.com] has quit [Quit: Quit]
05:34 -!- bitdex_ [~bitdex@gateway/tor-sasl/bitdex] has quit [Quit: = ""]
05:50 -!- jonatack3 [~jonatack@user/jonatack] has quit [Read error: Connection reset by peer]
05:50 -!- jonatack3 [~jonatack@user/jonatack] has joined #c-lightning
06:22 -!- jespada [~jespada@cpc121308-nmal25-2-0-cust15.19-2.cable.virginm.net] has quit [Read error: Connection reset by peer]
06:41 -!- jespada [~jespada@nmal-25-b2-v4wan-166098-cust2758.vm24.cable.virginm.net] has joined #c-lightning
06:47 -!- jespada [~jespada@nmal-25-b2-v4wan-166098-cust2758.vm24.cable.virginm.net] has quit [Ping timeout: 245 seconds]
06:52 -!- jespada [~jespada@cpc121308-nmal25-2-0-cust15.19-2.cable.virginm.net] has joined #c-lightning
10:22 -!- vincenzopalazzo [~vincenzop@146.70.126.231] has joined #c-lightning
11:13 -!- RubenSomsen [sid301948@user/rubensomsen] has quit [Ping timeout: 240 seconds]
11:17 -!- RubenSomsen [sid301948@user/rubensomsen] has joined #c-lightning
11:58 -!- btcGuest21 [~btcGuest2@76.176.228.42] has joined #c-lightning
11:58 < btcGuest21> Hello all
11:59 < btcGuest21> I have compiled lightningd from a raspberry pi
11:59 < btcGuest21> and everything looks fine
11:59 < btcGuest21> until I run it
12:02 < btcGuest21> It seems to run ok without proxy settings, but as soon as I enable the proxy tor settings it crashes
12:04 < btcGuest21> lightning_connectd: Connecting stream socket to Tor service (version v23.08)
12:04 < btcGuest21> 0x556d6564c3 send_backtrace
12:04 < btcGuest21>  common/daemon.c:33
12:04 < btcGuest21> 0x556d65f2ef status_failed
12:04 < btcGuest21>  common/status.c:221
12:04 < btcGuest21> 0x556d6523ab tor_fixed_service
12:04 < btcGuest21>  connectd/tor_autoservice.c:322
12:04 < btcGuest21> 0x556d6499e7 setup_listeners
12:04 < btcGuest21>  connectd/connectd.c:1369
12:04 < btcGuest21> 0x556d649ca7 connect_init
12:04 < btcGuest21>  connectd/connectd.c:1466
12:04 < btcGuest21> 0x556d64bc9f recv_req
12:04 < btcGuest21>  connectd/connectd.c:2044
12:04 < btcGuest21> 0x556d656723 handle_read
12:04 < btcGuest21>  common/daemon_conn.c:35
12:04 < btcGuest21> 0x556d6ebf2f next_plan
12:04 < btcGuest21>  ccan/ccan/io/io.c:59
12:04 < btcGuest21> 0x556d6ec507 do_plan
12:34 < vincenzopalazzo> mh
12:34 < vincenzopalazzo> strange
12:34 < vincenzopalazzo> can you open a issue for it?
12:36 < btcGuest21> a few seconds ago I was able to fi it
12:36 < btcGuest21> well, not the actual crash, but the config
12:37 < vincenzopalazzo> from the crash that you post looks like that core lightning crash while running some tor code
12:37 < vincenzopalazzo> but without a better report I can not tell
12:38 < btcGuest21> I had the default port for 'addr='.. why change it right? well when using statictor it requires us to change the port to the Tor Control Port 9051 as follows:
12:38 < btcGuest21> addr=statictor:127.0.0.1:9051
12:38 < btcGuest21> adding examples to the config-example will greatly improve the experience for new users :D
12:41 < btcGuest21> How can I start lightningd without having to type the hsm_secret? I want to set it up as a service
12:51 < vincenzopalazzo> Do you read this https://docs.corelightning.org/reference/lightningd-config ? 
12:52 -!- btcGuest21 [~btcGuest2@76.176.228.42] has quit [Quit: Client closed]
13:13 -!- brimonk_ [~brian@142.93.196.94] has quit [Server closed connection]
13:13 -!- brimonk [~brian@142.93.196.94] has joined #c-lightning
13:18 -!- btcGuest21 [~btcGuest2@76.176.228.42] has joined #c-lightning
13:19 < btcGuest21> do I do `lightningd --hsm_secret=my_secret` ?
13:20 < btcGuest21>   I don't think that's an option tho... so once there's a password I basically can't configure it as an auto start service?
13:23 < btcGuest21> ahm found the answer here: https://docs.corelightning.org/docs/securing-keys
13:25 < btcGuest21> wait... it still doesn't say how I can send the password
13:31 -!- vincenzopalazzo [~vincenzop@146.70.126.231] has quit [Ping timeout: 245 seconds]
13:37 < btcGuest21> I guess there's no way 🤷🏻‍♂️
13:42 < btcGuest21> it's alright tho
13:51 -!- btcGuest21 [~btcGuest2@76.176.228.42] has quit [Quit: Client closed]
14:34 -!- btcGuest21 [~btcGuest2@76.176.228.42] has joined #c-lightning
15:10 -!- RubenSomsen [sid301948@user/rubensomsen] has quit [Ping timeout: 240 seconds]
15:10 -!- RubenSomsen [sid301948@user/rubensomsen] has joined #c-lightning
17:29 -!- Netsplit *.net <-> *.split quits: sgiath-, opsec_x122
17:30 -!- Netsplit over, joins: opsec_x122
17:30 -!- btcGuest21 [~btcGuest2@76.176.228.42] has quit [Quit: Client closed]
17:30 -!- sgiath [~sgiath@2a02:25b0:aaaa:aaaa:a3c3:ed4b:6b06:0] has joined #c-lightning
17:38 -!- jespada [~jespada@cpc121308-nmal25-2-0-cust15.19-2.cable.virginm.net] has quit [Ping timeout: 245 seconds]
17:57 -!- jespada [~jespada@cpc121308-nmal25-2-0-cust15.19-2.cable.virginm.net] has joined #c-lightning
19:19 -!- btcGuest21 [~btcGuest2@76.176.228.42] has joined #c-lightning
19:35 -!- btcGuest21 [~btcGuest2@76.176.228.42] has quit [Quit: Client closed]
21:32 -!- btcGuest21 [~btcGuest2@76.176.228.42] has joined #c-lightning
21:32 < btcGuest21> Hello all!
21:33 < btcGuest21> I have setup the c-lightning node with the default hsm_secret, and it was running fine
21:33 < btcGuest21> now I decided to create an hsm_secret using my own bip39
21:34 < btcGuest21> when entering the password, it continues to throw the next message: lightningd: Wallet sanity check failed.
21:34 < btcGuest21> Any ideas on how to fix this?
21:54 -!- btcGuest21 [~btcGuest2@76.176.228.42] has quit [Quit: Client closed]
22:00 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning
22:09 -!- btcGuest21 [~btcGuest2@76.176.228.42] has joined #c-lightning
22:09 < btcGuest21> nvm i was able to figure it out
22:14 -!- btcGuest21 [~btcGuest2@76.176.228.42] has quit [Quit: Client closed]
22:40 -!- opsec_x122 [~opsec_x12@44.25.143.46] has quit [Remote host closed the connection]
22:42 -!- opsec_x12 [~opsec_x12@44.25.143.46] has joined #c-lightning
22:48 -!- opsec_x122 [~opsec_x12@44.25.143.46] has joined #c-lightning
22:48 -!- opsec_x12 [~opsec_x12@44.25.143.46] has quit [Remote host closed the connection]
--- Log closed Wed Sep 06 00:00:15 2023