[bug]: received critical error from sub-server

[youngzhenhao]

Background

Tapd of litd often crashes because this error occurs, so I have to restart litd, but usually after running it for a while, about a day or so, the error reappears:

"taproot-assets": {
            "disabled": false,
            "running": false,
            "error": "received critical error from sub-server (taproot-assets), shutting down: unable to receive proof using courier: error fetching proof provenance: fetching single proof failed: proof backoff receive attempt has failed: unable to log proof delivery attempt: unknown sqlite error: interrupted (9)",
            "custom_status": ""
        }

Your environment

litd version 0.14.0-alpha commit=v0.14.0-alpha
Linux 5.15.0-107-generic #117-Ubuntu SMP Fri Apr 26 12:26:49 UTC 2024 x86_64
Bitcoin Core version v25.0.0

logs before and after restarting

lnd.log

[guggero]

Thanks for the report and the logs. So I think the tapd SQLite database is simply overloaded, which leads to certain requests being interrupted.

I see the following things in the log:

• unable to fetch roots for universe sync: missing universe id: That's a bug we fixed in the latest version. Please update to litd v0.14.1-alpha that was just released yesterday.
• unable to sync universe: sync is already in progress, please wait for it to finish: Syncs are stacking up. That might be a follow-up error from the above.
• There are a LOT of requests to /taprpc.TaprootAssets/ListTransfers, often more than 10 in a row, within just a couple of milli-seconds. Is that an application of yours? If yes, try to make fewer requests. You're basically hammering the database.