Terminal server shuts down from hash error

[gkrizek]

I have a node that is running Litd with everything integrated (lnd, loop, pool, faraday). One day I noticed that litd was still running but LNC sessions weren't working. After investigation, I found that litd and LND were still running but the Terminal Server (for LNC), Loop, Pool, and Faraday were all shut down. After looking at the logs I found the reason for the shutdown:

2023-08-22 00:04:06.413 [ERR] CHDB: unable to fetch amp htlcs for inv [0 0 0 86] and setIDs [0x40048c9f00]: %!w(*errors.errorString=&{unable to locate invoice})
2023-08-22 00:04:06.413 [ERR] ACCT: Error in invoice subscription: invalid hash length of 0, want 32
2023-08-22 00:04:06.413 [ERR] LITD: Received critical error from subsystem, shutting down: invalid hash length of 0, want 32

Expected behavior

No process in Litd should shut down because of this error. I believe that this error should be caught and returned in the APIs, but it's not a fatal error that would shut down the server.

Actual behavior

It shuts down some subservers

To reproduce

I don't know exactly how to replicate this. This is a user's node and I don't have all the information into what they do. They did say they never use the APIs directly, rather use things like Zeus, Thunderhub, and lncli. I'm not sure the exactly API call or function to cause this.

System information

litd 0.10.4