--- Log opened Sat Oct 27 00:00:48 2018
00:11 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer]
00:12 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning
01:11 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...]
01:20 -!- spinza [~spin@155.93.246.187] has joined #c-lightning
02:09 -!- ken2812221 [~ken281222@110.50.135.178] has joined #c-lightning
03:24 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...]
03:38 -!- spinza [~spin@155.93.246.187] has joined #c-lightning
04:19 -!- booyah [~bb@193.25.1.157] has quit [Read error: Connection reset by peer]
04:20 -!- booyah [~bb@193.25.1.157] has joined #c-lightning
05:11 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...]
05:18 -!- spinza [~spin@155.93.246.187] has joined #c-lightning
07:18 < molz> $ lightning-cli close 0270685ca81a8e4d4d01beec5781f4cc924684072ae52c507f8ebe9daf0caaab7b{ "code" : -1, "message" : "Channel is in state AWAITING_UNILATERAL" }
07:19 < molz> for the channel with this node it says       "connected": true,  BUT...
07:19 < molz>           "status": [
07:19 < molz>             "AWAITING_UNILATERAL:Attempting to reconnect"
07:23 < molz> oh now my node crashed
07:32 -!- queip [~queip@unaffiliated/rezurus] has joined #c-lightning
07:42 < molz> crash.log https://paste.ee/p/ULBQl#599P2pI6R8t3e6E2FrehVd7Zp3Reko35
08:08 < molz> ahhhhh... i think i have another bug report for rusty :D
08:09 < molz> it crashed again after i updated the node to v0.6.2, not sure if this version has anything new/different from 0.6.2rc1
08:16 < molz> haha..and this related to roasbeef's faucet node, my c-lightning node crashed when i tried to close the channel with the lnd faucet node.. fun :D
10:45 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 272 seconds]
11:01 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning
12:08 < molz> ok i have another node running the older version, also crashed when i tried to close a similar channel
12:15 -!- belcher_ [~belcher@unaffiliated/belcher] has quit [Read error: Connection reset by peer]
12:15 -!- belcher_ [~belcher@unaffiliated/belcher] has joined #c-lightning
12:37 -!- deusexbeer [~deusexbee@080-250-076-017-dynamic-pool-adsl.wbt.ru] has joined #c-lightning
12:53 -!- michaelsdunn1 [~michaelsd@unaffiliated/michaelsdunn1] has joined #c-lightning
14:03 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 252 seconds]
14:26 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning
15:21 -!- michaelsdunn1 [~michaelsd@unaffiliated/michaelsdunn1] has quit [Quit: My MacBook Air has gone to sleep. ZZZzzz…]
15:32 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...]
15:58 -!- spinza [~spin@155.93.246.187] has joined #c-lightning
16:00 -!- michaelsdunn1 [~michaelsd@unaffiliated/michaelsdunn1] has joined #c-lightning
16:08 -!- michaelsdunn1 [~michaelsd@unaffiliated/michaelsdunn1] has quit [Quit: My MacBook Air has gone to sleep. ZZZzzz…]
19:03 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...]
19:08 -!- spinza [~spin@155.93.246.187] has joined #c-lightning
19:48 < rusty> molz: yay!
19:50 < rusty> molz: yep, found it!
19:50 < molz> hi rusty :D
19:51 < molz> what did you find?
19:51 < rusty> The cause of the bug.
19:51 < rusty> molz: may I file a bug for you?
19:51 < molz> oh wow.. that fast
19:51 < molz> sure please
19:51 < molz> what's the cause?
19:51 < molz> i was about to submit an issue but now i don't have to! :D
19:52 < molz> if you need more logs, i have them
19:52 < rusty> molz: do you have a GH acct I should reference?
19:53 < molz> lol.. my name is just "molxyz" on GH
19:55 < molz> rusty, i was looking thru the issues to see if anyone has had the same or similar case and found this:  https://github.com/ElementsProject/lightning/issues/2042
19:55 < molz> not quite the same but the crash looks familiar
19:56 < rusty> molz: no, that one is bitcoin-cli *Crashed* and lightningd got upset about it.  That's... not optimal, but we're in trouble at this point anyway.
19:57 < rusty> molz: https://github.com/ElementsProject/lightning/pull/2057
19:57 < molz> ah ok.. i was looking at "FATAL SIGNAL 6 "
19:58 < molz> ah i see... 
20:00 < molz> at first i thought maybe my system was out of memory, then i tested the second node on another server, happened that it also had a similar channel and i tried to close it then it crashed so i knew it must not be because of memory
21:09 < molz> rusty, so i got the fix compiled, no more crash but i can't close the channel
21:09 < molz> $ lightning-cli close 0270685ca81a8e4d4d01beec5781f4cc924684072ae52c507f8ebe9daf0caaab7b true
21:09 < molz> { "code" : -1, "message" : "Channel is in state AWAITING_UNILATERAL" }
21:10 < rusty> molz: yeah, it's already closing...
21:10 < molz> oh
21:10 < rusty> molz: well, your side has presumably broadcast the last commitment tx.
21:11 < molz> rusty, but it doesn't say it's closing
21:11 < molz>           "status": [
21:11 < molz>             "AWAITING_UNILATERAL:Attempting to reconnect"
21:14 < rusty> molz: perhaps we should change "AWAITING_UNILATERAL" to "STARTED_UNILATERAL_CLOSE"? But it should have broadcast a tx; see 'scratch_txid' for the txid it would have broadcast...
21:14 < rusty> s/change/rename/
21:22 < molz> rusty, guess what both txids aren't on any explorer
21:22 < molz> "scratch_txid": "ed3e68ada91c49564a4a1df02b92faa5ce90e39bc6f7c96472eb7a399de279f6",
21:22 < molz> "funding_txid": "49200a046ffaf9cc45bec9745d464666f248ae020e1ed457512f579ce91c8444",
21:22 < molz> both of them ^^ don't exist  :D
21:23 < rusty> molz: hmm, not in my mempool either.  How did you do that?
21:23 < rusty> molz: testnet or mainnet?
21:24 < molz> testnet
21:24 < molz> i have no idea how it happened but here's the channel info:  https://paste.ee/p/Vuys5#sPO5m2K2BpScPDoEn3g9L5beh3zm61f9
21:27 < rusty> molz: hmm, that's super-weird.
21:28 < rusty> molz: 'bitcoin-cli -testnet getrawtransaction 49200a046ffaf9cc45bec9745d464666f248ae020e1ed457512f579ce91c8444' ?
21:28 < rusty> molz: did you fund this channel, or did the other side?
21:28 < molz> i funded this channel
21:30 < molz> hm i can't get the raw tx of this txid
21:39 < rusty> molz: OK, that implies your bitcoind rejected the funding tx.  Which *should* cause an internal error...
21:40 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-cferpsjslngrfmjj] has left #c-lightning []
21:41 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-cferpsjslngrfmjj] has joined #c-lightning
21:47 < molz> rusty, that txid is not in debug.log or crash logs 
21:52 < rusty> molz: have you restarted your bitcoind between fundchannel for this channel and now?
21:52 < molz> i don't remember but i probably have
21:53 < molz> that node pubkey is in a crash log
21:53 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer]
21:53 < molz> +2.053380850 lightningd(18475):DEBUG: lightning_openingd-0270685ca81a8e4d4d01beec5781f4cc924684072ae52c507f8ebe9daf0caaab7b chan #490: peer_out WIRE_ERROR
21:53 < molz> +2.054048282 lightning_hsmd(18483):DEBUG: Client: Received message 18 from client
21:53 < molz> +2.054170875 lightningd(18475):DEBUG: lightning_openingd-0270685ca81a8e4d4d01beec5781f4cc924684072ae52c507f8ebe9daf0caaab7b chan #490: Handed peer, entering loop
21:54 < rusty> Hmm, could be it accepted it then it somehow got lost from the mempool... if we crash between then it might cause an issue.  Let me check...
21:54 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning
21:56 < molz> it's also in the debug.log
21:56 < molz> 2018-10-27T14:56:46.295Z lightningd(18475): 0270685ca81a8e4d4d01beec5781f4cc924684072ae52c507f8ebe9daf0caaab7b chan #15: Peer has reconnected, state AWAITING_UNILATERAL
21:56 < molz> 2018-10-27T14:56:46.297Z lightningd(18475): lightning_openingd-0270685ca81a8e4d4d01beec5781f4cc924684072ae52c507f8ebe9daf0caaab7b chan #490: pid 18565, msgfd 25
21:57 < molz> ok rusty, i also have a lnd node on this server, and so both lnd and c-lightning nodes share a same bitcoind, could this be the problem?
21:57 < molz> in the past we had this problem when two lnd nodes sharing one bitcoind node
22:01 < rusty> molz: shouldn't be, at all.  Let me check what happens to our UTXOs in this situation.  Ideally, we should consider them "unspent" if the channel closes, or probably re-spend them to make sure the funding never goes through.  But I don't think we do :( 
22:04 < molz> rusty, but what i don't get is it doesn't seem the tx happend at all
22:05 < molz> i mean the funding tx
22:08 < rusty> molz: Ah, wait.  If bitcoind *did* reject our funding tx, we'll actually end up exactly in this state.  Trying to unilateral close.  Hm.  Got 'Peer permanent failure ' anywhere in your logs?
22:08 < molz> let me check
22:11 < molz> rusty, nope, not in debug.log, not in two crash.logs i have
22:14 < rusty> Hmm, it would have happened back when you opened this channel.  I guess your logs don't go that far back?
22:18 < molz> yea i didn't have a log when i opened the channel
22:18 < molz> i just started the debug.log after the crash
22:19 < molz> i think i had a similar channel before but i could force close it 
22:20 < rusty> Hmm, well that logs at level "unusual" so it would be printed out in any logs.  Hmm...
22:21 < molz> now i just closed the other few channels so i can see 'Peer permanent failure ' on those channel but not on this particular channel
22:25 < molz> what does this mean:
22:25 < molz> 2018-10-28T04:02:10.106Z lightning_connectd(26901): Connect OUT to 0270685ca81a8e4d4d01beec5781f4cc924684072ae52c507f8ebe9daf0caaab7b
22:25 < molz> 2018-10-28T04:02:10.106Z lightning_connectd(26901): peer_out WIRE_INIT
22:28 < rusty> molz: it means we connected and sent our INIT message (the first thing we do on connect)
22:31 < molz> rusty, it seems to have trouble connecting to that node for some reason
22:31 < molz> i just checked, the node is online
--- Log closed Sun Oct 28 00:00:49 2018