[Bug]: "Unable to fetch transaction" log spam on LN log when starting up Server

What is your BTCPay version?

I’m running the latest version BTCPay Server v1.9.2+6193835ea.

How did you deploy BTCPay Server?

Docker installation

What happened?

After the upgrade to BTCPay Server v1.9.2+6193835ea, the LND log is filled with this errors:

2023-04-28 20:03:59.331 [ERR] LNWL: unable to fetch transaction xxxxxxxxxxx for mempool: -5: No such mempool transaction. Use -txindex or provide a block hash to enable blockchain transaction queries. Use gettransaction for wallet transactions.

Hundreds of them.

When the node is finished starting up, RPC is up and running, then the error ceases for a while, but then resumes with less TX’s ( currently 5).

I’m running the server with a Pruned node.

Is this normal behavior, and if so, why? May this be because my LN opening channel TX’s are old enough to have fallen outside of the blockchain window set in the PRUNE window?

How did you encounter this bug?

Checked Logs

Relevant log output

2023-04-28 20:14:53.258 [ERR] LNWL: unable to fetch transaction xxxxxxxxxxxx from mempool: -5: No such mempool transaction. Use -txindex or provide a block hash to enable blockchain transaction queries. Use gettransaction for wallet transactions.

What browser do you use?

Any

Additional information

N/a

Are you sure this is a bug report?

• I confirm this is a bug report

[pavlenex]

I believe this one got resolved after we bumped to lnd 0.16.2-beta if not, let us know and we will re-open. Thanks for reporting.

[Goro2030]

It is not fully resolved, but the log spam went from hundreds of “unable to fetch transaction” errors, which was trashing the disk, to 4 log entries. So I can call this solved!