lightning icon indicating copy to clipboard operation
lightning copied to clipboard

channel updates and node announcements not propagating

Open JssDWt opened this issue 4 months ago • 10 comments

Issue and Steps to Reproduce

lightningd appears to fail to propagate its own channel updates through the network. Yesterday, one of our nodes hadn't sent out a channel update or node announcement in over 22 days. This corresponds with the latest restart of the node. So it appears gossip is only exchanged when the node is restarted. During this period there were several updates made to channel policies, but they also had not been propagated through the network. Today the node was restarted and (some, but not all) gossip made it to other nodes.

I need some guidance how to troubleshoot this issue.

  • Which logs should I look for?
  • In which places in the codebase can I add logs to make it easier to troubleshoot?
  • Are there settings we can use to increase gossip propagation?

getinfo output

{
   "id": "redacted",
   "alias": "redacted",
   "color": "redacted",
   "num_peers": 25,
   "num_pending_channels": 0,
   "num_active_channels": 31,
   "num_inactive_channels": 1,
   "address": [redacted],
   "binding": [redacted],
   "version": "v24.02.1",
   "blockheight": 840822,
   "network": "bitcoin",
   "fees_collected_msat": redacted,
   "lightning-dir": "redacted",
   "our_features": {
      "init": "08a0000a8a5961",
      "node": "88a0000a8a5961",
      "channel": "",
      "invoice": "02000002024100"
   }
}

JssDWt avatar Apr 25 '24 12:04 JssDWt