You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
version of btcd, bitcoind, or other backend: bitcoind v0.15.1
any other relevant environment details
Steps to reproduce
Don't know how to reproduce on different nodes.
Expected behaviour
Open channel and keep the active status connecting with the node.
Actual behaviour
I have a channel opened with a node (028c1f8d907879ee8691ddab3547e93c5ec2098cc0f38cc39c4ee989cb3a10ae71). The channel went offline and every time I try to reconnect it goes in active state for a while (30sec) then I see the following error:
2018-06-11 10:56:25.059 [ERR] HSWC: ChannelLink(521292:551:0) unable to synchronize channel states: didn't receive ChannelReestablish before deadline
2018-06-11 10:56:25.060 [ERR] HSWC: ChannelLink(521292:551:0) Failing link: didn't receive ChannelReestablish before deadline
This happens only with a single channel. Other channels works fine. This happened on 0.5.1 and 0.5.2.
I also see these errors (but I don't think they are connected to the same issue, but I see every time I restart LND and I would like to remove it):
2018-06-11 10:51:13.775 [INF] HSWC: Adding live link chan_id=f69a436a38c75b500514432b4781581d91f92446c3c65923a2b9562e3777f0cd, short_chan_id=518867:1610:1
2018-06-11 10:51:15.162 [INF] HSWC: Received re-establishment message from remote side for channel(ccf077372e56b9a22359c6c34624f9911d5881472b431405505bc7386a439af6:1)
2018-06-11 10:51:15.252 [ERR] HSWC: failing packet after detecting incomplete forward
2018-06-11 10:51:15.210 [ERR] HSWC: failing packet after detecting incomplete forward
2018-06-11 10:51:15.231 [ERR] HSWC: failing packet after detecting incomplete forward
2018-06-11 10:51:15.273 [ERR] HSWC: failing packet after detecting incomplete forward
2018-06-11 10:51:15.293 [ERR] HSWC: failing packet after detecting incomplete forward
2018-06-11 10:51:15.314 [ERR] HSWC: failing packet after detecting incomplete forward
2018-06-11 10:51:15.333 [ERR] HSWC: failing packet after detecting incomplete forward
2018-06-11 10:51:15.353 [ERR] HSWC: failing packet after detecting incomplete forward
2018-06-11 10:51:15.373 [ERR] HSWC: failing packet after detecting incomplete forward
2018-06-11 10:51:15.392 [ERR] HSWC: failing packet after detecting incomplete forward
2018-06-11 10:51:15.412 [ERR] HSWC: failing packet after detecting incomplete forward
2018-06-11 10:51:15.431 [ERR] HSWC: failing packet after detecting incomplete forward
2018-06-11 10:51:15.451 [ERR] HSWC: failing packet after detecting incomplete forward
2018-06-11 10:51:15.472 [ERR] HSWC: failing packet after detecting incomplete forward
2018-06-11 10:51:15.492 [ERR] HSWC: failing packet after detecting incomplete forward
2018-06-11 10:51:15.511 [ERR] HSWC: failing packet after detecting incomplete forward
2018-06-11 10:51:15.533 [ERR] HSWC: failing packet after detecting incomplete forward
2018-06-11 10:51:15.553 [ERR] HSWC: failing packet after detecting incomplete forward
2018-06-11 10:51:15.573 [ERR] HSWC: failing packet after detecting incomplete forward
2018-06-11 10:51:15.593 [ERR] HSWC: failing packet after detecting incomplete forward
2018-06-11 10:51:15.612 [ERR] HSWC: failing packet after detecting incomplete forward
2018-06-11 10:51:15.633 [ERR] HSWC: failing packet after detecting incomplete forward
2018-06-11 10:51:15.652 [ERR] HSWC: failing packet after detecting incomplete forward
2018-06-11 10:51:15.672 [ERR] HSWC: failing packet after detecting incomplete forward
2018-06-11 10:51:15.691 [ERR] HSWC: failing packet after detecting incomplete forward
2018-06-11 10:51:15.715 [ERR] HSWC: failing packet after detecting incomplete forward
2018-06-11 10:51:15.735 [ERR] HSWC: failing packet after detecting incomplete forward
2018-06-11 10:51:15.764 [ERR] HSWC: failing packet after detecting incomplete forward
2018-06-11 10:51:15.784 [ERR] HSWC: failing packet after detecting incomplete forward
2018-06-11 10:51:15.803 [ERR] HSWC: failing packet after detecting incomplete forward
2018-06-11 10:51:15.823 [ERR] HSWC: failing packet after detecting incomplete forward
2018-06-11 10:51:15.842 [ERR] HSWC: failing packet after detecting incomplete forward
2018-06-11 10:51:15.862 [ERR] HSWC: failing packet after detecting incomplete forward
2018-06-11 10:51:15.882 [ERR] HSWC: failing packet after detecting incomplete forward
2018-06-11 10:51:15.902 [ERR] HSWC: failing packet after detecting incomplete forward
2018-06-11 10:51:15.921 [ERR] HSWC: failing packet after detecting incomplete forward
2018-06-11 10:51:15.941 [ERR] HSWC: failing packet after detecting incomplete forward
2018-06-11 10:51:15.961 [ERR] HSWC: failing packet after detecting incomplete forward
2018-06-11 10:51:15.982 [ERR] HSWC: failing packet after detecting incomplete forward
2018-06-11 10:51:16.003 [ERR] HSWC: failing packet after detecting incomplete forward
2018-06-11 10:51:16.023 [ERR] HSWC: failing packet after detecting incomplete forward
2018-06-11 10:51:16.042 [ERR] HSWC: failing packet after detecting incomplete forward
2018-06-11 10:51:16.062 [ERR] HSWC: failing packet after detecting incomplete forward
2018-06-11 10:51:16.082 [ERR] HSWC: failing packet after detecting incomplete forward
2018-06-11 10:51:16.102 [ERR] HSWC: failing packet after detecting incomplete forward
2018-06-11 10:51:16.121 [ERR] HSWC: failing packet after detecting incomplete forward
2018-06-11 10:51:16.141 [ERR] HSWC: failing packet after detecting incomplete forward
2018-06-11 10:51:16.161 [ERR] HSWC: failing packet after detecting incomplete forward
2018-06-11 10:51:16.181 [ERR] HSWC: failing packet after detecting incomplete forward
2018-06-11 10:51:16.181 [ERR] HSWC: unable to cancel HTLC: No HTLC with ID 1 in channel 518867:1610:1
2018-06-11 10:51:16.181 [ERR] HSWC: unable to cancel HTLC: No HTLC with ID 2 in channel 518867:1610:1
2018-06-11 10:51:16.181 [ERR] HSWC: unable to cancel HTLC: No HTLC with ID 3 in channel 518867:1610:1
2018-06-11 10:51:16.181 [ERR] HSWC: unable to cancel HTLC: No HTLC with ID 4 in channel 518867:1610:1
2018-06-11 10:51:16.181 [ERR] HSWC: unable to cancel HTLC: No HTLC with ID 5 in channel 518867:1610:1
2018-06-11 10:51:16.181 [ERR] HSWC: unable to cancel HTLC: No HTLC with ID 6 in channel 518867:1610:1
2018-06-11 10:51:16.181 [ERR] HSWC: unable to cancel HTLC: No HTLC with ID 7 in channel 518867:1610:1
2018-06-11 10:51:16.181 [ERR] HSWC: unable to cancel HTLC: No HTLC with ID 8 in channel 518867:1610:1
2018-06-11 10:51:16.181 [ERR] HSWC: unable to cancel HTLC: No HTLC with ID 9 in channel 518867:1610:1
2018-06-11 10:51:16.181 [ERR] HSWC: unable to cancel HTLC: No HTLC with ID 10 in channel 518867:1610:1
2018-06-11 10:51:16.181 [ERR] HSWC: unable to cancel HTLC: No HTLC with ID 11 in channel 518867:1610:1
2018-06-11 10:51:16.182 [ERR] HSWC: unable to cancel HTLC: No HTLC with ID 12 in channel 518867:1610:1
2018-06-11 10:51:16.182 [ERR] HSWC: unable to cancel HTLC: No HTLC with ID 13 in channel 518867:1610:1
2018-06-11 10:51:16.182 [ERR] HSWC: unable to cancel HTLC: No HTLC with ID 14 in channel 518867:1610:1
2018-06-11 10:51:16.182 [ERR] HSWC: unable to cancel HTLC: No HTLC with ID 15 in channel 518867:1610:1
2018-06-11 10:51:16.182 [ERR] HSWC: unable to cancel HTLC: No HTLC with ID 16 in channel 518867:1610:1
2018-06-11 10:51:16.182 [ERR] HSWC: unable to cancel HTLC: No HTLC with ID 17 in channel 518867:1610:1
2018-06-11 10:51:16.182 [ERR] HSWC: unable to cancel HTLC: No HTLC with ID 18 in channel 518867:1610:1
2018-06-11 10:51:16.182 [ERR] HSWC: unable to cancel HTLC: No HTLC with ID 19 in channel 518867:1610:1
2018-06-11 10:51:16.182 [ERR] HSWC: unable to cancel HTLC: No HTLC with ID 20 in channel 518867:1610:1
2018-06-11 10:51:16.182 [ERR] HSWC: unable to cancel HTLC: No HTLC with ID 21 in channel 518867:1610:1
2018-06-11 10:51:16.182 [ERR] HSWC: unable to cancel HTLC: No HTLC with ID 22 in channel 518867:1610:1
2018-06-11 10:51:16.182 [ERR] HSWC: unable to cancel HTLC: No HTLC with ID 23 in channel 518867:1610:1
2018-06-11 10:51:16.182 [ERR] HSWC: unable to cancel HTLC: No HTLC with ID 24 in channel 518867:1610:1
2018-06-11 10:51:16.182 [ERR] HSWC: unable to cancel HTLC: No HTLC with ID 25 in channel 518867:1610:1
2018-06-11 10:51:16.182 [ERR] HSWC: unable to cancel HTLC: No HTLC with ID 26 in channel 518867:1610:1
2018-06-11 10:51:16.182 [ERR] HSWC: unable to cancel HTLC: No HTLC with ID 27 in channel 518867:1610:1
2018-06-11 10:51:16.182 [ERR] HSWC: unable to cancel HTLC: No HTLC with ID 28 in channel 518867:1610:1
2018-06-11 10:51:16.182 [ERR] HSWC: unable to cancel HTLC: No HTLC with ID 29 in channel 518867:1610:1
2018-06-11 10:51:16.182 [ERR] HSWC: unable to cancel HTLC: No HTLC with ID 30 in channel 518867:1610:1
2018-06-11 10:51:16.182 [ERR] HSWC: unable to cancel HTLC: No HTLC with ID 31 in channel 518867:1610:1
2018-06-11 10:51:16.182 [ERR] HSWC: unable to cancel HTLC: No HTLC with ID 32 in channel 518867:1610:1
2018-06-11 10:51:16.182 [ERR] HSWC: unable to cancel HTLC: No HTLC with ID 33 in channel 518867:1610:1
2018-06-11 10:51:16.182 [ERR] HSWC: unable to cancel HTLC: No HTLC with ID 34 in channel 518867:1610:1
2018-06-11 10:51:16.182 [ERR] HSWC: unable to cancel HTLC: No HTLC with ID 35 in channel 518867:1610:1
2018-06-11 10:51:16.182 [ERR] HSWC: unable to cancel HTLC: No HTLC with ID 36 in channel 518867:1610:1
2018-06-11 10:51:16.182 [ERR] HSWC: unable to cancel HTLC: No HTLC with ID 37 in channel 518867:1610:1
2018-06-11 10:51:16.182 [ERR] HSWC: unable to cancel HTLC: No HTLC with ID 38 in channel 518867:1610:1
2018-06-11 10:51:16.182 [ERR] HSWC: unable to cancel HTLC: No HTLC with ID 39 in channel 518867:1610:1
2018-06-11 10:51:16.182 [ERR] HSWC: unable to cancel HTLC: No HTLC with ID 40 in channel 518867:1610:1
2018-06-11 10:51:16.182 [ERR] HSWC: unable to cancel HTLC: No HTLC with ID 41 in channel 518867:1610:1
2018-06-11 10:51:16.182 [ERR] HSWC: unable to cancel HTLC: No HTLC with ID 42 in channel 518867:1610:1
2018-06-11 10:51:16.182 [ERR] HSWC: unable to cancel HTLC: No HTLC with ID 43 in channel 518867:1610:1
2018-06-11 10:51:16.183 [ERR] HSWC: unable to cancel HTLC: No HTLC with ID 44 in channel 518867:1610:1
2018-06-11 10:51:16.183 [ERR] HSWC: unable to cancel HTLC: No HTLC with ID 45 in channel 518867:1610:1
2018-06-11 10:51:16.183 [ERR] HSWC: unable to cancel HTLC: No HTLC with ID 46 in channel 518867:1610:1
2018-06-11 10:51:16.183 [ERR] HSWC: unable to cancel HTLC: No HTLC with ID 47 in channel 518867:1610:1
2018-06-11 10:51:16.183 [ERR] HSWC: unable to cancel HTLC: No HTLC with ID 48 in channel 518867:1610:1
2018-06-11 10:51:16.183 [ERR] HSWC: unable to cancel HTLC: No HTLC with ID 49 in channel 518867:1610:1
2018-06-11 10:51:22.468 [INF] HSWC: Sent 0 satoshis and received 0 satoshis in the last 10 seconds (50.100000 tx/sec)
Thanks
The text was updated successfully, but these errors were encountered:
Background
Channel goes offline and online every minute
Your environment
uname -aon *Nix): Linux 4.4.0-121-generic rpcserver: fix pendingchannels panic #145-Ubuntu SMPbtcd,bitcoind, or other backend: bitcoind v0.15.1Steps to reproduce
Don't know how to reproduce on different nodes.
Expected behaviour
Open channel and keep the active status connecting with the node.
Actual behaviour
I have a channel opened with a node (028c1f8d907879ee8691ddab3547e93c5ec2098cc0f38cc39c4ee989cb3a10ae71). The channel went offline and every time I try to reconnect it goes in active state for a while (30sec) then I see the following error:
This happens only with a single channel. Other channels works fine. This happened on 0.5.1 and 0.5.2.
I also see these errors (but I don't think they are connected to the same issue, but I see every time I restart LND and I would like to remove it):
Thanks
The text was updated successfully, but these errors were encountered: