--- Day changed Sun Jun 10 2018 00:17 -!- grafcaps [~haroldbr@50.90.83.229] has joined #c-lightning 00:21 -!- grafcaps [~haroldbr@50.90.83.229] has quit [Ping timeout: 264 seconds] 00:51 -!- simlay [~simlay@gateway/tor-sasl/simlay] has quit [Ping timeout: 250 seconds] 00:53 -!- simlay [~simlay@gateway/tor-sasl/simlay] has joined #c-lightning 01:01 < windsok> I have a channel that seems to be stuck in CHANNELD_SHUTTING_DOWN state, is there a way to force broadcasting a tx to get my satoshis out of that channel? 01:02 < windsok> this is a very old channel from Jan 01:13 < windsok> ah, close with force=true seems to have done it 01:14 < windsok> but now I see the problem. broadcast error 16: bad-txns-vout-empty 01:14 < windsok> I remember now https://github.com/ElementsProject/lightning/issues/632 01:16 < windsok> wondering if there any any way to spend this UTXO, even if all the satoshis go to fees 01:46 -!- simlay [~simlay@gateway/tor-sasl/simlay] has quit [Quit: WeeChat 2.1] 01:53 -!- simlay [~simlay@gateway/tor-sasl/simlay] has joined #c-lightning 02:08 -!- simlay [~simlay@gateway/tor-sasl/simlay] has quit [Remote host closed the connection] 02:11 -!- simlay [~simlay@gateway/tor-sasl/simlay] has joined #c-lightning 02:25 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer] 02:27 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning 03:51 -!- cryptapus [~cryptapus@unaffiliated/cryptapus] has quit [Read error: Connection reset by peer] 04:39 -!- grafcaps [~haroldbr@50.90.83.229] has joined #c-lightning 04:44 -!- grafcaps [~haroldbr@50.90.83.229] has quit [Ping timeout: 276 seconds] 05:04 -!- ebx [~ebx@unaffiliated/ebex] has joined #c-lightning 05:22 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer] 05:23 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning 05:27 -!- tiagotrs [~user@p5DC46B79.dip0.t-ipconnect.de] has joined #c-lightning 05:27 -!- tiagotrs [~user@p5DC46B79.dip0.t-ipconnect.de] has quit [Changing host] 05:27 -!- tiagotrs [~user@unaffiliated/tiagotrs] has joined #c-lightning 06:19 < ctrlbreak> So... I've tried to ask this previously, but never really received an answer. 06:19 < ctrlbreak> I have multiple channels in this state: 06:19 < ctrlbreak> "id": "03f6489657028db5316fc920b92122805cabd87e937a6adb33661d4b44dcb6dc19", 06:19 < ctrlbreak> "connected": false, 06:19 < ctrlbreak> "channels": [ 06:19 < ctrlbreak> { 06:19 < ctrlbreak> "state": "CHANNELD_SHUTTING_DOWN", 06:19 < ctrlbreak> ... 06:19 < ctrlbreak> "status": [ 06:19 < ctrlbreak> "Loaded from database" 06:19 < ctrlbreak> ], 06:20 < ctrlbreak> Never changing. I'm presuming I have to manually remove them via some method at this point? 06:48 < provoostenator> ctrlbreak it might also be worth filing a Github issue for. I assume at some point this either shouldn't be possible or it should not be confusing. 06:52 < provoostenator> I sometimes find it helps to look up the IP address for that node on e.g. the Recksplorer and try to connect. There's also "lightning-cli close [channel id] true" which will do a unilateral close if that hasn't happened already. 06:57 < ctrlbreak> provoostenator: Thanks for the actual response! I actually have attempted that form of close already. Still they persist :-( I've heard that perhaps there's a 'dev switch' that enable some of the older dev-* commands... but I hvaen't looked into it too far yet due to lack of time :/ 07:00 < provoostenator> ./configure --enable-developer followed by make, should give you all the footguns you need 07:10 < ctrlbreak> lol... thanks. I don't mind footguns at this point. My next step is to back-burner this c-lightning VM and move to LND :-S So this is a last ditch effort to save this instance as it may still be a little bit beyond my grasp :-( 07:27 -!- tiagotrs [~user@unaffiliated/tiagotrs] has quit [Ping timeout: 264 seconds] 07:28 < molz> ctrlbreak, haha :D 07:28 < molz> i think every impl is having some issue 07:30 < buZz> ctrlbreak: actually those channels should close by themselves after a while? 07:31 < buZz> might be a longer while then you think , maybe 2-3 days 08:15 -!- grafcaps [~haroldbr@50.90.83.229] has joined #c-lightning 08:20 -!- grafcaps [~haroldbr@50.90.83.229] has quit [Ping timeout: 248 seconds] 08:34 -!- grafcaps [~haroldbr@50.90.83.229] has joined #c-lightning 08:37 -!- cryptapus [~cryptapus@jupiter.osmus.org] has joined #c-lightning 08:37 -!- cryptapus [~cryptapus@jupiter.osmus.org] has quit [Changing host] 08:37 -!- cryptapus [~cryptapus@unaffiliated/cryptapus] has joined #c-lightning 09:18 -!- tiagotrs [~user@unaffiliated/tiagotrs] has joined #c-lightning 09:33 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer] 09:35 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning 09:48 -!- tiagotrs [~user@unaffiliated/tiagotrs] has quit [Ping timeout: 268 seconds] 10:22 -!- tiagotrs [~user@p5DC47005.dip0.t-ipconnect.de] has joined #c-lightning 10:22 -!- tiagotrs [~user@p5DC47005.dip0.t-ipconnect.de] has quit [Changing host] 10:22 -!- tiagotrs [~user@unaffiliated/tiagotrs] has joined #c-lightning 11:02 -!- CubicEarths [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has joined #c-lightning 11:07 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer] 11:09 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning 11:12 -!- antanst [~antanst@62.169.219.213] has quit [Quit: ZNC 1.6.3+deb1 - http://znc.in] 11:16 -!- antanst [~antanst@62.169.219.213] has joined #c-lightning 11:21 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 276 seconds] 11:27 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning 11:56 -!- simlay [~simlay@gateway/tor-sasl/simlay] has quit [Quit: WeeChat 2.1] 14:28 -!- simlay [~simlay@gateway/tor-sasl/simlay] has joined #c-lightning 14:31 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 256 seconds] 14:58 -!- tiagotrs [~user@unaffiliated/tiagotrs] has quit [Ping timeout: 260 seconds] 16:20 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning 17:38 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 265 seconds] 17:56 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning 18:22 -!- booyah [~bb@193.25.1.157] has quit [Remote host closed the connection] 19:18 -!- dougsland [~douglas@c-73-234-93-65.hsd1.nh.comcast.net] has joined #c-lightning 19:46 -!- dougsland [~douglas@c-73-234-93-65.hsd1.nh.comcast.net] has quit [Ping timeout: 256 seconds] 20:03 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 245 seconds] 21:00 -!- ebx [~ebx@unaffiliated/ebex] has quit [Remote host closed the connection] 21:01 -!- grafcaps [~haroldbr@50.90.83.229] has quit [Ping timeout: 240 seconds] 21:06 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning 21:14 -!- grafcaps [~haroldbr@50.90.83.229] has joined #c-lightning 22:21 -!- grafcaps [~haroldbr@50.90.83.229] has quit [Ping timeout: 256 seconds]