Autopilot channel opening forever

[stridentbean]

Background

This user turned on autopilot to open channels. One channel started opening but never finished. It has been for several weeks.

Any recommendations on how to close a stuck pending open channel?

Your environment

• version of lnd
  0.5.2-beta commit=v0.5.2-beta
• which operating system (uname -a on *Nix)
  Linux lnd 4.14.70-v7+ Fixing some README typos #2 SMP Wed Sep 19 07:49:26 UTC 2018 armv7l Linux
• version of btcd, bitcoind, or other backend
  bitcoind: 0.17.0
• any other relevant environment details
  bitcoind and lnd are running in docker containers
  raspberry pi 3b+

Steps to reproduce

Hard to give exact steps. Just turned on autopilot and it did its thing. It's possible a channel was in the opening process then switched to tor only before it completely opened.

Expected behaviour

Channel should open after a few blocks.

Actual behaviour

Channel is pending open. It is unable to be used and unable to be closed.

Data

From the logs file, a little redundant

2019-03-20T11:54:03Z lnd UNKNOWN[7504] 2019-03-20 11:54:03.539 [WRN] PEER: Unable to find our forwarding policy for channel 1ab35b431ec5df99ca71ebc938fff6c035bbd091f9a948bc0fd9add6c4992a19:0, using default values
2019-03-20T11:54:34Z lnd UNKNOWN[7504] 2019-03-20 11:54:34.007 [ERR] HSWC: ChannelLink(0:0:0) Failing link: unable to synchronize channel states: didn't receive ChannelReestablish before deadline
2019-03-20T11:59:08Z lnd UNKNOWN[7504] 2019-03-20 11:59:08.661 [WRN] PEER: Unable to find our forwarding policy for channel 1ab35b431ec5df99ca71ebc938fff6c035bbd091f9a948bc0fd9add6c4992a19:0, using default values
2019-03-20T11:59:38Z lnd UNKNOWN[7504] 2019-03-20 11:59:38.663 [ERR] HSWC: ChannelLink(0:0:0) Failing link: unable to synchronize channel states: didn't receive ChannelReestablish before deadline
2019-03-20T12:01:13Z lnd UNKNOWN[7504] 2019-03-20 12:01:13.845 [WRN] PEER: Unable to find our forwarding policy for channel 1ab35b431ec5df99ca71ebc938fff6c035bbd091f9a948bc0fd9add6c4992a19:0, using default values
2019-03-20T12:01:43Z lnd UNKNOWN[7504] 2019-03-20 12:01:43.847 [ERR] HSWC: ChannelLink(0:0:0) Failing link: unable to synchronize channel states: didn't receive ChannelReestablish before deadline
2019-03-20T12:06:55Z lnd UNKNOWN[7504] 2019-03-20 12:06:55.967 [WRN] PEER: Unable to find our forwarding policy for channel 1ab35b431ec5df99ca71ebc938fff6c035bbd091f9a948bc0fd9add6c4992a19:0, using default values
2019-03-20T12:07:25Z lnd UNKNOWN[7504] 2019-03-20 12:07:25.970 [ERR] HSWC: ChannelLink(0:0:0) Failing link: unable to synchronize channel states: didn't receive ChannelReestablish before deadline
2019-03-20T12:11:13Z lnd UNKNOWN[7504] 2019-03-20 12:11:13.433 [WRN] PEER: Unable to find our forwarding policy for channel 1ab35b431ec5df99ca71ebc938fff6c035bbd091f9a948bc0fd9add6c4992a19:0, using default values

[wpaulino]

The transaction doesn't seem to have propagated through the network. Is it in the bitcoind's mempool? What do the lnd logs show for the channel point?

[Roasbeef]

It looks like the transaction was just never actually broadcast, or the output was spent by something else. If so, then the funds aren't actually locked at all as we've removed the transaction.

[stridentbean]

The transaction doesn't seem to have propagated through the network. Is it in the bitcoind's mempool? What do the lnd logs show for the channel point?

How does one check the bitcoind mempool? I would think restarting it would flush anything out. Maybe we've got to manually flush it?

Is there anyway to remove a pending channel like that? Could always reset the wallet. I'll ask if the funds on chain add up. This is the only channel open atm.

Other logs that may or may not be useful

2019-03-18T14:04:16Z lnd UNKNOWN[7504] 2019-03-18 14:04:15.622 [ERR] LNWL: Unable to receive ZMQ rawtx message: invalid flag
2019-03-18T14:04:16Z lnd UNKNOWN[7504] 2019-03-18 14:04:15.622 [ERR] LNWL: Unable to receive ZMQ rawtx message: invalid flag
2019-03-18T14:04:16Z lnd UNKNOWN[7504] 2019-03-18 14:04:15.622 [ERR] LNWL: Unable to receive ZMQ rawtx message: invalid flag
2019-03-18T14:30:10Z lnd UNKNOWN[7504] 2019-03-18 14:30:10.907 [ERR] DISC: unable to fetch utxo for chan_id=592570796737429504: target output has been spent
2019-03-20T01:20:26Z lnd UNKNOWN[7504] 2019-03-20 01:20:26.076 [WRN] DISC: no channel updates found for short_chan_id=567903:1783:1
2019-03-20T01:20:27Z lnd UNKNOWN[7504] 2019-03-20 01:20:26.508 [WRN] DISC: no channel updates found for short_chan_id=520452:2171:0

[stridentbean]

The transaction doesn't seem to have propagated through the network. Is it in the bitcoind's mempool? What do the lnd logs show for the channel point?

How does one check the bitcoind mempool? I would think restarting it would flush anything out. Maybe we've got to manually flush it?

Is there anyway to remove a pending channel like that? Could always reset the wallet. I'll ask if the funds on chain add up. This is the only channel open atm.

Other logs that may or may not be useful

2019-03-18T14:04:16Z lnd UNKNOWN[7504] 2019-03-18 14:04:15.622 [ERR] LNWL: Unable to receive ZMQ rawtx message: invalid flag
2019-03-18T14:04:16Z lnd UNKNOWN[7504] 2019-03-18 14:04:15.622 [ERR] LNWL: Unable to receive ZMQ rawtx message: invalid flag
2019-03-18T14:04:16Z lnd UNKNOWN[7504] 2019-03-18 14:04:15.622 [ERR] LNWL: Unable to receive ZMQ rawtx message: invalid flag
2019-03-18T14:30:10Z lnd UNKNOWN[7504] 2019-03-18 14:30:10.907 [ERR] DISC: unable to fetch utxo for chan_id=592570796737429504: target output has been spent
2019-03-20T01:20:26Z lnd UNKNOWN[7504] 2019-03-20 01:20:26.076 [WRN] DISC: no channel updates found for short_chan_id=567903:1783:1
2019-03-20T01:20:27Z lnd UNKNOWN[7504] 2019-03-20 01:20:26.508 [WRN] DISC: no channel updates found for short_chan_id=520452:2171:0

[wpaulino]

How does one check the bitcoind mempool?

bitcoin-cli getrawtransaction tx_hash

If the transaction is double spending an input however, it won't show up in the mempool and the pending channel shown is just benign and can be ignored since the funds aren't actually locked up.

[stridentbean]

Seems it was a double spend error then. Thanks.