-
Notifications
You must be signed in to change notification settings - Fork 946
Description
I have been attempting to open and successfully close a testnet transaction between two of my computers. So far I got to the point where both computers successfully open a channel and are in the CHANNELD_NORMAL state. As a test, I tried a mutual close of the channels with lightning-cli close
peer-b-id from peer-a. This put both peers in the CLOSINGD_SIGEXCHANGE state. I've done this twice and I've never been able to get it out of this state.
After restarting both nodes, I tried to reconnect to peer-b from peer-a (02058ea66978d2e5c346642c45f3cec5a4c733897b59244fc29c3107e844f62608
), I get this on peer-b:
lightningd(29128): peer 02058ea66978d2e5c346642c45f3cec5a4c733897b59244fc29c3107e844f62608: Peer has reconnected, state CLOSINGD_SIGEXCHANGE
lightning_gossipd(29137): TRACE: Forgetting remote peer 02058ea66978d2e5c346642c45f3cec5a4c733897b59244fc29c3107e844f62608
lightning_gossipd(29137): TRACE: req: type WIRE_GOSSIPCTL_HANDLE_PEER len 279
lightning_gossipd(29137): TRACE: handle_peer 02058ea66978d2e5c346642c45f3cec5a4c733897b59244fc29c3107e844f62608: new peer
lightning_gossipd(29137): TRACE: 02058ea66978d2e5c346642c45f3cec5a4c733897b59244fc29c3107e844f62608: we sent them a fatal error, closing
Error is : Final fee 362 vs 329 at limits 363-535
and then peer-a just hangs. also, "we sent them a fatal error" doesn't seem to be true, since a fatal error is not reported to peer-a. possibly related: #405