[bug]: [ERR] NANN: Unable to retrieve chan status for Channel -s since update to v0.20.0 on postgres

[openoms]

Pre-Submission Checklist

• I have searched the existing issues and believe this is a new bug.
• I am not asking a question about how to use lnd, but reporting a bug (otherwise open a discussion).

LND Version

v0.20.0-beta

LND Configuration

db.use-native-sql=true
bitcoind.rpcpass=passxxxx
db.backend=postgres
db.postgres.dsn=postgres://user:pass@xx.xx.x.x:5432/lnd
db.postgres.timeout=0
db.postgres.maxconnections=50
restlisten=0.0.0.0:8080
rpclisten=0.0.0.0:10009
listen=0.0.0.0:9735
prometheus.listen=0.0.0.0:9092
bitcoin.node=bitcoind
bitcoind.rpcuser=rpcuser
bitcoind.zmqpubrawblock=tcp://bitcoind:28332
bitcoind.zmqpubrawtx=tcp://bitcoind:28333
tlsextradomain=lnd
accept-keysend=1
allow-circular-route=1
stagger-initial-reconnect=1
protocol.wumbo-channels=1
maxchansize=500000000
bitcoin.timelockdelta=60
default-remote-max-htlcs=50
debuglevel=info
prometheus.enable=1
gc-canceled-invoices-on-the-fly=true
gc-canceled-invoices-on-startup=true
tor.active=true
tor.v3=true
tor.skip-proxy-for-clearnet-targets=true
bitcoind.rpchost=bitcoind:8332
bitcoin.basefee=0
bitcoin.feerate=1000
max-commit-fee-rate-anchors=100
bitcoind.zmqpubrawblock=tcp://bitcoind:28332
bitcoind.zmqpubrawtx=tcp://bitcoind:28333
alias=xxxx
minchansize=10000000
bitcoin.mainnet=true

Backend Version

Bitcoin Core 28.0

Backend Configuration

debug=mempool
debug=rpc
shrinkdebugfile=1
server=1
txindex=1
printtoconsole=1
rpcuser=xxx
rpcpassword=xxx
zmqpubrawtx=tcp://0.0.0.0:28333
zmqpubrawblock=tcp://0.0.0.0:28332
blockfilterindex=1
dbcache=2048
maxmempool=512
rpcworkqueue=128
mainnet=1

OS/Distribution

lightninglabs lnd container in K8s

Bug Details & Steps to Reproduce

Found out when bos peers stopped working with

edge not found

errors after the update to LND v0.20.0-beta.

lncli listchannels show the channels as active.

Expected Behavior

Channels should show up.

Debug Information

2025-12-01 20:09:22.200 [ERR] NANN: Unable to retrieve chan status for Channel(196f058ae8d244a5be3e4fe4b5563406fef30fa24825dd7f528c7506ff36835a:1): could not fetch channel: edge not found
2025-12-01 20:09:22.202 [ERR] NANN: Unable to retrieve chan status for Channel(6b9e46118b49b9120a4423cc5bef50475217681de1fe3f1404e1b40e2d665f7d:0): could not fetch channel: edge not found
2025-12-01 20:09:22.204 [ERR] NANN: Unable to retrieve chan status for Channel(196f058ae8d244a5be3e4fe4b5563406fef30fa24825dd7f528c7506ff36835a:2): could not fetch channel: edge not found
2025-12-01 20:09:22.207 [ERR] NANN: Unable to retrieve chan status for Channel(af73bba2a00dcc6b5e6d22b6b6c59948c75cb880b7a1c5de5df0a8319b99e7b7:1): could not fetch channel: edge not found
2025-12-01 20:09:22.209 [ERR] NANN: Unable to retrieve chan status for Channel(6b9e46118b49b9120a4423cc5bef50475217681de1fe3f1404e1b40e2d665f7d:1): could not fetch channel: edge not found
2025-12-01 20:09:22.212 [ERR] NANN: Unable to retrieve chan status for Channel(196f058ae8d244a5be3e4fe4b5563406fef30fa24825dd7f528c7506ff36835a:3): could not fetch channel: edge not found
2025-12-01 20:09:22.213 [ERR] NANN: Unable to retrieve chan status for Channel(870112b937e44d023e22cdca352daf908e9f4b149afdd4e48ef2638f1c5860a7:4): could not fetch channel: edge not found
2025-12-01 20:09:22.214 [ERR] NANN: Unable to retrieve chan status for Channel(a3131b0014ebc9184d3697facd50b4b3dfd68fccf1148cf0ebc833ed73c11dc6:1): could not fetch channel: edge not found
2025-12-01 20:09:22.215 [ERR] NANN: Unable to retrieve chan status for Channel(d77290ad97775b15f2f23e5cea49b785ccb172bc5608ef8f6913be6947da10c6:0): could not fetch channel: edge not found
2025-12-01 20:09:22.215 [ERR] NANN: Unable to retrieve chan status for Channel(6b9e46118b49b9120a4423cc5bef50475217681de1fe3f1404e1b40e2d665f7d:2): could not fetch channel: edge not found
2025-12-01 20:09:22.216 [ERR] NANN: Unable to retrieve chan status for Channel(69d5b6db12ff4177a49783c66785df6824fcad62b9639bd9a46acd053a42801c:1): could not fetch channel: edge not found
2025-12-01 20:10:22.284 [ERR] NANN: Unable to retrieve chan status for Channel(196f058ae8d244a5be3e4fe4b5563406fef30fa24825dd7f528c7506ff36835a:1): could not fetch channel: edge not found
2025-12-01 20:10:22.287 [ERR] NANN: Unable to retrieve chan status for Channel(6b9e46118b49b9120a4423cc5bef50475217681de1fe3f1404e1b40e2d665f7d:0): could not fetch channel: edge not found
2025-12-01 20:10:22.290 [ERR] NANN: Unable to retrieve chan status for Channel(196f058ae8d244a5be3e4fe4b5563406fef30fa24825dd7f528c7506ff36835a:2): could not fetch channel: edge not found
2025-12-01 20:10:22.293 [ERR] NANN: Unable to retrieve chan status for Channel(af73bba2a00dcc6b5e6d22b6b6c59948c75cb880b7a1c5de5df0a8319b99e7b7:1): could not fetch channel: edge not found
2025-12-01 20:10:22.296 [ERR] NANN: Unable to retrieve chan status for Channel(6b9e46118b49b9120a4423cc5bef50475217681de1fe3f1404e1b40e2d665f7d:1): could not fetch channel: edge not found
2025-12-01 20:10:22.300 [ERR] NANN: Unable to retrieve chan status for Channel(196f058ae8d244a5be3e4fe4b5563406fef30fa24825dd7f528c7506ff36835a:3): could not fetch channel: edge not found
2025-12-01 20:10:22.301 [ERR] NANN: Unable to retrieve chan status for Channel(870112b937e44d023e22cdca352daf908e9f4b149afdd4e48ef2638f1c5860a7:4): could not fetch channel: edge not found
2025-12-01 20:10:22.303 [ERR] NANN: Unable to retrieve chan status for Channel(a3131b0014ebc9184d3697facd50b4b3dfd68fccf1148cf0ebc833ed73c11dc6:1): could not fetch channel: edge not found
2025-12-01 20:10:22.304 [ERR] NANN: Unable to retrieve chan status for Channel(d77290ad97775b15f2f23e5cea49b785ccb172bc5608ef8f6913be6947da10c6:0): could not fetch channel: edge not found
2025-12-01 20:10:22.305 [ERR] NANN: Unable to retrieve chan status for Channel(6b9e46118b49b9120a4423cc5bef50475217681de1fe3f1404e1b40e2d665f7d:2): could not fetch channel: edge not found
2025-12-01 20:10:22.306 [ERR] NANN: Unable to retrieve chan status for Channel(69d5b6db12ff4177a49783c66785df6824fcad62b9639bd9a46acd053a42801c:1): could not fetch channel: edge not found

Environment

k8s deployment with https://github.com/blinkbitcoin/charts/tree/main/charts/lnd

[ziggie1984]

have you tried a restart, we fixed a big in this area see: #10378

[ziggie1984]

