Lost sats when mynode crashed while I had a pending opening channel #5664

ziomanzo · 2021-08-25T07:39:38Z

ziomanzo
Aug 25, 2021

Mynode hade a power failure a while ago and I had pending opening channels. I recovered from seed + scb file. But still a weird situation my 2M sats are lost.
Does anybody has an idea how to solve this? I had contact with LNBIG but still unable to recover my 2M sats.

Onchain TX (Screenshot RTL)

Waiting close (screenshot RTL)

Any suggestions to recover my 2M sats?

Answered by guggero

Sep 16, 2021

Looks good, now you just have to wait for the time lock to expire (blocks_till_maturity).

View full answer

guggero · 2021-08-25T07:41:08Z

guggero
Aug 25, 2021
Collaborator

Can you post the channel point as text please so we don't have to type it from the screenshot? Thanks.

1 reply

ziomanzo Aug 25, 2021
Author

e4500f1e34bd2d6924265efcf95e92c4fbbe0d0e80955fa4eb396eb23e09ce07:1

guggero · 2021-08-25T07:49:40Z

guggero
Aug 25, 2021
Collaborator

Is the second screenshot what you see after you restored from seed+SCB? Can you try manually connecting to the peer "LNBIG.com [lnd-27]"? That should cause them to force close the channel and your node to sweep the funds.

6 replies

ziomanzo Aug 25, 2021
Author

Ps.

Mynode pubkey:
0290ba7b9d7d16d86c6ab71b43258f38e6eea12c71da110a2d895c6ae20fcdc01a

guggero Aug 25, 2021
Collaborator

That is weird, LNBIG's node should close the channel from their end if you're connected and restored from SCB. Can you try restarting your node? If that doesn't do anything, can you paste the output of lncli pendingchannels here please? And perhaps the logs from the last startup, grepped by e4500f1e34bd2d6924265efcf95e92c4fbbe0d0e80955fa4eb396eb23e09ce07 and 03fce165537aea120bffe8505876b44d5119354f825b3eac329b761fc5636bf334.

ziomanzo Aug 25, 2021
Author

I restarted mynode several times already.
I don't know how to grep the logs by this specific endpoint. I flashed my sdcard on my pi with MynodeBTC. I can only see current recent logs, I don't know how to do this manually.

guggero Aug 25, 2021
Collaborator

Okay, can you just upload the latest log file please?

ziomanzo Aug 25, 2021
Author

when I go to logs in the mynode UX I can only see the most recent logs of today, I can't go further in time (in MAY)
I'll google later today how to get the logs grepped by this this specific endpoint and the peer node like you asked before.
thanks for trying to help me!

ps.: this is the output of pending close:
lncli pending close:

