Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Channels stuck on "waiting_close_channels" #2636

Closed
danbadjar opened this issue Feb 12, 2019 · 1 comment
Closed

Channels stuck on "waiting_close_channels" #2636

danbadjar opened this issue Feb 12, 2019 · 1 comment

Comments

@danbadjar
Copy link

Background

Hello, I have 2 channels stuck on waiting_close_channels and I can't force close them.
If I try to force close :

channel is already in the process of being force closed

In my logs I found :
[ERR] NTFN: Rescan to determine the spend details of outpoint=cee48f182027505458756419972717da9267bf4d65ac7a3452a843a0ef691807:1 within range 562608-562761 failed: transaction not found within range [ERR] NTFN: Rescan to determine the spend details of outpoint=e0c3caca63303d272654ff73f4c9937fa785662897a2fc570d0ae504e0738688:1 within range 562608-562761 failed: transaction not found within range

Looking for the first channel point I found:
2019-02-11 15:58:47.322 [INF] PEER: ChannelPoint(cee48f182027505458756419972717da9267bf4d65ac7a3452a843a0ef691807:1): sending shutdown message 2019-02-11 15:58:47.323 [INF] PEER: ChannelPoint(cee48f182027505458756419972717da9267bf4d65ac7a3452a843a0ef691807:1): Responding to shutdown 2019-02-11 15:58:47.329 [INF] PEER: ChannelPoint(cee48f182027505458756419972717da9267bf4d65ac7a3452a843a0ef691807:1): proposing fee of 383 sat to close chan 2019-02-11 15:58:48.117 [INF] PEER: ChannelPoint(cee48f182027505458756419972717da9267bf4d65ac7a3452a843a0ef691807:1) fee of 0.00000383 BTC accepted, ending negotiation PreviousOutPoint: (wire.OutPoint) cee48f182027505458756419972717da9267bf4d65ac7a3452a843a0ef691807:1, 2019-02-11 15:58:48.383 [INF] PEER: Waiting for confirmation of cooperative close of ChannelPoint(cee48f182027505458756419972717da9267bf4d65ac7a3452a843a0ef691807:1) with txid: 4dc27af5085586d 5feeeca8a6e814bf98b9d7d1cff35ee0119ded34ef09bac48 2019-02-11 17:30:58.389 [INF] NTFN: New spend subscription: spend_id=20, outpoint=cee48f182027505458756419972717da9267bf4d65ac7a3452a843a0ef691807:1, height_hint=560803 2019-02-11 17:30:59.114 [INF] CNCT: Close observer for ChannelPoint(cee48f182027505458756419972717da9267bf4d65ac7a3452a843a0ef691807:1) active 2019-02-11 17:31:01.215 [INF] CNCT: ChannelArbitrator(cee48f182027505458756419972717da9267bf4d65ac7a3452a843a0ef691807:1): starting state=StateDefault 2019-02-11 17:31:01.688 [ERR] NTFN: Rescan to determine the spend details of outpoint=cee48f182027505458756419972717da9267bf4d65ac7a3452a843a0ef691807:1 within range 562608-562608 failed: tran saction not found within range 2019-02-11 17:31:14.618 [INF] PEER: NodeKey(038ddc73e450a4bfb52992b35be8b0f52e1a1b4726ff319249a3314a508b616cde) loading ChannelPoint(cee48f182027505458756419972717da9267bf4d65ac7a3452a843a0ef6 91807:1) 2019-02-11 17:31:14.618 [WRN] PEER: ChannelPoint(cee48f182027505458756419972717da9267bf4d65ac7a3452a843a0ef691807:1) has status ChanStatusDefault|ChanStatusCommitBroadcasted, won't start.

Is this a bug? Is there a way to unlock this funds? Sorry , newbie here.

Your environment

  • v0.5.1-beta-704
  • linux
  • bitcoind-0.17.1
  • any other relevant environment details
@wpaulino
Copy link
Contributor

Everything is working as expected. You closed the channel cooperatively, so now you'll have to wait for the closing transaction to confirm on-chain to access your funds.

[ERR] NTFN: Rescan to determine the spend details of outpoint=cee48f182027505458756419972717da9267bf4d65ac7a3452a843a0ef691807:1 within range 562608-562761 failed: transaction not found within range [ERR] NTFN: Rescan to determine the spend details of outpoint=e0c3caca63303d272654ff73f4c9937fa785662897a2fc570d0ae504e0738688:1 within range 562608-562761 failed: transaction not found within range

This is a benign error and should be demoted.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants