Thank you @lhebert. Looks like it was actually caused by SELinux, and we now have custom selinux policies to overcome this issue.   ... View more

yeah, i ended up figuring out last week.   thanks for your reply 🙂 ... View more