do you see the channels when you query for it via lncli getchaninfo ...

[openoms]

have you tried a restart, we fixed a big in this area see: #10378

yes, the node has been restarted multiple times with no change in this issue

do you see the channels when you query for it via lncli getchaninfo ...

It is similar for all the listed channels:

lncli getchaninfo --chan_point 196f058ae8d244a5be3e4fe4b5563406fef30fa24825dd7f528c7506ff36835a:1
{
    "channel_id":  "1017489159958298625",
    "chan_point":  "196f058ae8d244a5be3e4fe4b5563406fef30fa24825dd7f528c7506ff36835a:1",
    "last_update":  0,
    "node1_pub":  "021294fff596e497ad2902cd5f19673e9020953d90625d68c22e91b51a45c032d3",
    "node2_pub":  "02dfb4c1dd59216fa6a28d0f012e188516f63517db68c4e4b82c3af41343a05bc4",
    "capacity":  "15000000",
    "node1_policy":  null,
    "node2_policy":  null,
    "custom_records":  {},
    "auth_proof":  null
}

Got more errors when tried running for the missing edges listed in the logs:

# Channel 1 - capacity 15000000 sats → max_htlc 14850000000 msat
lncli updatechanpolicy --chan_point 196f058ae8d244a5be3e4fe4b5563406fef30fa24825dd7f528c7506ff36835a:1 --create_missing_edge --base_fee_msat 0 --fee_rate_ppm 1000 --time_lock_delta 60 --min_htlc_msat 1000 --max_htlc_msat 14850000000

# Channel 2 - capacity 15000000 sats → max_htlc 14850000000 msat
lncli updatechanpolicy --chan_point 196f058ae8d244a5be3e4fe4b5563406fef30fa24825dd7f528c7506ff36835a:2 --create_missing_edge --base_fee_msat 0 --fee_rate_ppm 1000 --time_lock_delta 60 --min_htlc_msat 1000 --max_htlc_msat 14850000000

logs | grep -i "edge\|policy\|error"

