On 14/02/16 02:14, Robert Heller wrote: > I sent this out about a week or so ago, but I have heard nothing. I am > *thinking* it is a SELINUX problem, but I cannot figure out what. > If you suspect SELinux is to blame, have you tried putting SELinux into permissive mode to see that resolves the issues? setenforce 0 (re-enable with setenforce 1) If everything works with SELinux in permissive mode, then you'll need to create a policy for it *[0]*. ak. *[0]*: https://wiki.centos.org/HowTos/SELinux#head-faa96b3fdd922004cdb988c1989e56191c257c01