I’m mostly thinking that there must be something that happens to make the errors start. You’re getting an 802, which is an “Unable to open file” error. This means presumably that the database server is borked, there is a network issue, or any number of other reasons that there could be an 802 error.
One thing to confirm, are you getting an 802 if you try this from outside of OttoFMS? ie. if you make a data api request without using ottofms api tokens does it also give you an 802 error? There’s nothing happening from the OttoFMS side that makes the requests different across time, and I can’t think of any way that OttoFMS could cause an 802 error.
@kduval It looks like something was indeed happening. It seems having the flush cache schedule script from SimpleQ eventually overlap with a nightly DBVerification schedule would land us in that bad place.
The thing I do not understand is that things did not get back to normal once the verification is done with. Perhaps this should be reported to Claris.