depth changed for funding tx, but channel state is still CHANNELD_AWAITING_LOCKIN

[fixone]

this does not look to have the same reason as other contexts where the channel state would remain CHANNELD_AWAITING_LOCKIN
"version" : "v0.5.2-2016-11-21-2448-ge41d565"
listpeers shows

...
{ "id" : "03e14c229048c5e7174ec667ec3b7357b1dba6c069bdf04599b9d77f0d41c6ea84", "connected" : false, "channels" :
			[
				{ "state" : "CHANNELD_AWAITING_LOCKIN", "short_channel_id" : "1290013:342:1", "channel_id" : "6ff5b1e5d04e98aaf1980870de2676b92384008364707bbd9e9af7f344344283", "funding_txid" : "82423444f3f79a9ebd7b706483008423b97626de700898f1aa984ed0e5b1f56f", "msatoshi_to_us" : 950000000, "msatoshi_total" : 950000000, "dust_limit_satoshis" : 546, "max_htlc_value_in_flight_msat" : 18446744073709551615, "channel_reserve_satoshis" : 0, "htlc_minimum_msat" : 0, "their_to_self_delay" : 6, "our_to_self_delay" : 144, "to_self_delay" : 6, "max_accepted_htlcs" : 483, "status" :
					[  ], "in_payments_offered" : 0, "in_msatoshi_offered" : 0, "in_payments_fulfilled" : 0, "in_msatoshi_fulfilled" : 0, "out_payments_offered" : 0, "out_msatoshi_offered" : 0, "out_payments_fulfilled" : 0, "out_msatoshi_fulfilled" : 0 } ] }
....

but log shows that funding goes well, transaction (82423444f3f79a9ebd7b706483008423b97626de700898f1aa984ed0e5b1f56f) is relayed (and currently has 240+ confirms)