2025-12-01 22:39:19.532 [WRN] LCHN: Missing edge for active channel (196f058ae8d244a5be3e4fe4b5563406fef30fa24825dd7f528c7506ff36835a:1) during policy update. Recreating edge with default policy.
2025-12-01 22:39:19.542 [ERR] LCHN: Attempt to add missing edge for channel (196f058ae8d244a5be3e4fe4b5563406fef30fa24825dd7f528c7506ff36835a:1) errored with: expected the funding transaction script to be set
2025-12-01 22:39:19.727 [WRN] LCHN: Missing edge for active channel (196f058ae8d244a5be3e4fe4b5563406fef30fa24825dd7f528c7506ff36835a:2) during policy update. Recreating edge with default policy.
2025-12-01 22:39:19.791 [ERR] LCHN: Attempt to add missing edge for channel (196f058ae8d244a5be3e4fe4b5563406fef30fa24825dd7f528c7506ff36835a:2) errored with: expected the funding transaction script to be set
2025-12-01 22:39:19.963 [WRN] LCHN: Missing edge for active channel (196f058ae8d244a5be3e4fe4b5563406fef30fa24825dd7f528c7506ff36835a:3) during policy update. Recreating edge with default policy.
2025-12-01 22:39:20.070 [ERR] LCHN: Attempt to add missing edge for channel (196f058ae8d244a5be3e4fe4b5563406fef30fa24825dd7f528c7506ff36835a:3) errored with: expected the funding transaction script to be set
2025-12-01 22:39:20.176 [WRN] LCHN: Missing edge for active channel (6b9e46118b49b9120a4423cc5bef50475217681de1fe3f1404e1b40e2d665f7d:0) during policy update. Recreating edge with default policy.
2025-12-01 22:39:20.225 [ERR] LCHN: Attempt to add missing edge for channel (6b9e46118b49b9120a4423cc5bef50475217681de1fe3f1404e1b40e2d665f7d:0) errored with: expected the funding transaction script to be set
2025-12-01 22:39:20.351 [WRN] LCHN: Missing edge for active channel (6b9e46118b49b9120a4423cc5bef50475217681de1fe3f1404e1b40e2d665f7d:1) during policy update. Recreating edge with default policy.
2025-12-01 22:39:20.411 [ERR] LCHN: Attempt to add missing edge for channel (6b9e46118b49b9120a4423cc5bef50475217681de1fe3f1404e1b40e2d665f7d:1) errored with: expected the funding transaction script to be set
2025-12-01 22:39:20.564 [WRN] LCHN: Missing edge for active channel (6b9e46118b49b9120a4423cc5bef50475217681de1fe3f1404e1b40e2d665f7d:2) during policy update. Recreating edge with default policy.
2025-12-01 22:39:20.677 [ERR] LCHN: Attempt to add missing edge for channel (6b9e46118b49b9120a4423cc5bef50475217681de1fe3f1404e1b40e2d665f7d:2) errored with: expected the funding transaction script to be set
2025-12-01 22:39:20.789 [WRN] LCHN: Missing edge for active channel (af73bba2a00dcc6b5e6d22b6b6c59948c75cb880b7a1c5de5df0a8319b99e7b7:1) during policy update. Recreating edge with default policy.
2025-12-01 22:39:20.852 [ERR] LCHN: Attempt to add missing edge for channel (af73bba2a00dcc6b5e6d22b6b6c59948c75cb880b7a1c5de5df0a8319b99e7b7:1) errored with: expected the funding transaction script to be set
2025-12-01 22:39:21.003 [WRN] LCHN: Missing edge for active channel (870112b937e44d023e22cdca352daf908e9f4b149afdd4e48ef2638f1c5860a7:4) during policy update. Recreating edge with default policy.
2025-12-01 22:39:21.102 [ERR] LCHN: Attempt to add missing edge for channel (870112b937e44d023e22cdca352daf908e9f4b149afdd4e48ef2638f1c5860a7:4) errored with: expected the funding transaction script to be set
2025-12-01 22:39:21.253 [WRN] LCHN: Missing edge for active channel (a3131b0014ebc9184d3697facd50b4b3dfd68fccf1148cf0ebc833ed73c11dc6:1) during policy update. Recreating edge with default policy.
2025-12-01 22:39:21.345 [ERR] LCHN: Attempt to add missing edge for channel (a3131b0014ebc9184d3697facd50b4b3dfd68fccf1148cf0ebc833ed73c11dc6:1) errored with: expected the funding transaction script to be set
2025-12-01 22:39:21.505 [WRN] LCHN: Missing edge for active channel (d77290ad97775b15f2f23e5cea49b785ccb172bc5608ef8f6913be6947da10c6:0) during policy update. Recreating edge with default policy.
2025-12-01 22:39:21.610 [ERR] LCHN: Attempt to add missing edge for channel (d77290ad97775b15f2f23e5cea49b785ccb172bc5608ef8f6913be6947da10c6:0) errored with: expected the funding transaction script to be set
2025-12-01 22:39:22.209 [ERR] NANN: Unable to retrieve chan status for Channel(69d5b6db12ff4177a49783c66785df6824fcad62b9639bd9a46acd053a42801c:1): could not fetch channel: edge not found
2025-12-01 22:39:28.816 [ERR] HSWC: Unhandled error while reforwarding htlc settle/fail over htlcswitch: insufficient bandwidth to route htlc
2025-12-01 22:39:46.625 [ERR] LCHN: Got nil channel edge policy when updating a channel. Channel point: 196f058ae8d244a5be3e4fe4b5563406fef30fa24825dd7f528c7506ff36835a:1
2025-12-01 22:39:46.680 [ERR] LCHN: Got nil channel edge policy when updating a channel. Channel point: 196f058ae8d244a5be3e4fe4b5563406fef30fa24825dd7f528c7506ff36835a:2
2025-12-01 22:39:46.736 [ERR] LCHN: Got nil channel edge policy when updating a channel. Channel point: 196f058ae8d244a5be3e4fe4b5563406fef30fa24825dd7f528c7506ff36835a:3
2025-12-01 22:39:46.791 [ERR] LCHN: Got nil channel edge policy when updating a channel. Channel point: 6b9e46118b49b9120a4423cc5bef50475217681de1fe3f1404e1b40e2d665f7d:0
2025-12-01 22:39:46.846 [ERR] LCHN: Got nil channel edge policy when updating a channel. Channel point: 6b9e46118b49b9120a4423cc5bef50475217681de1fe3f1404e1b40e2d665f7d:1
2025-12-01 22:39:46.900 [ERR] LCHN: Got nil channel edge policy when updating a channel. Channel point: 6b9e46118b49b9120a4423cc5bef50475217681de1fe3f1404e1b40e2d665f7d:2
2025-12-01 22:39:46.956 [ERR] LCHN: Got nil channel edge policy when updating a channel. Channel point: af73bba2a00dcc6b5e6d22b6b6c59948c75cb880b7a1c5de5df0a8319b99e7b7:1
2025-12-01 22:39:47.015 [ERR] LCHN: Got nil channel edge policy when updating a channel. Channel point: 870112b937e44d023e22cdca352daf908e9f4b149afdd4e48ef2638f1c5860a7:4
2025-12-01 22:39:47.072 [ERR] LCHN: Got nil channel edge policy when updating a channel. Channel point: a3131b0014ebc9184d3697facd50b4b3dfd68fccf1148cf0ebc833ed73c11dc6:1
2025-12-01 22:39:47.128 [ERR] LCHN: Got nil channel edge policy when updating a channel. Channel point: d77290ad97775b15f2f23e5cea49b785ccb172bc5608ef8f6913be6947da10c6:0
2025-12-01 22:39:47.451 [WRN] LCHN: Missing edge for active channel (69d5b6db12ff4177a49783c66785df6824fcad62b9639bd9a46acd053a42801c:1) during policy update. Recreating edge with default policy.
2025-12-01 22:39:47.624 [ERR] LCHN: Attempt to add missing edge for channel (69d5b6db12ff4177a49783c66785df6824fcad62b9639bd9a46acd053a42801c:1) errored with: expected the funding transaction script to be set
2025-12-01 22:40:26.367 [ERR] HSWC: Unhandled error while reforwarding htlc settle/fail over htlcswitch: insufficient bandwidth to route htlc

[openoms]

Update:
bos peers
started working after running the commands above, but the lncli getchaninfo results still look the same.

bos fees does error still:

err: 
  - 503
  - GetFeeReportError
  - 
    err: 
      message: 2 UNKNOWN: 
      stack: 
        - Error: 2 UNKNOWN: 
        -     at callErrorFromStatus (/usr/lib/node_modules/balanceofsatoshis/node_modules/lightning/node_modules/@grpc/grpc-js/build/src/call.js:32:19)
        -     at Object.onReceiveStatus (/usr/lib/node_modules/balanceofsatoshis/node_modules/lightning/node_modules/@grpc/grpc-js/build/src/client.js:193:76)
        -     at Object.onReceiveStatus (/usr/lib/node_modules/balanceofsatoshis/node_modules/lightning/node_modules/@grpc/grpc-js/build/src/client-interceptors.js:361:141)
        -     at Object.onReceiveStatus (/usr/lib/node_modules/balanceofsatoshis/node_modules/lightning/node_modules/@grpc/grpc-js/build/src/client-interceptors.js:324:181)
        -     at /usr/lib/node_modules/balanceofsatoshis/node_modules/lightning/node_modules/@grpc/grpc-js/build/src/resolving-call.js:135:78
        -     at process.processTicksAndRejections (node:internal/process/task_queues:77:11)
        - for call at
        -     at ServiceClientImpl.makeUnaryRequest (/usr/lib/node_modules/balanceofsatoshis/node_modules/lightning/node_modules/@grpc/grpc-js/build/src/client.js:161:32)
        -     at ServiceClientImpl.<anonymous> (/usr/lib/node_modules/balanceofsatoshis/node_modules/lightning/node_modules/@grpc/grpc-js/build/src/make-client.js:105:19)
        -     at asyncAuto.getFeeReport (/usr/lib/node_modules/balanceofsatoshis/node_modules/lightning/lnd_methods/offchain/get_fee_rates.js:47:33)
        -     at runTask (/usr/lib/node_modules/balanceofsatoshis/node_modules/async/auto.js:293:13)
        -     at /usr/lib/node_modules/balanceofsatoshis/node_modules/async/auto.js:233:31
        -     at processQueue (/usr/lib/node_modules/balanceofsatoshis/node_modules/async/auto.js:243:13)
        -     at taskComplete (/usr/lib/node_modules/balanceofsatoshis/node_modules/async/auto.js:259:9)
        -     at /usr/lib/node_modules/balanceofsatoshis/node_modules/async/auto.js:286:17
        -     at /usr/lib/node_modules/balanceofsatoshis/node_modules/async/internal/onlyOnce.js:12:16
        -     at validate (/usr/lib/node_modules/balanceofsatoshis/node_modules/lightning/lnd_methods/offchain/get_fee_rates.js:42:16)
        -     at runTask (/usr/lib/node_modules/balanceofsatoshis/node_modules/async/auto.js:295:13)
        -     at /usr/lib/node_modules/balanceofsatoshis/node_modules/async/auto.js:233:31
        -     at processQueue (/usr/lib/node_modules/balanceofsatoshis/node_modules/async/auto.js:243:13)
        -     at auto (/usr/lib/node_modules/balanceofsatoshis/node_modules/async/auto.js:230:5)
        -     at /usr/lib/node_modules/balanceofsatoshis/node_modules/lightning/lnd_methods/offchain/get_fee_rates.js:35:12
        -     at new Promise (<anonymous>)

