I’ve seen these errors before, and they’ve always been caused by some oddball Asternic Reports MySQL TRIGGER.