2018-04-02T09:41:20.196Z lightningd(10192): Owning output 0 715602 (SEGWIT) txid 82423444f3f79a9ebd7b706483008423b97626de700898f1aa984ed0e5b1f56f
2018-04-02T09:41:20.196Z lightningd(10192):      (tx 82423444f3f79a9ebd7b706483008423b97626de700898f1aa984ed0e5b1f56f)
2018-04-02T09:41:20.196Z lightningd(10192): sendrawtransaction: 0200000000010207fb5c9baa4a04b944022488b76eee80262e0b9665f624faf395280b54e346c20000000000ffffffffbd90683418827c9cc8a83e92b55a53a5a927776f8ed6ba09ff6753c7df92094e0000000000ffffffff0252eb0a00000000001600146f2e9b951864460ce2595d492faa27b407f51eeff07e0e00000000002200204b024c89e225f4d15c310c66ac4bcb8736227d96f65d2cf9ac6bb21c7b8edfce02483045022100d3b0d0ef567db73e105dd1eb3b85a10736146ce97009d48958e76ee7dc974329022014c22d5f6cc22ff6dafd132f1df2f0fc8a0bee5e194fe86b893b68dd8e2d578801210205b14cc82837d83f89df6160d38fa513e6340b5df0a165566ffdc083239fa7b50247304402203197ffb10a8a56200f87f19d172d64e836d5c747add5c53bb3f80bb049d0a60302201d4e0c53cf3343316b0ce5a6c8d6704cf202d9abade5dd3b7c7108319dac8a5701210205b14cc82837d83f89df6160d38fa513e6340b5df0a165566ffdc083239fa7b500000000
2018-04-02T09:41:20.198Z lightningd(10192): Client: Received message 9 from client
2018-04-02T09:41:20.218Z lightningd(10192): lightning_channeld-03e14c229048c5e7174ec667ec3b7357b1dba6c069bdf04599b9d77f0d41c6ea84 chan #116: pid 22289, msgfd 32
2018-04-02T09:41:20.218Z lightningd(10192): 03e14c229048c5e7174ec667ec3b7357b1dba6c069bdf04599b9d77f0d41c6ea84 chan #116: Waiting for funding confirmations
2018-04-02T09:41:20.221Z lightningd(10192): 03e14c229048c5e7174ec667ec3b7357b1dba6c069bdf04599b9d77f0d41c6ea84 chan #116: Ignoring fee limits!
2018-04-02T09:41:20.242Z lightningd(10192):jcon fd 16: Success
2018-04-02T09:41:20.244Z lightning_gossipd(10200): Connected out for 033d45b692e1f3617dd77ab9bad6d070c6a3438467a5beed34c9b5a218b03fc15b
2018-04-02T09:41:20.256Z lightningd(10192): sendrawtx exit 0, gave 82423444f3f79a9ebd7b706483008423b97626de700898f1aa984ed0e5b1f56f?
2018-04-02T09:41:20.308Z lightningd(10192): lightning_channeld-03e14c229048c5e7174ec667ec3b7357b1dba6c069bdf04599b9d77f0d41c6ea84 chan #116: init LOCAL: remote_per_commit = 033b51b4a62c8952d443dcca3771d7f558dfaa71d383558d62222a444f31db7f84, old_remote_per_commit = 033b51b4a62c8952d443dcca3771d7f558dfaa71d383558d62222a444f31db7f84 next_idx_local = 1 next_idx_remote = 1 revocations_received = 0 feerates 2219/2219 (range 1-4294967295)
.....
2018-04-02T09:41:20.196Z lightningd(10192): 	 (tx 82423444f3f79a9ebd7b706483008423b97626de700898f1aa984ed0e5b1f56f)
...
2018-04-02T09:41:20.256Z lightningd(10192): sendrawtx exit 0, gave 82423444f3f79a9ebd7b706483008423b97626de700898f1aa984ed0e5b1f56f?
...
2018-04-02T09:42:20.809Z lightningd(10192): sendrawtx exit 0, gave 82423444f3f79a9ebd7b706483008423b97626de700898f1aa984ed0e5b1f56f?
...
2018-04-02T09:43:00.871Z lightningd(10192): sendrawtx exit 0, gave 82423444f3f79a9ebd7b706483008423b97626de700898f1aa984ed0e5b1f56f?
...
2018-04-02T10:03:12.249Z lightningd(10192): sendrawtx exit 0, gave 82423444f3f79a9ebd7b706483008423b97626de700898f1aa984ed0e5b1f56f?
...
2018-04-02T10:23:13.379Z lightningd(10192): sendrawtx exit 0, gave 82423444f3f79a9ebd7b706483008423b97626de700898f1aa984ed0e5b1f56f?
...
2018-04-02T10:43:24.809Z lightningd(10192): Owning output 0 715602 (SEGWIT) txid 82423444f3f79a9ebd7b706483008423b97626de700898f1aa984ed0e5b1f56f
2018-04-02T10:43:24.901Z lightningd(10192): 03e14c229048c5e7174ec667ec3b7357b1dba6c069bdf04599b9d77f0d41c6ea84 chan #116: Got depth change 0->1 for 82423444f3f79a9ebd7b706483008423b97626de700898f1aa984ed0e5b1f56f
2018-04-02T10:43:24.901Z lightningd(10192): 03e14c229048c5e7174ec667ec3b7357b1dba6c069bdf04599b9d77f0d41c6ea84 chan #116: Funding tx 82423444f3f79a9ebd7b706483008423b97626de700898f1aa984ed0e5b1f56f depth 1 of 3
2018-04-02T11:03:26.331Z lightningd(10192): 03e14c229048c5e7174ec667ec3b7357b1dba6c069bdf04599b9d77f0d41c6ea84 chan #116: Got depth change 1->2 for 82423444f3f79a9ebd7b706483008423b97626de700898f1aa984ed0e5b1f56f
2018-04-02T11:03:26.331Z lightningd(10192): 03e14c229048c5e7174ec667ec3b7357b1dba6c069bdf04599b9d77f0d41c6ea84 chan #116: Funding tx 82423444f3f79a9ebd7b706483008423b97626de700898f1aa984ed0e5b1f56f depth 2 of 3
2018-04-02T11:06:16.542Z lightningd(10192): 03e14c229048c5e7174ec667ec3b7357b1dba6c069bdf04599b9d77f0d41c6ea84 chan #116: Got depth change 2->3 for 82423444f3f79a9ebd7b706483008423b97626de700898f1aa984ed0e5b1f56f
2018-04-02T11:06:16.542Z lightningd(10192): 03e14c229048c5e7174ec667ec3b7357b1dba6c069bdf04599b9d77f0d41c6ea84 chan #116: Funding tx 82423444f3f79a9ebd7b706483008423b97626de700898f1aa984ed0e5b1f56f depth 3 of 3
2018-04-02T11:06:16.542Z lightningd(10192): 03e14c229048c5e7174ec667ec3b7357b1dba6c069bdf04599b9d77f0d41c6ea84 chan #116: Got depth change 0->3 for 82423444f3f79a9ebd7b706483008423b97626de700898f1aa984ed0e5b1f56f
2018-04-02T11:17:17.325Z lightningd(10192): 03e14c229048c5e7174ec667ec3b7357b1dba6c069bdf04599b9d77f0d41c6ea84 chan #116: Got depth change 3->4 for 82423444f3f79a9ebd7b706483008423b97626de700898f1aa984ed0e5b1f56f
2018-04-02T11:37:18.665Z lightningd(10192): 03e14c229048c5e7174ec667ec3b7357b1dba6c069bdf04599b9d77f0d41c6ea84 chan #116: Got depth change 4->5 for 82423444f3f79a9ebd7b706483008423b97626de700898f1aa984ed0e5b1f56f

then it goes all the way to

2018-04-03T11:38:41.405Z lightningd(10192): 03e14c229048c5e7174ec667ec3b7357b1dba6c069bdf04599b9d77f0d41c6ea84 chan #116: Got depth change 236->237 for 82423444f3f79a9ebd7b706483008423b97626de700898f1aa984ed0e5b1f56f
2018-04-03T11:40:11.603Z lightningd(10192): 03e14c229048c5e7174ec667ec3b7357b1dba6c069bdf04599b9d77f0d41c6ea84 chan #116: Got depth change 237->238 for 82423444f3f79a9ebd7b706483008423b97626de700898f1aa984ed0e5b1f56f
2018-04-03T11:42:01.832Z lightningd(10192): 03e14c229048c5e7174ec667ec3b7357b1dba6c069bdf04599b9d77f0d41c6ea84 chan #116: Got depth change 238->239 for 82423444f3f79a9ebd7b706483008423b97626de700898f1aa984ed0e5b1f56f

[cdecker]

Could be other end not sending the funding_locked message? "connected" : false seems to support that. Could you attempt to reconnect?

[fixone]

you are right, once I've reconnected the state changed to NORMAL

[ZmnSCPxj]

Can rhis be closed? Are there remaining problems?

[fixone]

Yes, can be closed, no remaining issues

…

On Fri, Apr 6, 2018, 6:26 PM ZmnSCPxj, ZmnSCPxj jxPCSmnZ < ***@***.***> wrote: Can rhis be closed? Are there remaining problems? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#1316 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAL_Tj6ecANMH3K3z0vI8xZkWl8_CZw4ks5tl4kYgaJpZM4TE8Is> .