lnd logs:

2025-12-01 22:57:28.360 [ERR] RPCS: [/lnrpc.Lightning/FeeReport]: no policy for outgoing channel 1017488060494774273 
2025-12-01 22:57:39.626 [ERR] RPCS: [/lnrpc.Lightning/FeeReport]: no policy for outgoing channel 1017488060494774273 

Restarted the node, but still showing those 11 channels without policy:

k -n blink-routing-routing  logs  -f  lnd1-0 -c lnd |  grep -i "edge\|policy\|error"
2025-12-01 23:03:19.840 [ERR] DISC: Unable to rebroadcast stale announcements: unable to retrieve outgoing channels: channel from self node has no policy
2025-12-01 23:03:23.035 [WRN] SRVR: No channel policy found for ChannelPoint(69d5b6db12ff4177a49783c66785df6824fcad62b9639bd9a46acd053a42801c:1): 
2025-12-01 23:03:23.087 [WRN] SRVR: No channel policy found for ChannelPoint(196f058ae8d244a5be3e4fe4b5563406fef30fa24825dd7f528c7506ff36835a:3): 
2025-12-01 23:03:23.088 [WRN] SRVR: No channel policy found for ChannelPoint(6b9e46118b49b9120a4423cc5bef50475217681de1fe3f1404e1b40e2d665f7d:0): 
2025-12-01 23:03:23.090 [WRN] SRVR: No channel policy found for ChannelPoint(6b9e46118b49b9120a4423cc5bef50475217681de1fe3f1404e1b40e2d665f7d:1): 
2025-12-01 23:03:23.092 [WRN] SRVR: No channel policy found for ChannelPoint(6b9e46118b49b9120a4423cc5bef50475217681de1fe3f1404e1b40e2d665f7d:2): 
2025-12-01 23:03:23.093 [WRN] SRVR: No channel policy found for ChannelPoint(af73bba2a00dcc6b5e6d22b6b6c59948c75cb880b7a1c5de5df0a8319b99e7b7:1): 
2025-12-01 23:03:23.095 [WRN] SRVR: No channel policy found for ChannelPoint(870112b937e44d023e22cdca352daf908e9f4b149afdd4e48ef2638f1c5860a7:4): 
2025-12-01 23:03:23.097 [WRN] SRVR: No channel policy found for ChannelPoint(a3131b0014ebc9184d3697facd50b4b3dfd68fccf1148cf0ebc833ed73c11dc6:1): 
2025-12-01 23:03:23.098 [WRN] SRVR: No channel policy found for ChannelPoint(d77290ad97775b15f2f23e5cea49b785ccb172bc5608ef8f6913be6947da10c6:0): 
2025-12-01 23:03:23.106 [WRN] SRVR: No channel policy found for ChannelPoint(196f058ae8d244a5be3e4fe4b5563406fef30fa24825dd7f528c7506ff36835a:1): 
2025-12-01 23:03:23.108 [WRN] SRVR: No channel policy found for ChannelPoint(196f058ae8d244a5be3e4fe4b5563406fef30fa24825dd7f528c7506ff36835a:2): 2025-12-01 23:09:19.064 [ERR] HSWC: Unhandled error while reforwarding htlc settle/fail over htlcswitch: insufficient bandwidth to route htlc
2025-12-01 23:09:49.665 [ERR] HSWC: Unhandled error while reforwarding htlc settle/fail over htlcswitch: insufficient bandwidth to route htlc

