You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A few days ago, I noticed I was getting the following when running lncli feereport:
lncli feereport
[lncli] rpc error: code = Unknown desc = no policy for outgoing channel XXXXX
I found the channel by running listchannels, but looked like it was an old one (now offline). For some reason, I recall finding disparities between local balance and channel size when inspecting the channel itself by id (If I recall right, the balance was something like ~60000 sats, but I'm not sure), as opposed to when running listchannels, that returned a bigger value.
Anyway, It could not be closed, so I tried force-closing it (maybe I shouldn't have done that?)
After a couple of days, the node went down, and it won't start anymore:
unable to start server: unmatched backend error: -26: bad-txns-in-belowout, value in (0.0006) < value out (0.09995071) (code 16)
Uh oh!
There was an error while loading. Please reload this page.
Background
A few days ago, I noticed I was getting the following when running
lncli feereport
:I found the channel by running
listchannels
, but looked like it was an old one (now offline). For some reason, I recall finding disparities between local balance and channel size when inspecting the channel itself by id (If I recall right, the balance was something like ~60000 sats, but I'm not sure), as opposed to when runninglistchannels
, that returned a bigger value.Anyway, It could not be closed, so I tried force-closing it (maybe I shouldn't have done that?)
After a couple of days, the node went down, and it won't start anymore:
The channel itself still appears on
waiting_close_channels
, if I get to run that command before the node stops:Your environment
0.11.0-beta
Steps to reproduce
The node won't start, it exits after unlocking.
The text was updated successfully, but these errors were encountered: