I've only been able to resolved this, by reverting back to Snort 2, deploy, and back to Snort 3, and of course, deploy. The only caveat is that it will cause a short interruption of traffic.
It is possible, however, that it may come back with same error after some time.