"waiting_close_channels": [

        "channel": {
            "remote_node_pub": "03fce165537aea120bffe8505876b44d5119354f825b3eac329b761fc5636bf334",
            "channel_point": "e4500f1e34bd2d6924265efcf95e92c4fbbe0d0e80955fa4eb396eb23e09ce07:1",
            "capacity": "2000000",
            "local_balance": "0",
            "remote_balance": "0",
            "local_chan_reserve_sat": "0",
            "remote_chan_reserve_sat": "0",
            "initiator": "INITIATOR_LOCAL",
            "commitment_type": "STATIC_REMOTE_KEY"
        },
        "limbo_balance": "0",
        "commitments": {
            "local_txid": "",
            "remote_txid": "",
            "remote_pending_txid": "",
            "local_commit_fee_sat": "0",
            "remote_commit_fee_sat": "0",
            "remote_pending_commit_fee_sat": "0"

guadama · 2021-09-12T03:26:54Z

guadama
Sep 12, 2021

Greetings ... Excuse me, could you help me with a similar problem?

I closed a channel and still the balance is not seen in the onChain ... I am new to this and I don't know what to do. I thank you who could help me

4 replies

guggero Sep 13, 2021
Collaborator

Try force-closing the channel.

guadama Sep 16, 2021

Try force-closing the channel.

2021-09-16 02:56:42.545 [ERR] RPCS: [/lnrpc.Lightning/CloseChannel]: channel not found
2021-09-16 02:58:15.433 [INF] HSWC: Removing channel link with ChannelID(1abef2db6b59b2948c86fe901c00101239cd89c654623ded3bf7b505316607b9)
2021-09-16 02:58:15.436 [INF] CNCT: Attempting to force close ChannelPoint(b807663105b5f73bed3d6254c689cd391210001c90fe868c94b2596bdbf2be1a:1)
2021-09-16 02:58:15.444 [INF] NANN: Announcing channel(b807663105b5f73bed3d6254c689cd391210001c90fe868c94b2596bdbf2be1a:1) disabled [requested]
2021-09-16 03:00:18.642 [ERR] RPCS: [/lnrpc.Lightning/GetNodeInfo]: rpc error: code = NotFound desc = unable to find node
2021-09-16 03:00:18.711 [ERR] RPCS: [/lnrpc.Lightning/GetNodeInfo]: rpc error: code = NotFound desc = unable to find node
2021-09-16 03:01:01.439 [ERR] RPCS: [/lnrpc.Lightning/GetNodeInfo]: rpc error: code = NotFound desc = unable to find node
2021-09-16 03:01:01.440 [ERR] RPCS: [/lnrpc.Lightning/GetNodeInfo]: rpc error: code = NotFound desc = unable to find node
2021-09-16 03:04:50.056 [INF] HSWC: Removing channel link with ChannelID(1abef2db6b59b2948c86fe901c00101239cd89c654623ded3bf7b505316607b9)
2021-09-16 03:04:50.056 [INF] CNCT: Attempting to force close ChannelPoint(b807663105b5f73bed3d6254c689cd391210001c90fe868c94b2596bdbf2be1a:1)
2021-09-16 03:13:01.241 [INF] HSWC: Removing channel link with ChannelID(1abef2db6b59b2948c86fe901c00101239cd89c654623ded3bf7b505316607b9)
2021-09-16 03:13:01.242 [INF] CNCT: Attempting to force close ChannelPoint(b807663105b5f73bed3d6254c689cd391210001c90fe868c94b2596bdbf2be1a:1)
2021-09-16 03:17:53.329 [ERR] RPCS: [/lnrpc.Lightning/GetNodeInfo]: rpc error: code = NotFound desc = unable to find node
2021-09-16 03:17:53.331 [ERR] RPCS: [/lnrpc.Lightning/GetNodeInfo]: rpc error: code = NotFound desc = unable to find node
2021-09-16 03:19:53.174 [INF] NTFN: New block: height=700746, sha=00000000000000000004d64cffeb3069ae369d0d972bea1f9c7604943121e503
2021-09-16 03:19:53.178 [INF] UTXN: Attempting to graduate height=700746: num_kids=0, num_babies=0
2021-09-16 03:23:14.576 [INF] NTFN: New block: height=700747, sha=00000000000000000001024903ff55aaaaddec7e5a88a8367a3c0c6d7ff13479
2021-09-16 03:23:14.576 [INF] UTXN: Attempting to graduate height=700747: num_kids=0, num_babies=0
2021-09-16 03:28:25.625 [ERR] RPCS: [/lnrpc.Lightning/GetNodeInfo]: rpc error: code = NotFound desc = unable to find node
2021-09-16 03:28:25.630 [ERR] RPCS: [/lnrpc.Lightning/GetNodeInfo]: rpc error: code = NotFound desc = unable to find node

guadama Sep 16, 2021

Try force-closing the channel.

lncli pendingchannels

{
"total_limbo_balance": "98085",
"pending_open_channels": [
],
"pending_closing_channels": [
],
"pending_force_closing_channels": [
{
"channel": {
"remote_node_pub": "034ea80f8b148c750463546bd999bf7321a0e6dfc60aaf84bd0400a2e8d376c0d5",
"channel_point": "b807663105b5f73bed3d6254c689cd391210001c90fe868c94b2596bdbf2be1a:1",
"capacity": "100000",
"local_balance": "97755",
"remote_balance": "0",
"local_chan_reserve_sat": "0",
"remote_chan_reserve_sat": "0",
"initiator": "INITIATOR_LOCAL",
"commitment_type": "ANCHORS"
},
"closing_txid": "44bb5eab3671ef308960592a6f09975c52ffe56280cdcbcdbe09c3f86fc32333",
"limbo_balance": "98085",
"maturity_height": 700895,
"blocks_til_maturity": 95,
"recovered_balance": "0",
"pending_htlcs": [
],
"anchor": "LIMBO"
}
],
"waiting_close_channels": [
]
}

guadama Sep 16, 2021

lncli logs

2021-09-16 12:44:44.387 [WRN] BTCN: Query(230) from peer 62.210.71.120:8333 failed, rescheduling: did not get response before timeout
2021-09-16 12:44:50.836 [WRN] BTCN: Query(231) from peer 62.210.71.120:8333 failed, rescheduling: did not get response before timeout
2021-09-16 12:44:50.836 [WRN] BTCN: Query(231) failed with error: did not get response before timeout. Timing out.
2021-09-16 12:44:54.837 [WRN] BTCN: Query(231) from peer 62.210.71.120:8333 failed, rescheduling: did not get response before timeout
2021-09-16 12:45:02.838 [WRN] BTCN: Query(231) from peer 62.210.71.120:8333 failed, rescheduling: did not get response before timeout
2021-09-16 12:45:08.201 [WRN] BTCN: Query(232) from peer 62.210.71.120:8333 failed, rescheduling: did not get response before timeout
2021-09-16 12:45:08.201 [WRN] BTCN: Query(232) failed with error: did not get response before timeout. Timing out.
2021-09-16 12:45:12.203 [WRN] BTCN: Query(232) from peer 62.210.71.120:8333 failed, rescheduling: did not get response before timeout
2021-09-16 12:45:20.204 [WRN] BTCN: Query(232) from peer 62.210.71.120:8333 failed, rescheduling: did not get response before timeout
2021-09-16 12:45:36.323 [WRN] BTCN: Query(233) from peer 62.210.71.120:8333 failed, rescheduling: did not get response before timeout
2021-09-16 12:45:36.323 [WRN] BTCN: Query(233) failed with error: did not get response before timeout. Timing out.
2021-09-16 12:45:40.324 [WRN] BTCN: Query(233) from peer 62.210.71.120:8333 failed, rescheduling: did not get response before timeout
2021-09-16 12:45:48.325 [WRN] BTCN: Query(233) from peer 62.210.71.120:8333 failed, rescheduling: did not get response before timeout
2021-09-16 12:45:53.969 [WRN] BTCN: Query(234) from peer 62.210.71.120:8333 failed, rescheduling: did not get response before timeout
2021-09-16 12:45:53.969 [WRN] BTCN: Query(234) failed with error: did not get response before timeout. Timing out.
2021-09-16 12:45:57.970 [WRN] BTCN: Query(234) from peer 62.210.71.120:8333 failed, rescheduling: did not get response before timeout
2021-09-16 12:46:05.970 [WRN] BTCN: Query(234) from peer 62.210.71.120:8333 failed, rescheduling: did not get response before timeout
2021-09-16 12:46:18.148 [WRN] BTCN: Query(235) from peer 62.210.71.120:8333 failed, rescheduling: did not get response before timeout
2021-09-16 12:46:18.149 [WRN] BTCN: Query(235) failed with error: did not get response before timeout. Timing out.
2021-09-16 12:46:22.158 [WRN] BTCN: Query(235) from peer 62.210.71.120:8333 failed, rescheduling: did not get response before timeout
2021-09-16 12:46:30.159 [WRN] BTCN: Query(235) from peer 62.210.71.120:8333 failed, rescheduling: did not get response before timeout
2021-09-16 12:46:39.510 [WRN] BTCN: Query(236) from peer 62.210.71.120:8333 failed, rescheduling: did not get response before timeout
2021-09-16 12:46:39.510 [WRN] BTCN: Query(236) failed with error: did not get response before timeout. Timing out.
2021-09-16 12:46:43.511 [WRN] BTCN: Query(236) from peer 62.210.71.120:8333 failed, rescheduling: did not get response before timeout
2021-09-16 12:46:51.512 [WRN] BTCN: Query(236) from peer 62.210.71.120:8333 failed, rescheduling: did not get response before timeout
2021-09-16 12:46:57.598 [WRN] BTCN: Query(237) from peer 62.210.71.120:8333 failed, rescheduling: did not get response before timeout
2021-09-16 12:46:57.598 [WRN] BTCN: Query(237) failed with error: did not get response before timeout. Timing out.
2021-09-16 12:47:01.599 [WRN] BTCN: Query(237) from peer 62.210.71.120:8333 failed, rescheduling: did not get response before timeout

guggero · 2021-09-16T13:56:10Z

guggero
Sep 16, 2021
Collaborator

Looks good, now you just have to wait for the time lock to expire (blocks_till_maturity).

1 reply

guadama Sep 16, 2021

Looks good, now you just have to wait for the time lock to expire (blocks_till_maturity).

Thank you very much for your attention and advice

Lost sats when mynode crashed while I had a pending opening channel #5664

Uh oh!

ziomanzo Aug 25, 2021

Replies: 4 comments · 12 replies

Uh oh!

guggero Aug 25, 2021 Collaborator

Uh oh!

Uh oh!

ziomanzo Aug 25, 2021 Author

Uh oh!

guggero Aug 25, 2021 Collaborator

Uh oh!

ziomanzo Aug 25, 2021 Author

Uh oh!

guggero Aug 25, 2021 Collaborator

Uh oh!

ziomanzo Aug 25, 2021 Author

Uh oh!

guggero Aug 25, 2021 Collaborator

Uh oh!

Uh oh!

ziomanzo Aug 25, 2021 Author

Uh oh!

guadama Sep 12, 2021

Uh oh!

guggero Sep 13, 2021 Collaborator

Uh oh!

guadama Sep 16, 2021

Uh oh!

guadama Sep 16, 2021

Uh oh!

guadama Sep 16, 2021

Uh oh!

guggero Sep 16, 2021 Collaborator

Uh oh!

guadama Sep 16, 2021

ziomanzo
Aug 25, 2021

Replies: 4 comments 12 replies

guggero
Aug 25, 2021
Collaborator

ziomanzo Aug 25, 2021
Author

guggero
Aug 25, 2021
Collaborator

ziomanzo Aug 25, 2021
Author

guggero Aug 25, 2021
Collaborator

ziomanzo Aug 25, 2021
Author

guggero Aug 25, 2021
Collaborator

ziomanzo Aug 25, 2021
Author

guadama
Sep 12, 2021

guggero Sep 13, 2021
Collaborator

guggero
Sep 16, 2021
Collaborator