[ziggie1984]

cc @ellemouton

[openoms]

Fixed only by closing two channels.
Looking at the getchaninfo output for the remaining errored chanels node1_policy or node2_policy is still null:

Channel	Own Node Position	Own Policy
:1 (196f...)	node2_pub	null
:0 (6b9e...)	node2_pub	null
:2 (6b9e...)	node1_pub	null
:1 (af73...)	node1_pub	null
:4 (8701...)	node1_pub	null
:1 (a313...)	node1_pub	null
:0 (d772...)	node1_pub	null
:1 (69d5...)	node1_pub	null

Running updatechanpolicy for the channels with missing policies results in:

lncli updatechanpolicy --chan_point 196f058ae8d244a5be3e4fe4b5563406fef30fa24825dd7f528c7506ff36835a:1 --base_fee_msat 0 --fee_rate_ppm 1000 --time_lock_delta 60 --min_htlc_msat 1000 --max_htlc_msat 148500000
00
{
    "failed_updates": [
        {
            "outpoint": "196f058ae8d244a5be3e4fe4b5563406fef30fa24825dd7f528c7506ff36835a:1",
            "reason": "UPDATE_FAILURE_NOT_FOUND",
            "update_error": "edge policy not found"
        }
    ]
}

[openoms]

Could chantools dropchannelgraph be used here at all (given the postgres database)?

Adding some analyses made with Claude Opus 4.5 in case it is useful:

Root Cause Analysis

There are two bugs in lnd/routing/localchans/manager.go:

Bug 1: Missing code path for "edge exists but policy is nil"

The processChan function (lines 87-150) only handles:

1. Edge found with policy → update it ✓
2. Edge not found → try createMissingEdge (if flag set) ✓

Missing case: Edge found but own policy is nil → no code to create the policy!

When ForAllOutgoingChannels finds the channel but the policy is nil, it fails with:

Got nil channel edge policy when updating a channel

The --create_missing_edge flag only triggers when the channel is NOT found in the first pass. Since the edge exists, the channel IS found, so createMissingEdge is never called.

Bug 2: FundingScript not set in createEdge

When --create_missing_edge does try to recreate a missing edge (when edge is truly missing), it creates a ChannelEdgeInfo but never sets the FundingScript field:

info := &models.ChannelEdgeInfo{
    ChannelID:    shortChanID.ToUint64(),
    ChainHash:    channel.ChainHash,
    Features:     lnwire.EmptyFeatureVector(),
    Capacity:     channel.Capacity,
    ChannelPoint: channel.FundingOutpoint,
    // FundingScript is NOT set!
}

When AddEdge is called in lnd/graph/builder.go (line 1064), it tries to unwrap FundingScript:

fundingPkScript, err := edge.FundingScript.UnwrapOrErr(fmt.Errorf(
    "expected the funding transaction script to be set",
))

The Fix

1. Bug 1 fix: In processChan, when edge == nil, instead of just failing, call createMissingEdge to create the policy (not just the edge).

2. Bug 2 fix: In createEdge, derive and set the FundingScript using the channel's multisig keys. Similar logic exists in:

   • lnd/funding/manager.go:makeFundingScript()
   • lnd/contractcourt/chain_watcher.go:deriveFundingPkScript()

[ellemouton]

@openoms - do you still have the logs from the first start-up with 0.20? (ie, the startup showing the migration logs) wondering if any warnings appeared there