Entries in log: **BROKEN** Cannot broadcast our commitment tx: it's invalid! (ancient channel?)

[freerko]

Hi,

I am running a very old c-lightning instance with the current 25.02 version. I noticed two BROKEN entries in the logfile but couldn't find any issue here regarding that error message:

2025-03-18T12:54:45.329Z BROKEN 034a5fdb2df3ce1bfd2c2aca205ce9cfeef1a5f4af21b0b5e81c453080c30d7683-chan#34: Cannot broadcast our commitment tx: it's invalid! (ancient channel?)

2025-03-18T12:54:45.329Z BROKEN 03dbe3fedd4f6e7f7020c69e6d01453d5a69f9faa1382901cf3028f1e997ef2814-chan#63: Cannot broadcast our commitment tx: it's invalid! (ancient channel?)

With lightning-cli listpeerchannels, both have the status AWAITING_UNILATERAL and the peers are not connected. Both funding_txids happened more than 7 years ago and local_funds_msat is 0 for both. When I run lightning-cli close on those peer-ids I get "Peer has no active channel".

How can I analyze this further and fix it or get rid of it?

[rustyrussell]

Yes, you can dev-forget-channel for those. You'll need to enable developer mode, but it will get rid of the messages.