--- Day changed Sat Aug 04 2018 00:53 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Ping timeout: 260 seconds] 01:04 -!- RubenSomsen [uid301948@gateway/web/irccloud.com/x-wbbcoczlmbtqfski] has quit [Quit: Connection closed for inactivity] 04:53 -!- ebx [~ebx@unaffiliated/ebex] has joined #c-lightning 06:01 -!- Lightblock_ [uid302821@gateway/web/irccloud.com/x-jqyxhpqzxtydiaci] has joined #c-lightning 06:19 < blockstream_bot> [Parth Choudhary, Blockstream] what is the meaning of `"CHANNELD_AWAITING_LOCKIN:Reconnected, and reestablished.", 06:19 < blockstream_bot> "CHANNELD_AWAITING_LOCKIN:They've confirmed funding, we haven't yet."` 06:19 < blockstream_bot> [Parth Choudhary, Blockstream] I am stuck on this since yesterday on testnet 06:20 < blockstream_bot> [Parth Choudhary, Blockstream] Is there an action needed on my end? 06:21 < molz> Parth, restart your node to see if the update is different? 06:22 < blockstream_bot> [Parth Choudhary, Blockstream] I restarted multiple times, same result. 06:23 < blockstream_bot> [Parth Choudhary, Blockstream] This is the docker instance `shesek/lightning-charge` mentioned in `lightning-charge` 06:40 < molz> maybe something is wrong with the docker? 07:42 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has joined #c-lightning 08:10 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has quit [Ping timeout: 260 seconds] 08:21 -!- RubenSomsen [uid301948@gateway/web/irccloud.com/x-wbhyzciuqhddqevt] has joined #c-lightning 08:41 -!- Lightblock_ [uid302821@gateway/web/irccloud.com/x-jqyxhpqzxtydiaci] has quit [Quit: Connection closed for inactivity] 09:22 < blockstream_bot> [Christian Decker, Blockstream] Parth: is your bitcoind synced with the network? Us not announcing usually means that we haven't seen enough confirmations yet, which happens if we are still syncing 09:23 < blockstream_bot> [Christian Decker, Blockstream] You can check the blockheight of c-lightning with `getinfo` 09:24 < blockstream_bot> [Christian Decker, Blockstream] And the peer of course needs to be connected 09:50 < blockstream_bot> [Parth Choudhary, Blockstream] yes just checked, it is not matching the blockheight response in `getblockchaininfo`. But why is it so slow? Testnet datadir size still 16GB for me, I have a good connection, too many read/writes on disk? 10:28 -!- mdrollette [~mdrollett@feynman.drollette.com] has quit [Ping timeout: 256 seconds] 10:39 -!- keymone [~keymone@ip1f13761c.dynamic.kabel-deutschland.de] has quit [Ping timeout: 256 seconds] 11:35 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer] 11:36 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning 12:59 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer] 13:00 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning 14:04 -!- CubicEarth [~CubicEart@c-73-181-185-197.hsd1.wa.comcast.net] has quit [Ping timeout: 256 seconds] 14:06 -!- CubicEarth [~CubicEart@c-73-181-185-197.hsd1.wa.comcast.net] has joined #c-lightning 14:57 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer] 14:58 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning 15:46 -!- qubenix [~qubenix@213.184.122.35] has quit [Remote host closed the connection] 17:10 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning 17:14 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 260 seconds] 17:16 -!- justan0theruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning 17:29 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Ping timeout: 264 seconds] 18:20 -!- qubenix [~qubenix@185.213.152.162] has joined #c-lightning 20:21 -!- cncr04s [~cncr04s@unaffiliated/cncr04s] has quit [Ping timeout: 260 seconds] 20:24 -!- cncr04s [~cncr04s@unaffiliated/cncr04s] has joined #c-lightning 21:34 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning 23:01 -!- ebx [~ebx@unaffiliated/ebex] has quit [Remote host closed the connection]