--- Log opened Fri Jan 29 00:00:29 2021
00:36 -!- liberliver [~Thunderbi@144.49.211.130.bc.googleusercontent.com] has joined #c-lightning
01:14 -!- az0re [~az0re@gateway/tor-sasl/az0re] has joined #c-lightning
01:14 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-qtzfkbumkrmirmay] has left #c-lightning []
01:14 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-qtzfkbumkrmirmay] has joined #c-lightning
02:26 -!- vasild_ [~vd@gateway/tor-sasl/vasild] has joined #c-lightning
02:26 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Disconnected by services]
02:26 -!- vasild_ is now known as vasild
03:17 -!- m-schmoock [~will@schmoock.net] has joined #c-lightning
04:42 -!- zmnscpxj [~zmnscpxj@gateway/tor-sasl/zmnscpxj] has joined #c-lightning
05:00 -!- Netsplit *.net <-> *.split quits: midnight
05:01 -!- Netsplit over, joins: midnight
05:01 -!- Netsplit *.net <-> *.split quits: fiatjaf2
05:01 -!- midnight [~midnight@unaffiliated/midnightmagic] has quit [Max SendQ exceeded]
05:01 -!- Netsplit over, joins: fiatjaf2
05:03 -!- midnight [~midnight@unaffiliated/midnightmagic] has joined #c-lightning
05:03 -!- Jackielove4u [uid43977@gateway/web/irccloud.com/x-sulwoxgyopxoqgnl] has quit [Ping timeout: 246 seconds]
05:05 -!- Jackielove4u [uid43977@gateway/web/irccloud.com/x-fbrpvvksdhpwfpai] has joined #c-lightning
05:10 < m-schmoock> cdecker: how can I restart a single failed job? https://github.com/ElementsProject/lightning/runs/1791226581?check_suite_focus=true 
05:10 <@cdecker> You can't start a single job, Github hasn't added that feature
05:11 <@cdecker> Working on making the tests more stable and fail faster in case we run into issues atm
05:11 < m-schmoock> uuuhhh such a basic feature not implemented. LOL ^^
05:11 < m-schmoock> do they accept BTC if the implement it fasteR?
05:12 <@cdecker> Yep, it's pretty basic, but then again we shouldn't have flaky tests ... ever...
05:13 <@cdecker> Pretty close to assigning tests to contributors by their authorship, then open issues and assign them automatically when one of theirs goes bad
05:13 < m-schmoock> :D
05:13 < m-schmoock> sure that will give me some tickets
05:16 <@cdecker> Don't think you'd be impacted as much, it's mostly some of the involved tests that are missing some sync-points or make implicit assumptions about timing, and in those cases it's best to ping the author since they might have the most context to fix it as well
05:17  * m-schmoock is syncing bitcoind on a raspi4 ... 100Hrs to go :]
05:17 < m-schmoock> its a lot faster than I thought.
05:37 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Ping timeout: 268 seconds]
05:39 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning
05:39 -!- zmnscpxj [~zmnscpxj@gateway/tor-sasl/zmnscpxj] has quit [Remote host closed the connection]
05:40 -!- zmnscpxj [~zmnscpxj@gateway/tor-sasl/zmnscpxj] has joined #c-lightning
05:44 -!- belcher_ is now known as belcher
06:01 < nibbier> so if I open a channel with fee < min relay fee.... my lightningd thinks it is setting up a channel, but no one knows about it. how would I resolve this?
06:14 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has joined #c-lightning
06:21 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Ping timeout: 268 seconds]
06:53 <@cdecker> You can rebroadcast the transaction once the mempool fee is lower. If that is unlikely (lower than the min-relay-fee, or loads of congestion), you can unreserve the UTXO and `dev-rescan-outputs` so they're available again, and then move the funds to a new address so the original tx is discarded even if the fee eventually comes down
07:00 -!- liberliver [~Thunderbi@144.49.211.130.bc.googleusercontent.com] has quit [Quit: liberliver]
07:43 -!- ctrlbreak_MAD [~ctrlbreak@159.2.165.130] has joined #c-lightning
07:46 -!- cltrbreak_MAD2 [~ctrlbreak@159.2.165.130] has quit [Ping timeout: 264 seconds]
07:56 -!- jonatack [jon@gateway/vpn/airvpn/jonatack] has quit [Ping timeout: 260 seconds]
08:05 < nibbier> cdecker: guess I'll try to unreserve then... was not able to see the full TX in the logs, so wouldn't know how to rebreadcast, and no indication of lightningd rebroadcasting on restart eg (had similar problems with lnd a few month back and was able to copy the full TX from the logs at least)
08:05 < nibbier> thanks
08:27 -!- kexkey [~kexkey@static-198-54-132-88.cust.tzulo.com] has joined #c-lightning
08:45 -!- kexkey [~kexkey@static-198-54-132-88.cust.tzulo.com] has quit [Ping timeout: 246 seconds]
09:14 -!- jonatack [jon@gateway/vpn/airvpn/jonatack] has joined #c-lightning
09:19 -!- ebmk [~ebmk@209.171.202.122] has joined #c-lightning
09:25 < ebmk> Could someone point me in the right direction for solbing this 'lightning-cli: Connecting to 'lightning-rpc': Connection refused' error. This is from any lightning-cli commands.
09:26 < ebmk> I'm just learning. I have my bitcoin node running perfectly but c-lightning is giving me headaches.
09:29 <@cdecker> That is usually a problem with c-lightning not running, can you check with `ps aux | grep lightningd` if something shows up?
09:30 < ebmk> ebmk     27407  0.0  0.0   6208   828 pts/1    S+   12:30   0:00 grep lightningd
09:30 < ebmk> is what returns
09:36 <@cdecker> Nope, not runnng then, you need to start it before you can talk to it
09:38 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-qtzfkbumkrmirmay] has left #c-lightning []
09:39 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-qtzfkbumkrmirmay] has joined #c-lightning
09:42 < ebmk> Okay. So when I type 'lightningd --network=bitcoin --log-level=debug' I get what looks like a functioning server but no access to typing in commands. So I drop the '--log-level=debug' and I get this:
09:42 < ebmk> 2021-01-29T17:40:31.787Z INFO    lightningd: --------------------------------------------------
09:42 < ebmk> 2021-01-29T17:40:31.787Z INFO    lightningd: Server started with public key 039e391f04ab46f972ff2b5174f0b8d2961517ffd6737e77c53bc122d4f80baa90, alias CHILLYWALK (color #039e39) and lightningd v0.9.3-50-ga5f16ab
09:42 < ebmk> 2021-01-29T17:40:31.789Z INFO    plugin-fetchinvoice: Killing plugin: offers not enabled in config
09:42 < ebmk> 2021-01-29T17:40:31.789Z INFO    plugin-offers: Killing plugin: offers not enabled in config
09:42 < ebmk> something tells me I need to get into a config file of sorts
09:42 < ebmk> maybe download some depended packages
09:42 <@cdecker> No this should be fine, what are you doing next?
09:43 <@cdecker> Does `lightningd` stop at some point?
09:43 < ebmk> At this point the 'ebmk@server $:' thing disappears
09:44 < ebmk> so no commands may be inputted
09:44 < ebmk> unless I ctrl-c, but that's a hard exit right?
09:45 < ebmk> oh im a dummy
09:45 < ebmk> lighting-cli seems to work
09:46 < ebmk> thanks for the help, I'm going to refer to the git so as not to bother you anymore :)
09:53 -!- ebmk [~ebmk@209.171.202.122] has quit [Remote host closed the connection]
10:00 -!- ksedgwic [~ksedgwic@192-184-130-48.fiber.dynamic.sonic.net] has quit [Ping timeout: 256 seconds]
10:02 <@cdecker> No problem at all, yes Ctrl-C would terminate lightningd. You can start it in the background with `--daemon`, but I usually prefer having a second shell open and still be able to see the logs
10:14 < nibbier> cdecker: the only "unreserve" I find is "unreserveinputs" and this requires a psbt as an argument. as I see it my tx is not a psbt, right? I'm currently running "fundchannel_cancel" with the peer having the stuck channel establishment but doubt this will help because "inflight" most likely means the node chatter and not the bitcoin tx being "in flight"
10:18 -!- jb55 [~jb55@gateway/tor-sasl/jb55] has quit [Ping timeout: 268 seconds]
10:19 -!- jb55 [~jb55@gateway/tor-sasl/jb55] has joined #c-lightning
10:42 -!- EndFiat [EndFiat@gateway/vpn/mullvad/endfiat] has quit [Ping timeout: 256 seconds]
10:43 -!- EndFiat [EndFiat@gateway/vpn/mullvad/endfiat] has joined #c-lightning
10:48 < nibbier> also: how would I re-broadcast the TX if I decided to go this route?
13:09 -!- belcher_ [~belcher@unaffiliated/belcher] has joined #c-lightning
13:12 -!- belcher [~belcher@unaffiliated/belcher] has quit [Ping timeout: 264 seconds]
13:26 -!- belcher_ is now known as belcher
14:06 -!- k3tan [~pi@gateway/tor-sasl/k3tan] has quit [Remote host closed the connection]
14:07 -!- k3tan [~pi@gateway/tor-sasl/k3tan] has joined #c-lightning
14:26 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Disconnected by services]
14:26 -!- vasild_ [~vd@gateway/tor-sasl/vasild] has joined #c-lightning
14:26 -!- vasild_ is now known as vasild
14:30 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Remote host closed the connection]
14:31 -!- vasild [~vd@gateway/tor-sasl/vasild] has joined #c-lightning
14:40 -!- zmnscpxj [~zmnscpxj@gateway/tor-sasl/zmnscpxj] has quit [Remote host closed the connection]
14:42 -!- zmnscpxj [~zmnscpxj@gateway/tor-sasl/zmnscpxj] has joined #c-lightning
16:33 -!- belcher_ [~belcher@unaffiliated/belcher] has joined #c-lightning
16:34 -!- belcher [~belcher@unaffiliated/belcher] has quit [Ping timeout: 260 seconds]
16:38 -!- belcher_ is now known as belcher
17:51 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-qtzfkbumkrmirmay] has left #c-lightning []
17:51 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-qtzfkbumkrmirmay] has joined #c-lightning
18:32 -!- EndFiat [EndFiat@gateway/vpn/mullvad/endfiat] has quit [Ping timeout: 265 seconds]
19:43 -!- EndFiat [EndFiat@gateway/vpn/mullvad/endfiat] has joined #c-lightning
20:02 -!- az0re [~az0re@gateway/tor-sasl/az0re] has quit [Remote host closed the connection]
20:02 -!- cryptosoap [~cryptosoa@gateway/tor-sasl/cryptosoap] has quit [Remote host closed the connection]
20:03 -!- cryptosoap [~cryptosoa@gateway/tor-sasl/cryptosoap] has joined #c-lightning
20:04 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning
22:11 -!- sr_gi [~sr_gi@static-6-109-229-77.ipcom.comunitel.net] has quit [Read error: Connection reset by peer]
22:11 -!- sr_gi [~sr_gi@static-6-109-229-77.ipcom.comunitel.net] has joined #c-lightning
--- Log closed Sat Jan 30 00:00:30 2021