Exit on startup: unable to force close channel #3477
Comments
|
Looks similar to #1267 (a very old issue). How long has this node been in operation? If you apply this patch, then you'll be able to start up again: diff --git a/contractcourt/channel_arbitrator.go b/contractcourt/channel_arbitrator.go
index b90707686..030eccb43 100644
--- a/contractcourt/channel_arbitrator.go
+++ b/contractcourt/channel_arbitrator.go
@@ -403,7 +403,7 @@ func (c *ChannelArbitrator) Start() error {
default:
c.cfg.BlockEpochs.Cancel()
- return err
+ //return err
}
}Looks like the you don't have any coins in the channel, so you can use the note added: Also while you're at it, I'd recommend updating to (edited your initial issue to remove some possibly sensitive content) |
|
Thanks roasbeef - will try to add the patch this morning and see if I can get back up and running and will then attempt to use abandonchannel. Node has been operation for about 7 months. Will update once I'm able to test. |
|
Still appear to be having the same issue after updating to 0.7.1 and applying the patch (commented out return err from contract court). Still crashing on startup after unlocking node. Debug error logs as follows (let me know if it would be helpful to see the full log of startup): 2019-09-06 15:24:23.858 [ERR] CNCT: ChannelArbitrator(800367ed55bbba13ba2586765ed8d681dfa5eba91602c66a2c183d676326b256:1): unable to broadcast close tx: -26: bad-txns-in-belowout, value in (0.00057) < value out (0.14996174) (code 16) |
|
Actually here's the proper patch to be able to restart: diff --git a/contractcourt/chain_arbitrator.go b/contractcourt/chain_arbitrator.go
index b3cd497d2..f57ee63ad 100644
--- a/contractcourt/chain_arbitrator.go
+++ b/contractcourt/chain_arbitrator.go
@@ -511,7 +511,7 @@ func (c *ChainArbitrator) Start() error {
// can carry out their duties.
for _, arbitrator := range c.activeChannels {
if err := arbitrator.Start(); err != nil {
- c.Stop()
+ //c.Stop()
return err
}
} |
|
Worked further with roasbeef to get the issue of node-startup solved with the patch included at the bottom. As a next step, used abandon channel to attempt to get rid of the zombie channel, which returned without error however still encountering the same errors when running lncli feereport ([lncli] rpc error: code = Unknown desc = no policy for outgoing channel 652233596219424769). Appears to be related to issue #2911 Patch used to get node to start-up successfully: |
That seems to be an issue with the |
Background
Attempted to run "lncli feereport" on node yesterday and ran into an error where it said "rpc error: code = Unknown desc = no policy for outgoing channel x". Could not find the channel in "lncli listchannels" but checking "lncli getchaninfo" I saw the channel with both policies as "null". I then tried to force close and got the response "channel is already being closed". Running "lncli pendingchannels" I saw the channel in waiting to be closed.
Thinking a reboot might help the situation, I restarted both lnd and bitcoind however upon restart, lnd starts up but then crashes with the error: "Unable to start server: -26: bad-txns-in-belowout, value in (x) < value out (x) (code 16)".
Every time I restart the node I get this same error now so can't even get into my node to try to replicate the original "lncli feereport" error.
Your environment
lnd: lnd version 0.7.0-beta commit=v0.7.0-beta-93-g377b7bf3ce493690fadc9d7be062062b006074c9
OS: Linux 4.15.0-60-generic #67-Ubuntu SMP Thu Aug 22 16:55:30 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
Bitcoind: Bitcoin Core Daemon version v0.17.1.0-gef70f9b52b851c7997a9f1a0834714e3eebc1fd8
Steps to reproduce
Starting LND (using supervisor - sudo supervisorctl start lnd)
Expected behaviour
LND should start normally
Actual behaviour
LND starts but shortly after I unlock it crashes, requiring unlock again.
Logs:
2019-09-06 15:24:23.858 [ERR] CNCT: ChannelArbitrator(x:1): unable to broadcast close tx: -26: bad-txns-in-belowout, value in (x) < value out (x) (code 16)
2019-09-06 15:24:23.858 [ERR] CNCT: ChannelArbitrator(x:1): unable to advance state: -26: bad-txns-in-belowout, value in (x) < value out (x) (code 16)
2019-09-06 15:24:23.863 [ERR] CNCT: ChannelArbitrator(x:0): unable to progress resolver: quitting
2019-09-06 15:24:23.866 [ERR] LTND: Unable to start server: -26: bad-txns-in-belowout, value in (x) < value out (x) (code 16)
2019-09-06 15:24:23.866 [INF] RPCS: Stopping RPC Server
2019-09-06 15:24:24.941 [INF] RPCS: password gRPC proxy started at 0.0.0.0:8080
2019-09-06 15:24:24.941 [INF] RPCS: password RPC server listening on 127.0.0.1:10009
2019-09-06 15:25:50.431 [INF] LTND: Received terminated
2019-09-06 15:25:50.432 [ERR] LTND: Unable to set up wallet password listeners: shutting down
The text was updated successfully, but these errors were encountered: