selinux enabled ? Looks that way. You either need to write some policy rules to allow the 2 daemons to talk when started as services - eg read audit log, use audit2allow etc (advised, recommended) or turn selinux off (hack, not advised. .. may be done briefly as part of troubleshooting to pinpoint its an selinux issue)<br>
<br>
alan