We've resolved the issue but will be keeping an eye on the system. We believe an automatic update that was performed overnight caused some configuration changes which resulted in the error appearing. We're going to mark this as resolved, but as mentioned we will be keeping an eye on it.